Answer in brief
CVE-2026-80926 records a Critical severity (CVSS 9.8) vulnerability in ksmbd: fix use-after-free in oplock break notification. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=945a86b21b40fb17183f5b27461baa6f03e2467f <892f643b141aee3f7aa7c0fc61ddcb55c59f1996 || >=1ff58dcfcab434ebb51649da33774fbb8e1f7b67 <5de0527f782430b1109a447646e32033ad018a6a || >=e735dbd489e3ea02be78dba991056fe1138be51e <c8279ae8df68cce9cd3b785e85f7a86c80a46e78 || >=b003086d76968298f22e7cf62239833b5a3a06b1 <8cc98db4fc590e6c7d9db6529320982ee16c5d1d || >=b003086d76968298f22e7cf62239833b5a3a06b1 <0e753899627b5e28a9fea8bca98262a6f65a2452 || 75e33deda658c1ab3a9336cbdb1436536f9b3660 || >=6.6.143 <6.6.158 || >=6.12.94 <6.12.111 || >=6.18.36 <6.18.51 || >=7.0.13 <7.1 | 892f643b141aee3f7aa7c0fc61ddcb55c59f1996, 5de0527f782430b1109a447646e32033ad018a6a, c8279ae8df68cce9cd3b785e85f7a86c80a46e78, 8cc98db4fc590e6c7d9db6529320982ee16c5d1d, 0e753899627b5e28a9fea8bca98262a6f65a2452, 6.6.158, 6.12.111, 6.18.51, 7.1 |
| Linux/Linuxgeneric | 7.1 | Not reported |
| Linux/Linuxgeneric | >=e735dbd489e3ea02be78dba991056fe1138be51e <c8279ae8df68cce9cd3b785e85f7a86c80a46e78 || >=b003086d76968298f22e7cf62239833b5a3a06b1 <8cc98db4fc590e6c7d9db6529320982ee16c5d1d || >=b003086d76968298f22e7cf62239833b5a3a06b1 <0e753899627b5e28a9fea8bca98262a6f65a2452 || 945a86b21b40fb17183f5b27461baa6f03e2467f || 1ff58dcfcab434ebb51649da33774fbb8e1f7b67 || 75e33deda658c1ab3a9336cbdb1436536f9b3660 || >=6.18.36 <6.18.51 || >=6.6.143 <6.7 || >=6.12.94 <6.13 || >=7.0.13 <7.1 | c8279ae8df68cce9cd3b785e85f7a86c80a46e78, 8cc98db4fc590e6c7d9db6529320982ee16c5d1d, 0e753899627b5e28a9fea8bca98262a6f65a2452, 6.18.51, 6.7, 6.13, 7.1 |
| Linux/Linuxgeneric | >=1ff58dcfcab434ebb51649da33774fbb8e1f7b67 <5de0527f782430b1109a447646e32033ad018a6a || >=e735dbd489e3ea02be78dba991056fe1138be51e <c8279ae8df68cce9cd3b785e85f7a86c80a46e78 || >=b003086d76968298f22e7cf62239833b5a3a06b1 <8cc98db4fc590e6c7d9db6529320982ee16c5d1d || >=b003086d76968298f22e7cf62239833b5a3a06b1 <0e753899627b5e28a9fea8bca98262a6f65a2452 || 945a86b21b40fb17183f5b27461baa6f03e2467f || 75e33deda658c1ab3a9336cbdb1436536f9b3660 || >=6.12.94 <6.12.111 || >=6.18.36 <6.18.51 || >=6.6.143 <6.7 || >=7.0.13 <7.1 | 5de0527f782430b1109a447646e32033ad018a6a, c8279ae8df68cce9cd3b785e85f7a86c80a46e78, 8cc98db4fc590e6c7d9db6529320982ee16c5d1d, 0e753899627b5e28a9fea8bca98262a6f65a2452, 6.12.111, 6.18.51, 6.7, 7.1 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.