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,… (CVE-2026-64073)
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.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel affects irq_work_single() on PREEMPT_RT systems where non-HARD irq_work runs in per-CPU kernel threads. After irq_work_single() clears the BUSY flag using atomic operations, it still dereferences the work structure for further checks. Meanwhile, another CPU may observe BUSY as cleared and free the work structure prematurely, causing a use-after-free condition. The patch wraps run_irq_workd() in an RCU read-side critical section and adds synchronize_rcu() in irq_work_sync() to ensure the caller waits for the RCU grace period before returning, preventing premature freeing and use-after-free.
Potential Impact
This vulnerability can lead to use-after-free memory corruption in the Linux kernel on PREEMPT_RT configurations. Such memory corruption could potentially cause system instability, crashes, or escalation of privileges if exploited. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by introducing RCU synchronization mechanisms to prevent premature freeing of irq_work structures. Users should apply the official Linux kernel updates that include this fix. Since no vendor advisory or patch links are provided, check the Linux kernel mailing lists or official repositories for the relevant patch and update guidance. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
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,… (CVE-2026-64073)
Description
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.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel affects irq_work_single() on PREEMPT_RT systems where non-HARD irq_work runs in per-CPU kernel threads. After irq_work_single() clears the BUSY flag using atomic operations, it still dereferences the work structure for further checks. Meanwhile, another CPU may observe BUSY as cleared and free the work structure prematurely, causing a use-after-free condition. The patch wraps run_irq_workd() in an RCU read-side critical section and adds synchronize_rcu() in irq_work_sync() to ensure the caller waits for the RCU grace period before returning, preventing premature freeing and use-after-free.
Potential Impact
This vulnerability can lead to use-after-free memory corruption in the Linux kernel on PREEMPT_RT configurations. Such memory corruption could potentially cause system instability, crashes, or escalation of privileges if exploited. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by introducing RCU synchronization mechanisms to prevent premature freeing of irq_work structures. Users should apply the official Linux kernel updates that include this fix. Since no vendor advisory or patch links are provided, check the Linux kernel mailing lists or official repositories for the relevant patch and update guidance. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8ffv-2j52-h7h3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64073"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912c562
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:53:19 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.