CVE-2026-72422ksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE
- 9.8CriticalCVSS base score
- 0.72%Exploitation in 30 daysEPSS · top 46% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE conn->preauth_info is shared connection state (struct preauth_integrity_info, kmalloc-96) that is allocated and freed by the SMB2 NEGOTIATE handler and read by the response send path. smb2_handle_negotiate() allocates conn->preauth_info, and on a deassemble_neg_contexts() failure kfrees it and sets it to NULL. Both the allocation and the free/NULL happen under ksmbd_conn_lock(conn) (the connection srv_mutex), which is held across the whole handler body. The response send path smb3_preauth_hash_rsp(), called from the send: block of __handle_ksmbd_work(), reads conn->preauth_info and dereferences conn->preauth_info->Preauth_HashValue (via ksmbd_gen_preauth_integrity_hash()) without taking conn_lock. When a client drives two SMB2 NEGOTIATE requests on the same connection, one worker can free conn->preauth_info on the failing-negotiate path while a concurrent send-path worker is reading it, producing a slab use-after-free read (KASAN-confirmed). The send-path read tested conn->preauth_info for NULL but raced with the free that occurs between the NULL check and the dereference, so the NULL guard alone does not close the window. Serialize the NEGOTIATE-branch read in smb3_preauth_hash_rsp() under ksmbd_conn_lock(conn) and re-check conn->preauth_info inside the lock. Because the negotiate handler holds conn_lock across its kfree + NULL assignment, a reader that also takes conn_lock either runs fully before the allocation or fully after the NULL store, and can never observe the freed-but-not-yet-NULLed pointer. ksmbd_gen_preauth_integrity_hash() takes no locks itself (it only computes a SHA-512 over the buffer), so no lock-ordering inversion is introduced, and conn_lock is a sleepable mutex which is safe on this send path (it already performs network I/O).
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 days later
· 2 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.72% · top 46% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected dd4e4c811898410e6a3ae3b63207b7c542860907 – < c7bef84740d1d57848c74f6f5b996606e43ea4fe
- affected aa7253c2393f6dcd6a1468b0792f6da76edad917 – < d0a469122e7bf8338fec1949fb1e8e1290ed8caa
- affected aa7253c2393f6dcd6a1468b0792f6da76edad917 – < 7470511d085af1c7a043a60e53d52b512d5a10b1
- affected aa7253c2393f6dcd6a1468b0792f6da76edad917 – < 16a1ecf39c217e3d164bd32ef2a4f650abc067fa
- affected aa7253c2393f6dcd6a1468b0792f6da76edad917 – < 77bb0bbfcc4e777ca653174689e5e363f8ee63d1
- affected aa7253c2393f6dcd6a1468b0792f6da76edad917 – < 1c89da3baa2b1f269178afa87dc30479b8535776
- affected aa7253c2393f6dcd6a1468b0792f6da76edad917 – < 0c054227479ed7e36ebccb3a558bc0ef698264f6
- affected 8a8315a5960bd2b5ffc75f44fc089e57c3b17c44
- affected ff20f1875889dbe4a67c9298e609d7c88cf6456d
- affected 5.15.61 – < 5.15.212
- affected 5.18.18 – < 5.19
- affected 5.19.2 – < 5.20
- affected 6.0
- unaffected < 6.0
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/c7bef84740d1d57848c74f6f5b996606e43ea4fe (opens in a new tab)
- https://git.kernel.org/stable/c/d0a469122e7bf8338fec1949fb1e8e1290ed8caa (opens in a new tab)
- https://git.kernel.org/stable/c/7470511d085af1c7a043a60e53d52b512d5a10b1 (opens in a new tab)
- https://git.kernel.org/stable/c/16a1ecf39c217e3d164bd32ef2a4f650abc067fa (opens in a new tab)
- https://git.kernel.org/stable/c/77bb0bbfcc4e777ca653174689e5e363f8ee63d1 (opens in a new tab)
- https://git.kernel.org/stable/c/1c89da3baa2b1f269178afa87dc30479b8535776 (opens in a new tab)
- https://git.kernel.org/stable/c/0c054227479ed7e36ebccb3a558bc0ef698264f6 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59321 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72422)Record last updated .