CVE-2026-64073

Analyzed Analyzed - Analysis Complete

Use-After-Free in Linux Kernel irq_work

Publication date: 2026-07-19

Last updated on: 2026-09-03

Assigner: kernel.org

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-19

Last Modified

2026-09-03

Generated

2026-09-18

AI Q&A

2026-07-19

EPSS Evaluated

2026-09-15

NVD

CVE-2026-64073

EUVD

EUVD-2026-45646

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 5.16 (inc) to 6.1.175 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.92 (exc)
linux	linux_kernel	From 6.13 (inc) to 6.18.34 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.11 (exc)
linux	linux_kernel	From 6.2 (inc) to 6.6.142 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This is a use-after-free vulnerability in the Linux kernel's irq_work subsystem when running on PREEMPT_RT. The issue occurs because irq_work_sync() can return and free memory while another CPU is still accessing the work structure after clearing the BUSY flag. The fix involves wrapping irq_work_single() in an RCU read-side critical section and adding synchronize_rcu() in irq_work_sync() to prevent premature frees.

Detection Guidance

This vulnerability is specific to the Linux kernel's irq_work subsystem on PREEMPT_RT systems. Detection requires checking kernel logs for use-after-free errors or kernel crashes related to irq_work. Commands like dmesg | grep -i "irq_work" or journalctl -k | grep -i "use-after-free" may help identify issues. Ensure your kernel is updated to a patched version.

Impact Analysis

This vulnerability could lead to system crashes, data corruption, or privilege escalation if exploited. Systems running Linux kernels with PREEMPT_RT enabled and using irq_work functionality may be affected. The impact depends on whether the vulnerable code paths are triggered in your specific use case.

Compliance Impact

This vulnerability is a use-after-free issue in the Linux kernel's irq_work subsystem on PREEMPT_RT systems. It does not directly relate to data protection or privacy compliance standards like GDPR or HIPAA, as those focus on data handling, storage, and access controls rather than kernel-level concurrency bugs.

Mitigation Strategies

Apply the latest kernel update from your Linux distribution to patch this vulnerability. If updating is not immediately possible, consider disabling PREEMPT_RT or avoiding workloads that trigger irq_work operations until patched. Monitor kernel logs for signs of exploitation or instability.

Hi! I’m here to help you understand CVE-2026-64073. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70