Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2025-40176

A critical flaw in the Linux kernel’s TLS handling could let an attacker cause a use‑after‑free or overwrite user memory if an async decryption fails. The kernel now waits for all pending decryption requests when the allocation for a clone fails, preventing the vulnerability. The issue is fixed in recent kernel releases.

publishedNov 12, 2025
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
35th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 29, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel, all distributions that use affected kernel versions. Typical users are system administrators and end users of those distributions.

02

Real-world impact

An attacker could exploit the flaw to crash the system, cause a denial of service, or potentially execute arbitrary code by triggering a use‑after‑free or memory overwrite during TLS processing.

03

Why this severity

The CVSS score of 9.8 reflects the vulnerability’s high impact on confidentiality, integrity, and availability, and the fact that it can be exploited remotely without authentication or user interaction.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade your Linux kernel to a version that includes the fix for CVE-2025-40176.
  2. 02Reboot the system to load the new kernel.

NVD description indicates the issue has been resolved in the Linux kernel.

05

Timeline

  1. Nov 12, 2025 · Nov 12, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 30, 2026 · 6d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 30, 2026 · 6d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →