Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability
Linux — Linux
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
7.8
1.3%
Vector breakdown
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- Jul 22, 2025
- Modified
- Jul 30, 2026
- Added to KEV
- Sep 4, 2025
- Federal patch due
- Sep 25, 2025
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
5 foundWeaponization
Public repositories whose name or description references CVE-2025-38352, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- farazsth98/chronomaly★ 311
Android kernel exploit for CVE-2025-38352, previously exploited in-the-wild. Targets vulnerable x86_64 Linux kernels v5.10.x.
updated Aug 24, 2026
- farazsth98/poc-CVE-2025-38352★ 117
This is a proof of concept for CVE-2025-38352, a vulnerability in the Linux kernel's POSIX CPU timers implementation. The September 2025 Android Bulletin mentions that this vulnerability has been used in limited, targeted exploitation in the wild.
updated Sep 4, 2026
- AnalyticETH/chronomaly-webos★ 13
CVE-2025-38352 kernel exploit for LG webOS Smart TVs (ARM64). Achieves persistent root on real consumer hardware with novel exploitation techniques. Responsibly disclosed to LG.
updated Sep 2, 2026
- jordelmir/Elysium-Vanguard-Sentinel-Audit★ 2
The official Sentinel Edition v7.11 - Hypervisor Detection & Kernel Memory Audit Suite for Honor Magic V2. Investigating CVE-2025-38352 and EL2 RKP defenses.
updated Mar 18, 2026
- Crime2/poc-CVE-2025-38352★ 0
updated Jul 10, 2026
References
Frequently asked questions
What is CVE-2025-38352?
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand(). If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail. Add the tsk->exit_state check into run_posix_cpu_timers() to fix this. This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.
How severe is CVE-2025-38352?
CVE-2025-38352 has a CVSS base score of 7.8 out of 10 (CVSS 3.1).
Is CVE-2025-38352 actively exploited in the wild?
Yes. CVE-2025-38352 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Sep 4, 2025, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-38352?
1.3% - meaning FIRST.org's EPSS model estimates a 1.3% probability this vulnerability will be exploited in the wild within 30 days (68% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2025-38352?
We found 5 public GitHub repositories referencing CVE-2025-38352, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2025-38352?
CVE-2025-38352 is classified under CWE-367 (CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition).
Cross-checked against
Impactr finds and proves whether CVE-2025-38352 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist