DE EN IT

~/exploited / cve-2025-39964

CVE-2025-39964: Linux Kernel

According to CISA this vulnerability is already used in attacks (added on 18 September 2026).

Key facts

CVECVE-2025-39964
VendorLinux — Kernel
VulnerabilityLinux Kernel Race Condition Vulnerability
Added18 September 2026
Deadline (US agencies)21 September 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score5.5 (medium) · CVSS 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack local, complexity: low, privileges: low needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 1.61%. Higher than 76.4% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-362 — Race Condition
Affected versionslinux kernel: >= 2.6.38, < 5.10.245
linux kernel: >= 5.11, < 5.15.194
linux kernel: >= 5.16, < 6.1.154
linux kernel: >= 6.2, < 6.6.108
linux kernel: >= 6.7, < 6.12.49
linux kernel: >= 6.13, < 6.16.9
linux kernel 6.17
simatic s7-1500 cpu 1518-4 pn\/dp mfp firmware: >= 3.1.6
and 1 more

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

Linux Kernel contains a race condition vulnerability which allows concurrent writes to the same AF_ALG socket causing data to be unpredictably interleaved and creating inconsistencies in the socket's internal state.

Required action (CISA)

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.

What admins should do now

  1. Affected? Check whether Linux Kernel is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 18 September 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).