CVE-2025-38352
Published: Jul 22, 2025
Modified: May 11, 2026
Description
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.
| Vendor | Product | Versions |
|---|---|---|
Linux | Linux | affected 0bdd2ed4138ec04e09b4f8165981efc99e439f55 - < 78a4b8e3795b31dae58762bc091bb0f4f74a2200affected 0bdd2ed4138ec04e09b4f8165981efc99e439f55 - < c076635b3a42771ace7d276de8dc3bc76ee2ba1baffected 0bdd2ed4138ec04e09b4f8165981efc99e439f55 - < 2f3daa04a9328220de46f0d5c919a6c0073a9f0baffected 0bdd2ed4138ec04e09b4f8165981efc99e439f55 - < 764a7a5dfda23f69919441f2eac2a83e7db6e5bbaffected 0bdd2ed4138ec04e09b4f8165981efc99e439f55 - < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff+3 more versions |
Linux | Linux | affected 2.6.36unaffected 0 - < 2.6.36unaffected 5.4.295 - <= 5.4.*unaffected 5.10.239 - <= 5.10.*unaffected 5.15.186 - <= 5.15.*+5 more versions |
References
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now