From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist()
Date: Fri, 4 Sep 2026 17:11:52 +0200 [thread overview]
Message-ID: <2026090411-CVE-2026-80813-ff96@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-80813 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 61c9967cd63448292a64f9ee9aeb6e2053e3a624 and fixed in 6.18.47 with commit 61dc1a37e04d4003a19095f54883358330034a39
Issue introduced in 6.13 with commit 61c9967cd63448292a64f9ee9aeb6e2053e3a624 and fixed in 7.1.11 with commit 2bc1e33ff6a558c8ceef7c0077f3ef70a15fcba2
Issue introduced in 6.13 with commit 61c9967cd63448292a64f9ee9aeb6e2053e3a624 and fixed in 7.2.1 with commit 123d664ac98d6f3464462ad4a530474b91ba9890
Issue introduced in 6.13 with commit 61c9967cd63448292a64f9ee9aeb6e2053e3a624 and fixed in 7.3-rc1 with commit 79aba4c9403419d822972d2851f2a96a2c0531cf
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80813
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/nvme/target/admin-cmd.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/61dc1a37e04d4003a19095f54883358330034a39
https://git.kernel.org/stable/c/2bc1e33ff6a558c8ceef7c0077f3ef70a15fcba2
https://git.kernel.org/stable/c/123d664ac98d6f3464462ad4a530474b91ba9890
https://git.kernel.org/stable/c/79aba4c9403419d822972d2851f2a96a2c0531cf
reply other threads:[~2026-09-04 15:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026090411-CVE-2026-80813-ff96@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.