UBUNTU-CVE-2024-58057: Medium severity ubuntu/linux-hwe-edge vulnerability

Q: What systems are most exposed to this issue?

Systems using the affected Ubuntu kernel packages are most exposed when IDPF workqueue activity is queued on a CPU that is heavily monopolized by another process. The reported scenario involved CPU0 receiving less than 0.5% CPU time for its kworker.

Q: Does exploitation require a remote attacker or user interaction?

The supplied severity vector indicates local access, low attack complexity, low privileges, and no user interaction. The described trigger is a misconfigured process consuming most CPU time on a processor used by the affected workqueues.

Q: What impact should operators expect if the issue is triggered?

IDPF workqueues can experience large completion delays, resulting in performance degradation and timeouts. The description states that the condition can eventually cause a system crash.

Q: What can be done before an updated kernel is deployed?

Avoid allowing processes to monopolize CPUs that service IDPF workqueues, particularly CPU0 in the described scenario. Monitor for sustained CPU starvation of kworker threads alongside IDPF completion delays or timeouts.

Published Mar 6, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: idpf: convert workqueues to unbound When a workqueue is created with WQUNBOUND, its work items are served by special worker-pools, whose host workers are not bound to any specific CPU. In the default configuration (i.e. when queuedelayedwork and friends do not specify which CPU to run the work item on), WQUNBOUND allows the work item to be executed on any CPU in the same node of the CPU it was enqueued on. While this solution potentially sacrifices locality, it avoids contention with other processes that might dominate the CPU time of the processor the work item was scheduled on. This is not just a theoretical problem: in a particular scenario misconfigured process was hogging most of the time from CPU0, leaving less than 0.5% of its CPU time to the kworker. The IDPF workqueues that were using the kworker on CPU0 suffered large completion delays as a result, causing performance degradation, timeouts and eventual system crash. I have also run a manual test to gauge the performance improvement. The test consists of an antagonist process (./stress --cpu 2) consuming as much of CPU 0 as possible. This process is run under taskset 01 to bind it to CPU0, and its priority is changed with chrt -pQ 9900 10000 ${pid} and renice -n -20 ${pid} after start. Then, the IDPF driver is forced to prefer CPU0 by editing all calls to queuedelayedwork, moddelayedwork, etc... to use CPU 0. Finally, ktraces for the workqueue events are collected. Without the current patch, the antagonist process can force arbitrary delays between workqueuequeuework and workqueueexecutestart, that in my tests were as high as 30ms. With the current patch applied, the workqueue can be migrated to another unloaded CPU in the same node, and, keeping everything else equal, the maximum delay I could see was 6us.

Affected Software

120 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.15*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1032.34~22.04.1

6.8.0-1032.34~22.04.1

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1034.39~22.04.1

6.8.0-1034.39~22.04.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1033.35~22.04.1

6.8.0-1033.35~22.04.1

ubuntu/linux-gke*

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-hwe-6.8<6.8.0-64.67~22.04.1

6.8.0-64.67~22.04.1

ubuntu/linux-ibm-6.8<6.8.0-1029.29~22.04.1

6.8.0-1029.29~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-64.67.1~22.04.1

6.8.0-64.67.1~22.04.1

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1031.34~22.04.1

6.8.0-1031.34~22.04.1

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1029.30~22.04.1

6.8.0-1029.30~22.04.1

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-64.67~22.04.1

6.8.0-64.67~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime-6.8<6.8.1-1025.26~22.04.1

6.8.1-1025.26~22.04.1

ubuntu/linux-gcp-fips*

ubuntu/linux<6.8.0-64.67

6.8.0-64.67

ubuntu/linux-aws<6.8.0-1032.34

6.8.0-1032.34

ubuntu/linux-azure<6.8.0-1034.39

6.8.0-1034.39

ubuntu/linux-azure-6.11<6.11.0-1015.15~24.04.1

6.11.0-1015.15~24.04.1

ubuntu/linux-azure-nvidia<6.8.0-1022.23

6.8.0-1022.23

ubuntu/linux-gcp<6.8.0-1033.35

6.8.0-1033.35

ubuntu/linux-gcp-6.11<6.11.0-1015.15~24.04.1

6.11.0-1015.15~24.04.1

ubuntu/linux-gke<6.8.0-1028.32

6.8.0-1028.32

ubuntu/linux-gkeop<6.8.0-1015.17

6.8.0-1015.17

ubuntu/linux-hwe-6.11<6.11.0-26.26~24.04.1

6.11.0-26.26~24.04.1

ubuntu/linux-ibm<6.8.0-1029.29

6.8.0-1029.29

ubuntu/linux-lowlatency<6.8.0-64.67.1

6.8.0-64.67.1

ubuntu/linux-lowlatency-hwe-6.11<6.11.0-1014.15~24.04.1

6.11.0-1014.15~24.04.1

ubuntu/linux-nvidia<6.8.0-1031.34

6.8.0-1031.34

ubuntu/linux-nvidia-6.11<6.11.0-1010.10

6.11.0-1010.10

ubuntu/linux-nvidia-lowlatency<6.8.0-1031.34.1

6.8.0-1031.34.1

ubuntu/linux-nvidia-tegra<6.8.0-1008.8

6.8.0-1008.8

ubuntu/linux-oem-6.11<6.11.0-1022.22

6.11.0-1022.22

ubuntu/linux-oem-6.8<6.8.0-1031.31

6.8.0-1031.31

ubuntu/linux-oracle<6.8.0-1029.30

6.8.0-1029.30

ubuntu/linux-raspi<6.8.0-1031.35

6.8.0-1031.35

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-xilinx<6.8.0-1017.18

6.8.0-1017.18

ubuntu/linux-raspi-realtime<6.8.0-2026.27

6.8.0-2026.27

ubuntu/linux-realtime<6.8.1-1025.26

6.8.1-1025.26

ubuntu/linux-fips<6.8.0-78.78+fips1

6.8.0-78.78+fips1

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.34~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1034.39~22.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1033.35~22.04.1
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-64.67~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1029.29~22.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-64.67.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1031.34~22.04.1
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1029.30~22.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-64.67~22.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1025.26~22.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-64.67
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.34
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1034.39
Upgrade
Upgrade ubuntu/linux-azure-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1015.15~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1022.23
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1033.35
Upgrade
Upgrade ubuntu/linux-gcp-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1015.15~24.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1028.32
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1015.17
Upgrade
Upgrade ubuntu/linux-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-26.26~24.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1029.29
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-64.67.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1014.15~24.04.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1031.34
Upgrade
Upgrade ubuntu/linux-nvidia-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1010.10
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1031.34.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1008.8
Upgrade
Upgrade ubuntu/linux-oem-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1022.22
Upgrade
Upgrade ubuntu/linux-oem-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1031.31
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1029.30
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1031.35
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.18
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2026.27
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1025.26
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78+fips1
Configuration
Create the IDPF workqueues with the WQ_UNBOUND flag so their work items can run on an unloaded CPU in the same node instead of remaining bound to the CPU where they were enqueued.
Linux kernel IDPF driver workqueues WQ_UNBOUND = enabled

Event History

Mar 6, 2025

CVE Published

via OSV·04:15 PM

Data Sourced

via OSV·04:15 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

What systems are most exposed to this issue?

Systems using the affected Ubuntu kernel packages are most exposed when IDPF workqueue activity is queued on a CPU that is heavily monopolized by another process. The reported scenario involved CPU0 receiving less than 0.5% CPU time for its kworker.

Does exploitation require a remote attacker or user interaction?

The supplied severity vector indicates local access, low attack complexity, low privileges, and no user interaction. The described trigger is a misconfigured process consuming most CPU time on a processor used by the affected workqueues.

What impact should operators expect if the issue is triggered?

IDPF workqueues can experience large completion delays, resulting in performance degradation and timeouts. The description states that the condition can eventually cause a system crash.

What can be done before an updated kernel is deployed?

Avoid allowing processes to monopolize CPUs that service IDPF workqueues, particularly CPU0 in the described scenario. Monitor for sustained CPU starvation of kworker threads alongside IDPF completion delays or timeouts.

UBUNTU-CVE-2024-58057: Medium severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

What systems are most exposed to this issue?

Does exploitation require a remote attacker or user interaction?

What impact should operators expect if the issue is triggered?

What can be done before an updated kernel is deployed?

Company

Resources

Contact

Frequently Asked Questions

What systems are most exposed to this issue?

Does exploitation require a remote attacker or user interaction?

What impact should operators expect if the issue is triggered?

What can be done before an updated kernel is deployed?