CVE-2025-38352
HighExploitedPublic exploitLinux kernel: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()
Published Jul 22, 2025 · Updated Oct 14, 2026 · Also known as A-425282960, ASB-A-425282960, DEBIAN-CVE-2025-38352, ROOT-OS-DEBIAN-11-CVE-2025-38352, ROOT-OS-DEBIAN-12-CVE-2025-38352, ROOT-OS-UBUNTU-2204-CVE-2025-38352, ROOT-OS-UBUNTU-2404-CVE-2025-38352, USN-7853-3, USN-7854-1, USN-7874-2
Key Facts
Patch immediately- CVE-2025-38352 is a high-severity vulnerability (CVSS 7.4 v3.1) affecting linux-6.1 (debian), linux (debian), rootio-linux and 22 more products.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Sep 1, 2025. Public exploit code is available.
- EPSS estimates a 1.3% probability of exploitation in the next 30 days.
- Fixed versions are available, including aws 116.1, aws-5.15 116.1, aws-hwe 116.1.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
7.4
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
1.3%
Higher than 70.8% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2025-38352 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Sep 4, 2025 | Sep 25, 2025 | Not reported |
| Industry KEV feed | Sep 1, 2025 | Sep 25, 2025 | Not reported |
| CIRCL KEV | Sep 4, 2025 | Sep 25, 2025 | Not reported |
| ENISA EUVD | Sep 4, 2025 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected Products
5,330 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| linux-6.1debian | See advisory | 6.1.153-1~deb11u1 |
| linuxdebian | See advisory | 5.10.244-1 |
| rootio-linuxrootio | See advisory | 5.10.244-1 |
| aws-5.15ubuntu | See advisory | 116.1 |
| awsubuntu | See advisory | 116.1 |
Patched Releases
aws
116.1
aws-5.15
116.1
aws-hwe
116.1
azure
116.1
azure-5.15
116.1
bpftool
1:6.1.144-170.251.amzn2023, 3.10.0-1160.119.1.0.12.el7, 4.18.0-553.74.1.el8_10, 5.10.239-1.ph4, 5.15.0-312.187.5.el8uek, 5.15.0-312.187.5.el9uek, 6.1.143-1.ph5, 6.12.35-55.103.amzn2023, 7.6.0+6.14.0-32.32
cluster-md-kmp-64kb
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
cluster-md-kmp-azure
6.4.0-150600.8.48.1
cluster-md-kmp-default
4.12.14-122.272.1, 5.14.21-150400.24.176.1, 5.14.21-150500.55.121.2, 5.3.18-150300.59.218.1, 6.12.0-160000.6.1, 6.4.0-150600.23.65.1, 6.4.0-150700.53.11.1
cluster-md-kmp-rt
6.12.0-160000.6.1, 6.4.0-150600.10.49.1, 6.4.0-150700.7.13.1
dlm-kmp-64kb
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dlm-kmp-azure
6.4.0-150600.8.48.1
dlm-kmp-default
4.12.14-122.272.1, 5.14.21-150400.24.176.1, 5.14.21-150500.55.121.2, 5.3.18-150300.59.218.1, 6.12.0-160000.6.1, 6.4.0-150600.23.65.1, 6.4.0-150700.53.11.1
dlm-kmp-rt
6.12.0-160000.6.1, 6.4.0-150600.10.49.1, 6.4.0-150700.7.13.1
dtb-allwinner
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-altera
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-amazon
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-amd
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-amlogic
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-apm
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-apple
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-arm
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-broadcom
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-cavium
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
dtb-exynos
6.12.0-160000.6.1, 6.4.0-150600.23.65.1
Timeline
Publicly disclosed
Jul 22, 2025
Added to Industry KEV feed
Sep 1, 2025
Added to CISA KEV
Sep 4, 2025
Added to CIRCL KEV
Sep 4, 2025
Added to ENISA EUVD
Sep 4, 2025
Last updated
Oct 14, 2026
Weakness Type
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
References
- advisoryRHSA-2025:15471
- advisoryRHSA-2025:15472
- advisoryRHSA-2025:15646
- advisoryRHSA-2025:15647
- advisoryRHSA-2025:15648
FAQ
Common Questions.
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…
Affected: linux-6.1 (debian); linux (debian); rootio-linux, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Sep 1, 2025.
Yes. It was added on Sep 4, 2025 with a federal remediation due date of Sep 25, 2025.
Public exploit code is available.
Fixed versions are available, including aws 116.1, aws-5.15 116.1, aws-hwe 116.1.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2025-38352 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo