posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()
Get instant alerts when new vulnerabilities affect Linux - before attackers find them.
CISA Known Exploited Vulnerabilities (KEV) Catalog
EPSS (Exploit Prediction Scoring System) estimates a 1.4% chance this CVE is exploited in the wild within the next 30 days — higher than 72% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.
Linux kernel contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that has a high impact on confidentiality, integrity, and availability.
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.
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
No remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
Get alerted
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
This product uses data from the NVD API but is not endorsed or certified by the NVD. CVE records are from the CVE Program (CVE.org).