cbcvebase.
CVE-2024-31076
published 2024-06-21

CVE-2024-31076: In the Linux kernel, the following vulnerability has been resolved: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline The absence of…

PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
17.4th percentile
In the Linux kernel, the following vulnerability has been resolved: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline The absence of IRQD_MOVE_PCNTXT prevents immediate effectiveness of interrupt affinity reconfiguration via procfs. Instead, the change is deferred until the next instance of the interrupt being triggered on the original CPU. When the interrupt next triggers on the original CPU, the new affinity is enforced within __irq_move_irq(). A vector is allocated from the new CPU, but the old vector on the original CPU remains and is not immediately reclaimed. Instead, apicd->move_in_progress is flagged, and the reclaiming process is delayed until the next trigger of the interrupt on the new CPU. Upon the subsequent triggering of the interrupt on the new CPU, irq_complete_move() adds a task to the old CPU's vector_cleanup list if it remains online. Subsequently, the timer on the old CPU iterates over its vector_cleanup list, reclaiming old vectors. However, a rare scenario arises if the old CPU is outgoing before the interrupt triggers again on the new CPU. In that case irq_force_complete_move() is not invoked on the outgoing CPU to reclaim the old apicd->prev_vector because the interrupt isn't currently affine to the outgoing CPU, and irq_needs_fixup() returns false. Even though __vector_schedule_cleanup() is later called on the new CPU, it doesn't reclaim apicd->prev_vector; instead, it simply resets both apicd->move_in_progress and apicd->prev_vector to 0. As a result, the vector remains unreclaimed in vector_matrix, leading to a CPU vector leak. To address this issue, move the invocation of irq_force_complete_move() before the irq_needs_fixup() call to reclaim apicd->prev_vector, if the interrupt is currently or used to be affine to the outgoing CPU. Additionally, reclaim the vector in __vector_schedule_cleanup() as well, following a warning message, although theoretically it should never see apicd->move_in_progress with apicd->

Affected

25 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.94-1 (bookworm)linux 6.1.94-1 (bookworm)
linuxlinux
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < a40209d355afe4ed6d533507838c9e5cd70a76d8a40209d355afe4ed6d533507838c9e5cd70a76d8
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < f5f4675960609d8c5ee95f027fbf6ce380f98372f5f4675960609d8c5ee95f027fbf6ce380f98372
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < 6752dfcfff3ac3e16625ebd3f0ad9630900e7e766752dfcfff3ac3e16625ebd3f0ad9630900e7e76
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < 9eeda3e0071a329af1eba15f4e57dc39576bb4209eeda3e0071a329af1eba15f4e57dc39576bb420
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < e9c96d01d520498b169ce734a8ad1142bef86a30e9c96d01d520498b169ce734a8ad1142bef86a30
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < 59f86a2908380d09cdc726461c0fbb8d8579c99f59f86a2908380d09cdc726461c0fbb8d8579c99f
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < ebfb16fc057a016abb46a9720a54abf0d4f6abe1ebfb16fc057a016abb46a9720a54abf0d4f6abe1
linuxlinux>= f0383c24b4855f6a4b5a358c7b2d2c16e0437e9b < a6c11c0a5235fb144a65e0cb2ffd360ddc1f6c32a6c11c0a5235fb144a65e0cb2ffd360ddc1f6c32
linuxlinux_kernel>= 0 < 5.10.221-15.10.221-1
linuxlinux_kernel>= 0 < 6.1.94-16.1.94-1
linuxlinux_kernel>= 0 < 6.9.7-16.9.7-1
linuxlinux_kernel>= 0 < 6.9.7-16.9.7-1
linuxlinux_kernel>= 0 < 5.4.0-192.2125.4.0-192.212
linuxlinux_kernel>= 0 < 5.15.0-121.1315.15.0-121.131
linuxlinux_kernel>= 0 < 6.8.0-44.446.8.0-44.44
linuxlinux_kernel>= 0 < 4.15.0-230.2424.15.0-230.242
linuxlinux_kernel>= 4.13 < 4.19.3164.19.316
linuxlinux_kernel>= 4.20 < 5.4.2785.4.278
linuxlinux_kernel>= 5.11 < 5.15.1615.15.161
linuxlinux_kernel>= 5.16 < 6.1.936.1.93
linuxlinux_kernel>= 5.5 < 5.10.2195.10.219
linuxlinux_kernel>= 6.2 < 6.6.336.6.33
linuxlinux_kernel>= 6.7 < 6.9.46.9.4

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.