CVE-2025-39744
Last modified
CVE-2025-39744 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: rcu: Fix rcu_read_unlock() deadloop due to IRQ work During rcu_read_unlock_special(), if this happens during irq_exit(), we can lockup if an IPI is issued. This is because the IPI itself triggers the irq_exit() path causing a recursive lock up. This is precisely what Xiongfeng found when invoking a BPF program on the trace_tick_stop() tracepoint As shown in the trace below. Fix by managing the irq_work state correctly. irq_exit() __irq_exit_rcu() /* in_hardirq() returns false after this */ preempt_count_sub(HARDIRQ_OFFSET) tick_irq_exit() tick_nohz_irq_exit() tick_nohz_stop_sched_tick() trace_tick_stop() /* a bpf prog is hooked on this trace point */ __bpf_trace_tick_stop() bpf_trace_run2() rcu_read_unlock_special() /* will send a IPI to itself */ irq_work_queue_on(&rdp->defer_qs_iw, rdp->cpu); A simple reproducer can also be obtained by doing the following in tick_irq_exit(). It will hang on boot without the patch: static inline void tick_irq_exit(void) { + rcu_read_lock(); + WRITE_ONCE(current->rcu_read_unlock_special.b.need_qs, true); + rcu_read_unlock(); + [neeraj: Apply Frederic's suggested fix for PREEMPT_RT]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 6.6.103 |
| Linux | Linux Kernel | >= 6.7, < 6.12.43 |
| Linux | Linux Kernel | >= 6.13, < 6.15.11 |
| Linux | Linux Kernel | >= 6.16, < 6.16.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-39744?
How severe is CVE-2025-39744?
How do I fix CVE-2025-39744?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39739In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3974A vulnerability has been found in PHPGurukul COVID19 Testing…9.8
- CVE-2025-39740In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39741In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39742In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39743In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39745In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39746In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39747In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39748In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39749In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-3975A vulnerability was found in ScriptAndTools eCommerce-websit…6.9
Are you affected by CVE-2025-39744?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
