Skip to content
Threat Brief

← All advisories

CVE-2026-99571

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 6.1.118 before 6.26.2CVE Program
LinuxLinuxfrom 6.11.9 before 6.126.12CVE Program
LinuxLinuxfrom 6.6.62 before 6.76.7CVE Program
LinuxLinuxfrom 782373ba27660ba7d330208cf5509ece6feb4545 before 0af6a8aede3121bc9662111665294731daddb13a0af6a8aede3121bc9662111665294731daddb13aCVE Program
LinuxLinuxfrom 782373ba27660ba7d330208cf5509ece6feb4545 before 2eeeaa9c1ff0c429096acc2947c296db6a56f96d2eeeaa9c1ff0c429096acc2947c296db6a56f96dCVE Program
LinuxLinux4f946479b326a3cbb193f2b8368aed9269514c35Not documentedCVE Program
LinuxLinux6.12Not documentedCVE Program
LinuxLinux975cb1d2121511584695d0e47fdb90e6782da007Not documentedCVE Program
LinuxLinuxe15cebc1b21856944b387f4abd03b66bd3d4f027Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references