CVE-2026-99441
nvmet-auth: serialize access to DH-HMAC-CHAP state to fix UAF
What happened?
In the Linux kernel, the following vulnerability has been resolved:
nvmet-auth: serialize access to DH-HMAC-CHAP state to fix UAF
A REPLY AUTH_SEND command can derive a dhchap_skey key while a concurrent AUTH_RECEIVE command observing this REPLY state executes the failure path and frees that key. The REPLY command then continues and writes into freed memory, causing a use-after-free. KASAN reports it as:
BUG: KASAN: slab-use-after-free in __sha256_final Write of size 4 at addr ffff88800359c540 ... nvmet_auth_sq_free (drivers/nvme/target/auth.c:237) nvmet_execute_auth_receive (drivers/nvme/target/fabrics-cmd-auth.c:621)
Add a mutex to each submission queue to serialize authentication commands and timeout handling. Unlock the mutex before completing requests and ignore outdated timeout callbacks. Limit timeout delays to prevent immediate expiry on 32-bit kernels.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 7a277c37d3522e9b2777d762bbbcecafae2b1f8d to < 4074511c39abed4b763392f0430bf84f166abb4c; affected: 7a277c37d3522e9b2777d762bbbcecafae2b1f8d to < edb4f7bcffdb768103c561c588de310f34dd26ba; affected: 7a277c37d3522e9b2777d762bbbcecafae2b1f8d to < 35f55810ee2410815d687ff00fb8412d63ab2899; affected: 7a277c37d3522e9b2777d762bbbcecafae2b1f8d to < 53f6efe00cea0c0cf7bd99debe3cdac8567170b5 | See vendor advisory |
| LinuxLinux | affected: 6.0; unaffected: 0 to < 6.0; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.63 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99441
- https://git.kernel.org/stable/c/4074511c39abed4b763392f0430bf84f166abb4c
- https://git.kernel.org/stable/c/edb4f7bcffdb768103c561c588de310f34dd26ba
- https://git.kernel.org/stable/c/35f55810ee2410815d687ff00fb8412d63ab2899
- https://git.kernel.org/stable/c/53f6efe00cea0c0cf7bd99debe3cdac8567170b5