CVE-2025-38352
posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()
Reported by linux · Published July 22, 2025
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| perf | Amazon Linux | 4.14.355-280.679.amzn2 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 0bdd2ed4138ec04e09b4f8165981efc99e439f55, 0bdd2ed4138ec04e09b4f8165981efc99e439f55, 0bdd2ed4138ec04e09b4f8165981efc99e439f55 |
| Linux | Linux | 2.6.36, 0, 5.4.295 |
| amazon:2 | perf | 0 |
| Linux | Linux | 5.10.239, 0bdd2ed4138ec04e09b4f8165981efc99e439f55, 5.15.186 |
| linux | linux_kernel | |
| amazon:2023 | perf6.12 | 0 |
| amazon:2 | kernel-tools | 0 |
| amazon:2023 | perf | 0 |
| linux | linux_kernel | 2.6.36, 2.6.36, 2.6.36 |
| amazon:2 | kernel-devel | 0 |
| amazon:2023 | kernel-livepatch-6.12.35-55.103 | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2 | kernel | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2 | kernel-tools-devel | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
…and 12 more
Timeline
- Jul 10, 2025 CVE Published
- Jul 22, 2025 EPSS Score (30 in total, the first dated here)
- Sep 1, 2025 VulnCheck KEV Exploitation (7 in total, the first dated here)
- Sep 1, 2025 PoC Published (12 in total, the first dated here)
- Sep 4, 2025 CISA KEV Added
- Dec 21, 2025 VulnCheck XDB Entry (4 in total, the first dated here)
- Mar 17, 2026 Security Advisory (157 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (149 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38352
vulnetix vdb fixes CVE-2025-38352
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38352/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart