posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
|
|||||||||||||||||||||||||||||||||
| Linux | Linux | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | — |
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4327-1 | linux security update |
Debian DLA |
DLA-4328-1 | linux-6.1 security update |
Debian DSA |
DSA-5973-1 | linux security update |
EUVD |
EUVD-2025-22297 | 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. |
Ubuntu USN |
USN-7769-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7769-2 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-7769-3 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7770-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7771-1 | Linux kernel (OEM) vulnerabilities |
Ubuntu USN |
USN-7774-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7774-2 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7774-3 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-7775-1 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-7775-2 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7776-1 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7775-3 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7774-4 | Linux kernel (KVM) vulnerabilities |
Ubuntu USN |
USN-7789-1 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7774-5 | Linux kernel (NVIDIA Tegra IGX) vulnerabilities |
Ubuntu USN |
USN-7789-2 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-7853-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7853-2 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7854-1 | Linux kernel (KVM) vulnerabilities |
Ubuntu USN |
USN-7861-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7863-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7861-2 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-7864-1 | Linux kernel (GCP and GKE) vulnerabilities |
Ubuntu USN |
USN-7853-3 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7865-1 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7861-3 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7874-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7874-2 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-7861-4 | Linux kernel (AWS) vulnerabilities |
Ubuntu USN |
USN-7875-1 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-7861-5 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-7874-3 | Linux kernel (IoT) vulnerabilities |
Ubuntu USN |
USN-7935-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7937-1 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-7939-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-7939-2 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-7940-1 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-7940-2 | Linux kernel (Azure, N-Series) vulnerabilities |
Ubuntu USN |
USN-7986-1 | Linux kernel vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is in the KEV database since Sept. 4, 2025.
Exploit prediction score: 1.4% (1.357% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Debian
Debian debian Linux |
|
| CPEs | cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | |
| Vendors & Products |
Debian
Debian debian Linux |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
kev
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-362 |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-367 |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-362 | |
| Metrics |
cvssV3_1
|
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linux
Linux linux Kernel |
|
| Vendors & Products |
Linux
Linux linux Kernel |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() | |
| References |
|
|