ksmbd: fix use-after-free of conn->preauth_info in concurrent SMB2 NEGOTIATE
Summary
| CVE | CVE-2026-72422 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:22:15 UTC |
| Updated | 2026-08-17 06:19:09 UTC |
| 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). |
Risk And Classification
Primary CVSS: v3.1 9.8 CRITICAL from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.006680000 probability, percentile 0.489070000 (date 2026-08-17)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected dd4e4c811898410e6a3ae3b63207b7c542860907 c7bef84740d1d57848c74f6f5b996606e43ea4fe git | Not specified |
| CNA | Linux | Linux | affected aa7253c2393f6dcd6a1468b0792f6da76edad917 d0a469122e7bf8338fec1949fb1e8e1290ed8caa git | Not specified |
| CNA | Linux | Linux | affected aa7253c2393f6dcd6a1468b0792f6da76edad917 7470511d085af1c7a043a60e53d52b512d5a10b1 git | Not specified |
| CNA | Linux | Linux | affected aa7253c2393f6dcd6a1468b0792f6da76edad917 16a1ecf39c217e3d164bd32ef2a4f650abc067fa git | Not specified |
| CNA | Linux | Linux | affected aa7253c2393f6dcd6a1468b0792f6da76edad917 77bb0bbfcc4e777ca653174689e5e363f8ee63d1 git | Not specified |
| CNA | Linux | Linux | affected aa7253c2393f6dcd6a1468b0792f6da76edad917 1c89da3baa2b1f269178afa87dc30479b8535776 git | Not specified |
| CNA | Linux | Linux | affected aa7253c2393f6dcd6a1468b0792f6da76edad917 0c054227479ed7e36ebccb3a558bc0ef698264f6 git | Not specified |
| CNA | Linux | Linux | affected 8a8315a5960bd2b5ffc75f44fc089e57c3b17c44 git | Not specified |
| CNA | Linux | Linux | affected ff20f1875889dbe4a67c9298e609d7c88cf6456d git | Not specified |
| CNA | Linux | Linux | affected 5.15.61 5.15.212 semver | Not specified |
| CNA | Linux | Linux | affected 5.18.18 5.19 semver | Not specified |
| CNA | Linux | Linux | affected 5.19.2 5.20 semver | Not specified |
| CNA | Linux | Linux | affected 6.0 | Not specified |
| CNA | Linux | Linux | unaffected 6.0 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.212 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.178 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.145 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.97 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.40 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.5 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/77bb0bbfcc4e777ca653174689e5e363f8ee63d1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d0a469122e7bf8338fec1949fb1e8e1290ed8caa | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1c89da3baa2b1f269178afa87dc30479b8535776 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/16a1ecf39c217e3d164bd32ef2a4f650abc067fa | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c7bef84740d1d57848c74f6f5b996606e43ea4fe | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0c054227479ed7e36ebccb3a558bc0ef698264f6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7470511d085af1c7a043a60e53d52b512d5a10b1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.