CVE-2025-38352: Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability
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 Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38352?
The severity of CVE-2025-38352 is categorized as medium due to its potential impact on system stability.
How do I fix CVE-2025-38352?
To fix CVE-2025-38352, update the Linux kernel to the latest stable version that includes the patch for this vulnerability.
What systems are affected by CVE-2025-38352?
CVE-2025-38352 affects various versions of the Linux kernel used in different distributions.
What are the potential consequences of CVE-2025-38352?
The potential consequences of CVE-2025-38352 include system instability and unexpected behavior during timer operations.
Is there an exploit available for CVE-2025-38352?
As of now, there is no known public exploit for CVE-2025-38352, but it is recommended to apply patches to mitigate risks.