Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80926ksmbd: fix use-after-free in oplock break notification

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in oplock break notification smb2_oplock_break_noti() reads opinfo->conn without any lock and dereferences it after two allocations which may sleep. When the durable handle owning the oplock is disconnected, session_fd_check() clears opinfo->conn and drops its conn reference under ci->m_lock, and the last ksmbd_conn_put() frees the connection. A break triggered by another connection that races with the teardown can then resurrect the freed connection: ksmbd_conn_get() is a plain atomic_inc, and the queued break work later dereferences the stale conn via ksmbd_conn_write(), a use-after-free reachable by any authenticated client holding a durable batch oplock. Thread the caller's inode into the notification path instead of taking a new reference on it. Every caller of oplock_break() already holds a live ksmbd_file (or an explicit ksmbd_inode_lookup_lock() reference, in the parent lease break paths) on the inode that owns the break target's oplock list, so ci cannot be freed during the call, and its lock can be taken without dereferencing opinfo->o_fp, which a concurrent close may free. Select and pin the connection under ci->m_lock, the same lock session_fd_check() and ksmbd_reopen_durable_fd() use to update opinfo->conn, so a concurrent detach either loses the race to the clear or keeps the connection alive until the notification work releases it. Transfer the reference to the work item and release it on allocation failures.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80926, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.44% · top 61% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 945a86b21b40fb17183f5b27461baa6f03e2467f – < 892f643b141aee3f7aa7c0fc61ddcb55c59f1996
    • affected 1ff58dcfcab434ebb51649da33774fbb8e1f7b67 – < 5de0527f782430b1109a447646e32033ad018a6a
    • affected e735dbd489e3ea02be78dba991056fe1138be51e – < c8279ae8df68cce9cd3b785e85f7a86c80a46e78
    • affected b003086d76968298f22e7cf62239833b5a3a06b1 – < 8cc98db4fc590e6c7d9db6529320982ee16c5d1d
    • affected b003086d76968298f22e7cf62239833b5a3a06b1 – < 0e753899627b5e28a9fea8bca98262a6f65a2452
    • affected 75e33deda658c1ab3a9336cbdb1436536f9b3660
    • affected 6.6.143 – < 6.6.158
    • affected 6.12.94 – < 6.12.111
    • affected 6.18.36 – < 6.18.51
    • affected 7.0.13 – < 7.1

  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80926 badge
[![CVE-2026-80926](https://cveledger.app/badge/CVE-2026-80926.svg)](https://cveledger.app/cve/CVE-2026-80926)

Record last updated .