Back to CVE records
Critical 9.8Published Aug 15, 2026

CVE-2026-72422ksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE

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.

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).

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
Aug 17, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from dd4e4c811898410e6a3ae3b63207b7c542860907 before c7bef84740d1d57848c74f6f5b996606e43ea4fe; from aa7253c2393f6dcd6a1468b0792f6da76edad917 before d0a469122e7bf8338fec1949fb1e8e1290ed8caa; from aa7253c2393f6dcd6a1468b0792f6da76edad917 before 7470511d085af1c7a043a60e53d52b512d5a10b1; from aa7253c2393f6dcd6a1468b0792f6da76edad917 before 16a1ecf39c217e3d164bd32ef2a4f650abc067fa; from aa7253c2393f6dcd6a1468b0792f6da76edad917 before 77bb0bbfcc4e777ca653174689e5e363f8ee63d1; from aa7253c2393f6dcd6a1468b0792f6da76edad917 before 1c89da3baa2b1f269178afa87dc30479b8535776; from aa7253c2393f6dcd6a1468b0792f6da76edad917 before 0c054227479ed7e36ebccb3a558bc0ef698264f6; 8a8315a5960bd2b5ffc75f44fc089e57c3b17c44; and 4 more ranges
CNA record

References

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.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.