Threats / Linux / CVE-2025-38352
CVE-2025-38352
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Linux Kernel vulnerability
Linux kernel TOCTOU race condition allows attackers to exploit timing windows between security checks and resource use, potentially compromising system confidentiality, integrity, and availability.
Verdict
Today item — known-exploited.
A time-of-check time-of-use vulnerability in the Linux kernel enables privilege escalation or unauthorized access by racing between permission validation and operation execution. Active exploitation observed in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-09-04).
Probability (EPSS)
EPSS 0.01345 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-367 TOCTOU Race Condition.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-367 · TOCTOU Race Condition
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a window between when the kernel validates access permissions and when it actually performs the protected operation.
Business
Unauthorized code execution or data access occurs on affected systems before patches are deployed.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I repeatedly trigger the vulnerable code path to increase the probability of winning the race condition during the validation gap.
Business
System stability degrades as repeated exploitation attempts consume resources and cause unpredictable behavior.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain elevated privileges or bypass access controls by modifying protected resources after the check but before use.
Business
Confidential data is exposed and system integrity is compromised across the affected Linux infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05