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

CVE-2025-68817

A critical use‑after‑free bug in the Linux kernel’s SMB server (ksmbd) can let an attacker crash the system or potentially execute code. The flaw occurs when many connections are opened and closed at the same time, freeing a connection object while another still uses it.

publishedJan 13, 2026
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
33th 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, especially version 6.6 and earlier, used in many servers and embedded devices.

02

Real-world impact

An attacker could cause the kernel to crash, leading to denial of service, or could potentially run arbitrary code if the use‑after‑free is exploited, compromising confidentiality, integrity, and availability of the affected system.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability requires no authentication, no user interaction, and can fully compromise confidentiality, integrity, and availability. The low attack complexity and high impact make it critical.

04

What to do about it

official fix available
recommended steps
  1. 01Update the Linux kernel to a version that includes the ksmbd use‑after‑free fix.
  2. 02Verify the kernel version after the update.
  3. 03Restart services that rely on the kernel if necessary.

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

05

Timeline

  1. Jan 13, 2026 · Jan 13, 2026
    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 →