irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 810979682ccc98dbd83f341c18a2e556c30a7164 · < 91840be8f710370607f949a627e070896faeddb8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT
On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0.
After irq_work_single() clears BUSY via atomic_cmpxchg(), it still dereferences @work for irq_work_is_hard() and rcuwait_wake_up().
An irq_work_sync() caller on another CPU that enters after BUSY is cleared can observe BUSY==0 immediately, return, and free the work before those accesses complete — causing a use-after-free.
Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire irq_work_single() execution is within an RCU read-side critical section. Then add synchronize_rcu() in irq_work_sync() after rcuwait_wait_event() to ensure the caller waits for the RCU grace period before returning, preventing premature frees.
From the CVE record · Linux
On PREEMPT_RT Linux kernels, irq_work_single() can access work after another CPU’s irq_work_sync() caller has freed it. This race can cause a use-after-free; the input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with PREEMPT_RT should check their builds; affected versions are not specified.