CVE-2026-99571

published 20 Nov 2026 · updated 20 Nov 2026

nvme-tcp: Validate the queue state under the queue lock in the address attribute

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2eeeaa9c1ff0c429096acc2947c296db6a56f96d, Kernel 6.2, Kernel 6.12 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: Validate the queue state under the queue lock in the address attribute Reading the "address" sysfs attribute calls kernel_getsockname() on the admin queue socket, which can race with the queue teardown during connection error recovery: a reader can observe NVME_TCP_Q_LIVE set, then block on the queue lock while nvme_tcp_free_queue() releases the socket and clears queue->sock without holding the lock. Once the reader acquires the lock it dereferences the NULL socket pointer. Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during error recovery") had the queue liveness check inside the lock. Commit 782373ba2766 ("nvme: tcp: avoid race between queue_lock lock and destroy") moved it back out because the lock itself is destroyed in nvme_tcp_free_queue(), so a reader arriving late trips mutex_destroy(). Check the queue liveness inside the queue lock, and clear queue->sock under the same lock. The teardown clears NVME_TCP_Q_LIVE under the lock well before the socket is released, so a reader either sees the bit cleared or a socket that cannot be released while it holds the lock. To also close the lock lifetime race, the queue locks are now owned by the controller: they are initialized with the queue array and only destroyed when the controller is freed, which cannot happen while a sysfs attribute read is still in progress. The queue count is computed by the NVME_TCP_OPT_NR_QUEUES() macro from the original connect options for both initialization and destruction, as reconnects may shrink ctrl->queue_count.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=782373ba27660ba7d330208cf5509ece6feb4545 <2eeeaa9c1ff0c429096acc2947c296db6a56f96d, >=6.1.118 <6.2, >=6.11.9 <6.12, >=6.6.62 <6.7, >=782373ba27660ba7d330208cf5509ece6feb4545 <0af6a8aede3121bc9662111665294731daddb13a, =4f946479b326a3cbb193f2b8368aed9269514c35, =6.12, =975cb1d2121511584695d0e47fdb90e6782da007, =e15cebc1b21856944b387f4abd03b66bd3d4f0272eeeaa9c1ff0c429096acc2947c296db6a56f96d, 6.2, 6.12, 6.7, 0af6a8aede3121bc9662111665294731daddb13a
linux-kernel: Kernel>=6.11.9 <6.12, >=6.12.0 <7.3.5, >=6.6.62 <6.7, >=6.1.118 <6.26.12, 7.3.5, 6.7, 6.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99571 severity on Zeptric[![CVE-2026-99571](https://zeptric.io/badge/cve/CVE-2026-99571.svg)](https://zeptric.io/cve/CVE-2026-99571)