CVE-2026-80926ksmbd: fix use-after-free in oplock break notification
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 945a86b21b40fb17183f5b27461baa6f03e2467f builds before 892f643b141aee3f7aa7c0fc61ddcb55c59f1996; from 1ff58dcfcab434ebb51649da33774fbb8e1f7b67 before 5de0527f782430b1109a447646e32033ad018a6a; from e735dbd489e3ea02be78dba991056fe1138be51e before c8279ae8df68cce9cd3b785e85f7a86c80a46e78; from b003086d76968298f22e7cf62239833b5a3a06b1 before 8cc98db4fc590e6c7d9db6529320982ee16c5d1d; from b003086d76968298f22e7cf62239833b5a3a06b1 before 0e753899627b5e28a9fea8bca98262a6f65a2452; 75e33deda658c1ab3a9336cbdb1436536f9b3660; from 6.6.143 before 6.6.158; from 6.12.94 before 6.12.111; and 2 more ranges | CNA record |
References
- https://git.kernel.org/stable/c/892f643b141aee3f7aa7c0fc61ddcb55c59f1996
- https://git.kernel.org/stable/c/5de0527f782430b1109a447646e32033ad018a6a
- https://git.kernel.org/stable/c/c8279ae8df68cce9cd3b785e85f7a86c80a46e78
- https://git.kernel.org/stable/c/8cc98db4fc590e6c7d9db6529320982ee16c5d1d
- https://git.kernel.org/stable/c/0e753899627b5e28a9fea8bca98262a6f65a2452
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.