CVE-2025-39964
crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg
Exploited in the wild. In CISA KEV since 2026‑09‑18. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record- Ask IT to identify every server, workstation, appliance, and virtual machine running the Linux kernel and record its installed kernel version.
- Install your operating-system or device vendor’s security update containing the fix; for the 5.10 branch, update to 5.10.245 or later.
- Restart updated systems into the new kernel and confirm the running version after reboot.
- If an update is unavailable, restrict untrusted local accounts and container workloads until the vendor provides a fixed release.
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg Issuing two writes to the same af_alg socket is bogus as the data will be interleaved in an unpredictable fashion. Furthermore, concurrent writes may create inconsistencies in the internal socket state. Disallow this by adding a new ctx->write field that indiciates exclusive ownership for writing.
In plain language
Written by AI from the recordThis is a serious flaw in the Linux kernel that attackers are actively using; update systems that have not received the vendor fix, including Linux kernel 5.10 systems before 5.10.245.
A locally authenticated attacker can exploit a race condition in Linux kernel AF_ALG socket handling by issuing concurrent writes, potentially compromising confidentiality, integrity, and availability.
If you're affected
- Full system compromise
- Business data exposure
- Service disruption
- Ransomware risk
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2026-09-18.
US federal agencies must remediate by 2026-09-21.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
1.0% chance of exploitation activity in the next 30 days, which ranks it in the 61st percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained, driven by in-the-wild reports.
Lifecycle
The patch came 8 days before any public exploit.
- Patch availablerecord updated
- Added to CISA KEVpatch available, patch available, record updated, record updated
- Patch availablerecord updated
- Patch availablerecord updated
- OpenVAS check added
- Public exploit / PoCsource: github-poc
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Scored 7.8 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Privilege EscalationT1068Exploitation for Privilege Escalationmedium confidence
Sources
References in the record
- git.kernel.org/stable/c/0f28c4adbc4a97437874c9b669fd7958a8c6d6ce
- git.kernel.org/stable/c/e4c1ec11132ec466f7362a95f36a506ce4dc08c9
- git.kernel.org/stable/c/1f323a48e9b5ebfe6dc7d130fdf5c3c0e92a07c8
And 496 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Siemens, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI