nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist()
In the Linux kernel, the following vulnerability has been resolved: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() When a host issues an Identify command with CNS 07h (Active Namespace ID List for a specific I/O Command Set), nvmet_execute_identify_nslist() is called with match_css set. The command-set filter dereferences req->ns, but this handler never calls nvmet_req_find_ns(), so req->ns is always NULL (nvmet_req_init() resets it to NULL). As soon as an enabled namespace with an NSID greater than the requested value exists, req->ns->csi dereferences a NULL pointer and oopses. Besides the crash, the comparison is logically wrong: to filter the list by command set it must test the command set of the namespace being iterated, not a single fixed value. Use the loop variable ns->csi.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.47, 7.1.11, 7.2.1
- CVEs
- CVE-2026-80813
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:33 UTC · Revision 1
Source evidence
nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist()
core-osv · Original sourcePublished 4 Sept 2026, 15:13 UTC
In the Linux kernel, the following vulnerability has been resolved: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() When a host issues an Identify command with CNS 07h (Active Namespace ID List for a specific I/O Command Set), nvmet_execute_identify_nslist() is called with match_css set. The command-set filter dereferences req->ns, but this handler never calls nvmet_req_find_ns(), so req->ns is always NULL (nvmet_req_init() resets it to NULL). As soon as an enabled namespace with an NSID greater than the requested value exists, req->ns->csi dereferences a NULL pointer and oopses. Besides the crash, the comparison is logically wrong: to filter the list by command set it must test the command set of the namespace being iterated, not a single fixed value. Use the loop variable ns->csi.
osv:CVE-2026-80813
Kernel
Fixed versions: 6.18.47, 7.1.11, 7.2.1
Complete source record
{
"id": "b7171a61434b14a0b76fe67e921adf1a6a88b7894f1487a3d01b60749f1a8fd3",
"url": "https://osv.dev/vulnerability/CVE-2026-80813",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() When a host issues an Identify command with CNS 07h (Active Namespace ID List for a specific I/O Command Set), nvmet_execute_identify_nslist() is called with match_css set. The command-set filter dereferences req->ns, but this handler never calls nvmet_req_find_ns(), so req->ns is always NULL (nvmet_req_init() resets it to NULL). As soon as an enabled namespace with an NSID greater than the requested value exists, req->ns->csi dereferences a NULL pointer and oopses. Besides the crash, the comparison is logically wrong: to filter the list by command set it must test the command set of the namespace being iterated, not a single fixed value. Use the loop variable ns->csi.",
"evidence": "osv:CVE-2026-80813",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.47",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.11",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-80813",
"aliases": [
"CVE-2026-80813"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "61c9967cd63448292a64f9ee9aeb6e2053e3a624"
},
{
"fixed": "61dc1a37e04d4003a19095f54883358330034a39"
},
{
"fixed": "2bc1e33ff6a558c8ceef7c0077f3ef70a15fcba2"
},
{
"fixed": "123d664ac98d6f3464462ad4a530474b91ba9890"
},
{
"fixed": "79aba4c9403419d822972d2851f2a96a2c0531cf"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80813.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.47"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "7.2.0"
},
{
"fixed": "7.2.1"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80813.json"
}
}
],
"modified": "2026-10-28T02:30:37.832921444Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/123d664ac98d6f3464462ad4a530474b91ba9890",
"https://git.kernel.org/stable/c/2bc1e33ff6a558c8ceef7c0077f3ef70a15fcba2",
"https://git.kernel.org/stable/c/61dc1a37e04d4003a19095f54883358330034a39",
"https://git.kernel.org/stable/c/79aba4c9403419d822972d2851f2a96a2c0531cf",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80813.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-80813",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80813.json"
}
},
"related_cves": [
{
"value": "CVE-2026-80813",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505360,
"published_at": "2026-09-04T15:13:33.761+00:00"
}