Linux
posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 78a4b8e3795b31dae58762bc091bb0f4f74a2200
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < c076635b3a42771ace7d276de8dc3bc76ee2ba1b
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < c29d5318708e67ac13c1b6fc1007d179fb65b4d7
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b
- >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55, < f90fff1e152dedf52b932240ebbd670d83330eca
Fixed in 78a4b8e3795b31dae58762bc091bb0f4f74a2200, c076635b3a42771ace7d276de8dc3bc76ee2ba1b, 2f3daa04a9328220de46f0d5c919a6c0073a9f0b, 764a7a5dfda23f69919441f2eac2a83e7db6e5bb, 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff, c29d5318708e67ac13c1b6fc1007d179fb65b4d7, 460188bc042a3f40f72d34b9f7fc6ee66b0b757b, f90fff1e152dedf52b932240ebbd670d83330eca
- 2.6.36
Fixed in 0, 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15.3, 6.16
Mitigation
Upgrade Linux to 78a4b8e3795b31dae58762bc091bb0f4f74a2200 or c076635b3a42771ace7d276de8dc3bc76ee2ba1b or 2f3daa04a9328220de46f0d5c919a6c0073a9f0b or 764a7a5dfda23f69919441f2eac2a83e7db6e5bb or 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff or c29d5318708e67ac13c1b6fc1007d179fb65b4d7 or 460188bc042a3f40f72d34b9f7fc6ee66b0b757b or f90fff1e152dedf52b932240ebbd670d83330eca or later.
Upgrade Linux to 0 or 5.4.295 or 5.10.239 or 5.15.186 or 6.1.142 or 6.6.94 or 6.12.34 or 6.15.3 or 6.16 or later.
Timeline
Days relative to CVE publicationFirst public PoC 153 days after publication; added to CISA KEV 44 days after publication. First PoC: farazsth98/poc-CVE-2025-38352 (created 21 Dec 2025, found by us: backfilled).
PoC repositories
Found on GitHub.7 PoCs · 1 informational
PoCs 7
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| farazsth98/poc-CVE-2025-38352 | 21 Dec 2025 +153 d | backfilled | 120 | PoC |
| farazsth98/chronomaly | 3 Jan 2026 +165 d | backfilled | 314 | PoC via PoC Index |
| Crime2/poc-CVE-2025-38352 | 8 Jan 2026 +170 d | backfilled | 0 | PoC |
| emurray2/chronomaly | 8 Feb 2026 +202 d | backfilled | 0 | PoC via PoC Index |
| AnalyticETH/chronomaly-webos | 30 May 2026 +312 d | backfilled | 19 | PoC |
| longwasu/CVE-2025-38352-PoC | 13 Sep 2026 +1.1 y | backfilled | 0 | PoC |
| pauloberenguel/lg-tv-root-exploit | 6 Nov 2026 +1.3 y | 14 Nov 2026 | 0 | PoC via PoC Index |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| jordelmir/Elysium-Vanguard-Sentinel-Audit | 24 Feb 2026 +217 d | 3 | Informational · detection
Flags · score 40
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.