{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99441","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.415Z","datePublished":"2026-11-19T14:41:25.953Z","dateUpdated":"2026-11-22T11:08:17.725Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:08:17.725Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-auth: serialize access to DH-HMAC-CHAP state to fix UAF\n\nA REPLY AUTH_SEND command can derive a dhchap_skey key while a\nconcurrent AUTH_RECEIVE command observing this REPLY state executes\nthe failure path and frees that key. The REPLY command then continues\nand writes into freed memory, causing a use-after-free. KASAN reports\nit as:\n\n  BUG: KASAN: slab-use-after-free in __sha256_final\n  Write of size 4 at addr ffff88800359c540\n  ...\n  nvmet_auth_sq_free (drivers/nvme/target/auth.c:237)\n  nvmet_execute_auth_receive (drivers/nvme/target/fabrics-cmd-auth.c:621)\n\nAdd a mutex to each submission queue to serialize authentication\ncommands and timeout handling. Unlock the mutex before completing\nrequests and ignore outdated timeout callbacks. Limit timeout delays\nto prevent immediate expiry on 32-bit kernels."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:A - A Fibre Channel initiator triggers the race with two in-flight commands on one submission queue: an Authentication Send carrying a DH-HMAC-CHAP Reply, and an Authentication Receive. lpfc_nvmet_unsol_fcp_event delivers each FCP IU to nvmet_fc_rcv_fcp_req, which reaches nvmet_execute_auth_send and nvmet_execute_auth_receive; the attacker has to be on that FC SAN.\nAC:L - The attacker submits both commands. nvmet_auth_reply stays in nvmet_auth_ctrl_sesskey, with dhchap_step still NVME_AUTH_DHCHAP_MESSAGE_REPLY, while nvme_auth_gen_session_key blocks in crypto_wait_req on the DH shared secret. The receive runs nvmet_execute_auth_receive on lpfc's phba->wq or another CQ during that wait.\nPR:N - nvmet_parse_fabrics_admin_cmd dispatches Authentication Send and Authentication Receive without nvmet_check_auth_status. nvmet_auth_ctrl_sesskey allocates sq->dhchap_skey before nvmet_auth_reply's crypto_memneq checks the host response, so the DHCHAP secret is unverified; Connect only matches the self-asserted hostnqn in nvmet_host_allowed.\nUI:N - The initiator sends Connect, the DH-HMAC-CHAP Negotiate on Authentication Send, the Authentication Receive that sets dhchap_step to REPLY, and then the overlapping Reply and Receive on the same queue.\nS:U - The corrupted object is sq->dhchap_skey on the nvmet host's kernel heap, the same security authority as the target. This is a kernel memory corruption in that host.\nC:H - The receive failure path calls nvmet_auth_sq_free, which kfree's sq->dhchap_skey and sq->dhchap_c1 while nvmet_auth_reply still uses them. nvme_auth_hash writes the digest through the freed skey, and nvmet_auth_host_hash passes it to nvme_auth_augmented_challenge, so a reclaimed slab is read as key material.\nI:H - __sha256_final's put_unaligned_be32 stores the session-key digest into the buffer nvmet_auth_ctrl_sesskey allocated as sq->dhchap_skey after the concurrent receive has freed it. That write hits a reclaimed hash-sized kmalloc slot (32 bytes for the default SHA-256) and is a kernel heap write primitive.\nA:H - The digest store into the freed sq->dhchap_skey slab is a kernel use-after-free that oopses the target, and the receive's FAILURE1 arm also calls nvmet_ctrl_fatal_error, which sets NVME_CSTS_CFS and queues nvmet_fatal_error_handler to delete the controller."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/target/auth.c","drivers/nvme/target/fabrics-cmd-auth.c","drivers/nvme/target/nvmet.h"],"versions":[{"version":"7a277c37d3522e9b2777d762bbbcecafae2b1f8d","lessThan":"4074511c39abed4b763392f0430bf84f166abb4c","status":"affected","versionType":"git"},{"version":"7a277c37d3522e9b2777d762bbbcecafae2b1f8d","lessThan":"edb4f7bcffdb768103c561c588de310f34dd26ba","status":"affected","versionType":"git"},{"version":"7a277c37d3522e9b2777d762bbbcecafae2b1f8d","lessThan":"35f55810ee2410815d687ff00fb8412d63ab2899","status":"affected","versionType":"git"},{"version":"7a277c37d3522e9b2777d762bbbcecafae2b1f8d","lessThan":"53f6efe00cea0c0cf7bd99debe3cdac8567170b5","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/target/auth.c","drivers/nvme/target/fabrics-cmd-auth.c","drivers/nvme/target/nvmet.h"],"versions":[{"version":"6.0","status":"affected"},{"version":"0","lessThan":"6.0","status":"unaffected","versionType":"semver"},{"version":"6.12.117","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.63","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.2","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.12.117"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.18.63"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"7.3.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"7.4-rc1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/4074511c39abed4b763392f0430bf84f166abb4c"},{"url":"https://git.kernel.org/stable/c/edb4f7bcffdb768103c561c588de310f34dd26ba"},{"url":"https://git.kernel.org/stable/c/35f55810ee2410815d687ff00fb8412d63ab2899"},{"url":"https://git.kernel.org/stable/c/53f6efe00cea0c0cf7bd99debe3cdac8567170b5"}],"title":"nvmet-auth: serialize access to DH-HMAC-CHAP state to fix UAF","x_generator":{"engine":"bippy-1.2.0"}}}}