Exploited CVEs / Linux / CVE-2025-38352
CVE-2025-38352
Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2025-09-25 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Actively exploited Linux Kernel vulnerability, High severity, CVSS 7.4. Added to the CISA KEV catalog 2025-09-04.
Risk summary
Updated July 26, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2025-38352
This is a Linux kernel race condition in posix-cpu-timers where handle_posix_cpu_timers() and posix_cpu_timer_del() can collide, affecting azl3 kernel builds 6.6.96.1-1 and 6.6.92.2-2 on Azure Linux 3.0. Despite a low 1% EPSS score, CISA added it to the Known Exploited Vulnerabilities catalog on 2025-09-04, so it is confirmed exploited in the wild. Timer race conditions like this are typically leveraged for local privilege escalation, meaning any user with local access to these hosts is a concern.
Do this: Patch the azl3 kernel on all Azure Linux 3.0 hosts running 6.6.96.1-1 or 6.6.92.2-2 to a fixed build and reboot to load it.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-38352
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2025-38352
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2025-09-25 (past due).
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Official fix for CVE-2025-38352
Check the vendor's security advisory channel for the patched Kernel versions and workarounds.
Common questions about CVE-2025-38352
Is CVE-2025-38352 actively exploited?
Yes. CVE-2025-38352 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2025-09-04, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 1.4%.
What is the CISA deadline and required action for CVE-2025-38352?
CISA set the federal (BOD 22-01) remediation due date at 2025-09-25, which has passed; treat any unremediated system as overdue. The verbatim 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.
What fixes CVE-2025-38352?
Check the vendor's security advisory for the patched Kernel versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2025-38352?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2025-38352's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
More exploited Linux CVEs
The newest Linux entries on the CISA KEV catalog:
All Linux exploited CVEs on one page: Linux vulnerabilities actively exploited.
Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.
