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

CVE-2026-80926

A critical use-after-free vulnerability (CVE-2026-80926) in the Linux kernel's ksmbd subsystem allows a race condition where a freed connection can be reused after being detached, potentially leading to arbitrary code execution. The bug occurs because ksmbd_oplock_break_notify() dereferences opiniono->conn without proper locking while other threads may have already freed it.

publishedSep 11, 2026
last modifiedSep 13, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
6th 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 Oct 13, 2026

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

01

Who is affected

Any authenticated client holding a durable batch oplock can be exploited

02

Real-world impact

An attacker could trigger a break operation that resurrects a previously freed connection, causing undefined behavior or privilege escalation in the SMB share subsystem.

03

Why this severity

Critical (CVSS 9.8) due to remote code execution potential through a race condition involving concurrent detach and break notifications.

04

What to do about it

official fix available
recommended steps
  1. 01Update the Linux kernel and ksmbd package to the patched version that resolves CVE-2026-80926
  2. 02Rebuild or reinstall the ksmbd component after applying the patch
  3. 03Verify the system is running the updated version that includes the fix
interim mitigations
  • If an immediate patch is not available, apply the in-place fixes described in the NVD advisory: ensure the caller's inode is threaded into the notification path and that connections are pinned under ci->m_lock before updating opiniono->conn to prevent use-after-free.

NVD-referenced vendor advisory (CVE-2026-80926 fix in Linux kernel)

05

Timeline

  1. Sep 11, 2026 · 2d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Sep 13, 2026 · 4h 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 →