Local system hang via recursive IRQ exit
Published Sep 11, 2025 · Updated May 11, 2026
Kernel RCU deadlock in affected Linux releases allows local users to hang the system by running BPF code on the trace_tick_stop tracepoint. During irq_exit(), rcu_read_unlock_special() queues defer_qs_iw to the current CPU, whose IPI re-enters irq_exit() and recursively locks up. Local access and permission to load the tracepoint BPF program are required; the demonstrated consequence is a system hang.
Summary
What happened
Kernel RCU deadlock in affected Linux releases allows local users to hang the system by running BPF code on the trace_tick_stop tracepoint. During irq_exit(), rcu_read_unlock_special() queues defer_qs_iw to the current CPU, whose IPI re-enters irq_exit() and recursively locks up. Local access and permission to load the tracepoint BPF program are required; the demonstrated consequence is a system hang.
The record
- CVE
- CVE-2025-39744
- Published
- Sep 11, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 11, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0864f057b050bc6dd68106b3185e02db5140012d <1cfa244f7198d325594e627574930b7b91df5bfe
- Affected versionversion=0864f057b050bc6dd68106b3185e02db5140012d <56c5ef194f4509df63fc0f7a91ea5973ce479b1e
- Affected versionversion=0864f057b050bc6dd68106b3185e02db5140012d <b41642c87716bbd09797b1e4ea7d904f06c39b7b
- Affected versionversion=0864f057b050bc6dd68106b3185e02db5140012d <ddebb2a7677673cf4438a04e1a48b8ed6b0c8e9a
- Affected versionversion=0864f057b050bc6dd68106b3185e02db5140012d <e7a375453cca2b8a0d2fa1b82b913f3fed7c0507
- Affected versionversion=5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo