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.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
| Linux | Linux | 5.16CNA affecteddefault affected | |
| Linux | Linux | >= 810979682ccc98dbd83f341c18a2e556c30a7164, < 18c0456ea2615b1a743a6db739c74411c3b42bc6, >= 810979682ccc98dbd83f341c18a2e556c30a7164, < 2dc79362302922cb18f35e262712b5e58de65442, >= 810979682ccc98dbd83f341c18a2e556c30a7164, < 684a78183c54c23e70d1cba320f7fc184604210b, >= 810979682ccc98dbd83f341c18a2e556c30a7164, < 81b582784518196eff1050212a046bc29d3a05dd, >= 810979682ccc98dbd83f341c18a2e556c30a7164, < 91840be8f710370607f949a627e070896faeddb8, >= 810979682ccc98dbd83f341c18a2e556c30a7164, < eef4f71b46a9929ac33e968538c9dd5d96a02460CNA affecteddefault unaffected |
CVSS version used by this source: 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
No social media mentions found for this CVE.
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.2 Bluesky, 0.1 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.3 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.