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

CVE-2026-64142

A race condition in the Linux kernel's SMB server (ksmbd) durable handle scavenger can corrupt lists and cause use‑after‑free conditions, potentially allowing an attacker to execute arbitrary code, cause a denial of service, or escalate privileges. The flaw has been fixed in the Linux kernel by changing how durable handles are scavenged and reference counted.

publishedJul 19, 2026
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
39th 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 19, 2026

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

01

Who is affected

Linux systems running the affected ksmbd SMB server component.

02

Real-world impact

Successful exploitation could lead to code execution, system crashes, or privilege escalation.

03

Why this severity

The CVSS v3.1 base score is 9.8 (Critical) because the vulnerability is network‑reachable, requires low attack complexity, no privileges or user interaction, and impacts confidentiality, integrity, and availability at the highest level.

04

What to do about it

official fix available
recommended steps
  1. 011. Check the currently running Linux kernel version on your system.
  2. 022. Obtain and install the latest kernel update from your Linux distribution that includes the fix for CVE-2026-64142.
  3. 033. Reboot the system to load the updated kernel.
  4. 044. After reboot, verify the kernel version to confirm the fix is applied.

NVD-referenced vendor advisory (Linux kernel patch)

05

Timeline

  1. Jul 19, 2026 · 14d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 20, 2026 · 13d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  3. Jul 30, 2026 · 3d ago
    Advisory updated
    The NVD record was last revised.
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 →