CVE-2026-99571 (GCVE-0-2026-99571)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
782373ba27660ba7d330208cf5509ece6feb4545 , < 0af6a8aede3121bc9662111665294731daddb13a
(git)
Affected: 782373ba27660ba7d330208cf5509ece6feb4545 , < 2eeeaa9c1ff0c429096acc2947c296db6a56f96d (git) Affected: 4f946479b326a3cbb193f2b8368aed9269514c35 (git) Affected: 975cb1d2121511584695d0e47fdb90e6782da007 (git) Affected: e15cebc1b21856944b387f4abd03b66bd3d4f027 (git) Affected: 6.1.118 , < 6.2 (semver) Affected: 6.6.62 , < 6.7 (semver) Affected: 6.11.9 , < 6.12 (semver) |
guessed | |
| Linux | Linux |
Affected:
6.12
Unaffected: 0 , < 6.12 (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/nvme/host/tcp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "0af6a8aede3121bc9662111665294731daddb13a",
"status": "affected",
"version": "782373ba27660ba7d330208cf5509ece6feb4545",
"versionType": "git"
},
{
"lessThan": "2eeeaa9c1ff0c429096acc2947c296db6a56f96d",
"status": "affected",
"version": "782373ba27660ba7d330208cf5509ece6feb4545",
"versionType": "git"
},
{
"status": "affected",
"version": "4f946479b326a3cbb193f2b8368aed9269514c35",
"versionType": "git"
},
{
"status": "affected",
"version": "975cb1d2121511584695d0e47fdb90e6782da007",
"versionType": "git"
},
{
"status": "affected",
"version": "e15cebc1b21856944b387f4abd03b66bd3d4f027",
"versionType": "git"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.118",
"versionType": "semver"
},
{
"lessThan": "6.7",
"status": "affected",
"version": "6.6.62",
"versionType": "semver"
},
{
"lessThan": "6.12",
"status": "affected",
"version": "6.11.9",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/nvme/host/tcp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.12"
},
{
"lessThan": "6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.1.118",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.6.62",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.11.9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: Validate the queue state under the queue lock in the address attribute\n\nReading the \"address\" sysfs attribute calls kernel_getsockname() on the\nadmin queue socket, which can race with the queue teardown during\nconnection error recovery: a reader can observe NVME_TCP_Q_LIVE set,\nthen block on the queue lock while nvme_tcp_free_queue() releases the\nsocket and clears queue-\u003esock without holding the lock. Once the\nreader acquires the lock it dereferences the NULL socket pointer.\n\nCommit 76d54bf20cdc (\"nvme-tcp: don\u0027t access released socket during\nerror recovery\") had the queue liveness check inside the lock.\nCommit 782373ba2766 (\"nvme: tcp: avoid race between queue_lock lock\nand destroy\") moved it back out because the lock itself is destroyed\nin nvme_tcp_free_queue(), so a reader arriving late trips\nmutex_destroy().\n\nCheck the queue liveness inside the queue lock, and clear queue-\u003esock\nunder the same lock. The teardown clears NVME_TCP_Q_LIVE under the\nlock well before the socket is released, so a reader either sees the\nbit cleared or a socket that cannot be released while it holds the\nlock. To also close the lock lifetime race, the queue locks are now\nowned by the controller: they are initialized with the queue array and\nonly destroyed when the controller is freed, which cannot happen while\na sysfs attribute read is still in progress. The queue count is\ncomputed by the NVME_TCP_OPT_NR_QUEUES() macro from the original\nconnect options for both initialization and destruction, as reconnects\nmay shrink ctrl-\u003equeue_count."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:05.894Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/0af6a8aede3121bc9662111665294731daddb13a"
},
{
"url": "https://git.kernel.org/stable/c/2eeeaa9c1ff0c429096acc2947c296db6a56f96d"
}
],
"title": "nvme-tcp: Validate the queue state under the queue lock in the address attribute",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99571",
"datePublished": "2026-11-20T05:49:05.894Z",
"dateReserved": "2026-09-25T10:25:14.422Z",
"dateUpdated": "2026-11-20T05:49:05.894Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99571",
"date": "2026-11-21",
"epss": "0.00156",
"percentile": "0.04734"
},
"microsoft_vex": {
"current_release_date": "2026-11-20T18:08:37.000Z",
"cve": "CVE-2026-99571",
"id": "msrc_CVE-2026-99571",
"initial_release_date": "2026-11-20T18:08:37.000Z",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "nvme-tcp: Validate the queue state under the queue lock in the address attribute",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-99571.json",
"version": "1"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/nvme/host/tcp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "0af6a8aede3121bc9662111665294731daddb13a",
"status": "affected",
"version": "782373ba27660ba7d330208cf5509ece6feb4545",
"versionType": "git"
},
{
"lessThan": "2eeeaa9c1ff0c429096acc2947c296db6a56f96d",
"status": "affected",
"version": "782373ba27660ba7d330208cf5509ece6feb4545",
"versionType": "git"
},
{
"status": "affected",
"version": "4f946479b326a3cbb193f2b8368aed9269514c35",
"versionType": "git"
},
{
"status": "affected",
"version": "975cb1d2121511584695d0e47fdb90e6782da007",
"versionType": "git"
},
{
"status": "affected",
"version": "e15cebc1b21856944b387f4abd03b66bd3d4f027",
"versionType": "git"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.118",
"versionType": "semver"
},
{
"lessThan": "6.7",
"status": "affected",
"version": "6.6.62",
"versionType": "semver"
},
{
"lessThan": "6.12",
"status": "affected",
"version": "6.11.9",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/nvme/host/tcp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.12"
},
{
"lessThan": "6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: Validate the queue state under the queue lock in the address attribute\n\nReading the \"address\" sysfs attribute calls kernel_getsockname() on the\nadmin queue socket, which can race with the queue teardown during\nconnection error recovery: a reader can observe NVME_TCP_Q_LIVE set,\nthen block on the queue lock while nvme_tcp_free_queue() releases the\nsocket and clears queue-\u003esock without holding the lock. Once the\nreader acquires the lock it dereferences the NULL socket pointer.\n\nCommit 76d54bf20cdc (\"nvme-tcp: don\u0027t access released socket during\nerror recovery\") had the queue liveness check inside the lock.\nCommit 782373ba2766 (\"nvme: tcp: avoid race between queue_lock lock\nand destroy\") moved it back out because the lock itself is destroyed\nin nvme_tcp_free_queue(), so a reader arriving late trips\nmutex_destroy().\n\nCheck the queue liveness inside the queue lock, and clear queue-\u003esock\nunder the same lock. The teardown clears NVME_TCP_Q_LIVE under the\nlock well before the socket is released, so a reader either sees the\nbit cleared or a socket that cannot be released while it holds the\nlock. To also close the lock lifetime race, the queue locks are now\nowned by the controller: they are initialized with the queue array and\nonly destroyed when the controller is freed, which cannot happen while\na sysfs attribute read is still in progress. The queue count is\ncomputed by the NVME_TCP_OPT_NR_QUEUES() macro from the original\nconnect options for both initialization and destruction, as reconnects\nmay shrink ctrl-\u003equeue_count."
}
],
"id": "CVE-2026-99571",
"lastModified": "2026-11-20T06:17:48.093",
"metrics": {},
"published": "2026-11-20T06:17:48.093",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0af6a8aede3121bc9662111665294731daddb13a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2eeeaa9c1ff0c429096acc2947c296db6a56f96d"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T11:24:47+00:00",
"cve": "CVE-2026-99571",
"id": "CVE-2026-99571",
"initial_release_date": "2026-11-20T05:49:05.894000+00:00",
"product_status:known_affected": "111",
"product_status:known_not_affected": "93",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via race condition in nvme-tcp address attribute",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99571.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-20T17:46:28Z",
"cve": "CVE-2026-99571",
"id": "CVE-2026-99571",
"initial_release_date": "2026-11-20T17:46:28Z",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-99571",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-99571.json",
"version": "2"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.