In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: Convert spinlock to mutex to lock evl workqueue
drain_workqueue() cannot be called safely in a spinlocked context due to
possible task rescheduling. In the multi-task scenario, calling
queue_work() while drain_workqueue() will lead to a Call Trace as
pushing a work on a draining workqueue is not permitted in spinlocked
context.
Call Trace:
<TASK>
? __warn+0x7d/0x140
? __queue_work+0x2b2/0x440
? report_bug+0x1f8/0x200
? handle_bug+0x3c/0x70
? exc_invalid_op+0x18/0x70
? asm_exc_invalid_op+0x1a/0x20
? __queue_work+0x2b2/0x440
queue_work_on+0x28/0x30
idxd_misc_thread+0x303/0x5a0 [idxd]
? __schedule+0x369/0xb40
? __pfx_irq_thread_fn+0x10/0x10
? irq_thread+0xbc/0x1b0
irq_thread_fn+0x21/0x70
irq_thread+0x102/0x1b0
? preempt_count_add+0x74/0xa0
? __pfx_irq_thread_dtor+0x10/0x10
? __pfx_irq_thread+0x10/0x10
kthread+0x103/0x140
? __pfx_kthread+0x10/0x10
ret_from_fork+0x31/0x50
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1b/0x30
</TASK>
The current implementation uses a spinlock to protect event log workqueue
and will lead to the Call Trace due to potential task rescheduling.
To address the locking issue, convert the spinlock to mutex, allowing
the drain_workqueue() to be called in a safe mutex-locked context.
This change ensures proper synchronization when accessing the event log
workqueue, preventing potential Call Trace and improving the overall
robustness of the code.
References
Configurations
Configuration 1 (hide)
|
History
24 Sep 2025, 18:15
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-667 | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
First Time |
Linux
Linux linux Kernel |
|
CPE | cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:* |
|
References | () https://git.kernel.org/stable/c/758071a35d9f3ffd84ff12169d081412a2f5f098 - Patch | |
References | () https://git.kernel.org/stable/c/c9b732a9f73eadc638abdcf0a6d39bc7a0c1af5f - Patch | |
References | () https://git.kernel.org/stable/c/d5638de827cff0fce77007e426ec0ffdedf68a44 - Patch |
21 Nov 2024, 09:21
Type | Values Removed | Values Added |
---|---|---|
References | () https://git.kernel.org/stable/c/758071a35d9f3ffd84ff12169d081412a2f5f098 - | |
References | () https://git.kernel.org/stable/c/c9b732a9f73eadc638abdcf0a6d39bc7a0c1af5f - | |
References | () https://git.kernel.org/stable/c/d5638de827cff0fce77007e426ec0ffdedf68a44 - | |
Summary |
|
20 May 2024, 13:00
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-05-20 10:15
Updated : 2025-09-24 18:15
NVD link : CVE-2024-35991
Mitre link : CVE-2024-35991
CVE.ORG link : CVE-2024-35991
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking