CVE-2025-38352
In the Linux kernel, the following vulnerability has been resolved:
posix-cpu-timers: fix race between handleposixcputimers() and posixcputimerdel()
If an exiting non-autoreaping task has already passed exit_notify() and
calls handleposixcpu_timers() from IRQ, it can be reaped by its parent
or debugger right after unlocktasksighand().
If a concurrent posixcputimer_del() runs at that moment, it won't be
able to detect timer->it.cpu.firing != 0: cputimertask_rcu() and/or
locktasksighand() will fail.
Add the tsk->exitstate check into runposixcputimers() to fix this.
This fix is not needed if CONFIGPOSIXCPUTIMERSTASK_WORK=y, because
exittaskwork() is called before exit_notify(). But the check still
makes sense, taskworkadd(&tsk->posixcputimerswork.work) will fail
anyway in this case.
Package Versions Affected
Automatically patch vulnerabilities without upgrading
CVSS Version



Related Resources
References
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git, https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff, https://git.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0b, https://git.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757b, https://git.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bb, https://git.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200, https://git.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1b, https://git.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7, https://git.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330eca, https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38352.json, https://github.com/farazsth98/chronomaly, https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html, https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html, https://nvd.nist.gov/vuln/detail/CVE-2025-38352, https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-38352
