CVE-2026-31444ksmbd: fix use-after-free and NULL deref in smb_grant_oplock()
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. 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 and NULL deref in smb_grant_oplock() smb_grant_oplock() has two issues in the oplock publication sequence: 1) opinfo is linked into ci->m_op_list (via opinfo_add) before add_lease_global_list() is called. If add_lease_global_list() fails (kmalloc returns NULL), the error path frees the opinfo via __free_opinfo() while it is still linked in ci->m_op_list. Concurrent m_op_list readers (opinfo_get_list, or direct iteration in smb_break_all_levII_oplock) dereference the freed node. 2) opinfo->o_fp is assigned after add_lease_global_list() publishes the opinfo on the global lease list. A concurrent find_same_lease_key() can walk the lease list and dereference opinfo->o_fp->f_ci while o_fp is still NULL. Fix by restructuring the publication sequence to eliminate post-publish failure: - Set opinfo->o_fp before any list publication (fixes NULL deref). - Preallocate lease_table via alloc_lease_table() before opinfo_add() so add_lease_global_list() becomes infallible after publication. - Keep the original m_op_list publication order (opinfo_add before lease list) so concurrent opens via same_client_has_lease() and opinfo_get_list() still see the in-flight grant. - Use opinfo_put() instead of __free_opinfo() on err_out so that the RCU-deferred free path is used. This also requires splitting add_lease_global_list() to take a preallocated lease_table and changing its return type from int to void, since it can no longer fail.
- 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
- Analyzed
- Record last updated
- Aug 5, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 302fef75512b2c8329a3f5efab1ae7ba2562387a builds before 9e785f004cbc56390479b77375726ea9b0d1a8a6; 08aa9f3c8cf4d0bee44df540dfe34e8d64069f2c builds before 7de55bba69cbf0f9280daaea385daf08bc076121; from 1d6abf145615dbfe267ce3b0a271f95e3780e18e before a5c6f6d6ceefed2d5210ee420fb75f8362461f46; from ce8507ee82c888126d8e7565e27c016308d24cde before 6d7e5a918c1d0aad06db0e17677b66fc9a471021; from 1dfd062caa165ec9d7ee0823087930f3ab8a6294 before 48623ec358c1c600fa1e38368746f933e0f1a617 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.12.78 before 6.12.80; from 6.18.19 before 6.18.21; from 6.19.9 before 6.19.11; 6.6.130; 7.0; 7.0 | NVD |
References
- https://git.kernel.org/stable/c/9e785f004cbc56390479b77375726ea9b0d1a8a6patch
- https://git.kernel.org/stable/c/7de55bba69cbf0f9280daaea385daf08bc076121patch
- https://git.kernel.org/stable/c/a5c6f6d6ceefed2d5210ee420fb75f8362461f46patch
- https://git.kernel.org/stable/c/6d7e5a918c1d0aad06db0e17677b66fc9a471021patch
- https://git.kernel.org/stable/c/48623ec358c1c600fa1e38368746f933e0f1a617patch
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.