From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-90230: nvmet: fix heap out-of-bounds read in nvmet_auth_negotiate()
Date: Thu, 17 Sep 2026 17:11:00 +0100 [thread overview]
Message-ID: <2026091740-CVE-2026-90230-12fc@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nvmet: fix heap out-of-bounds read in nvmet_auth_negotiate()
nvmet_execute_auth_send() allocates the DH-HMAC-CHAP message buffer with
the host-supplied transfer length (tl) and hands it to
nvmet_auth_negotiate() without passing tl along. nvmet_auth_negotiate()
then reads the negotiate header and, for each of the halen hash
identifiers and dhlen DH group identifiers, indexes into the fixed
idlist[60] array (hashes at idlist[0..halen), groups at idlist[30..]).
Neither the transfer length nor halen/dhlen is validated. A malicious or
non-conformant host can report a tl smaller than the negotiate structure,
or a halen/dhlen larger than the array (both are u8, up to 255), making
the loops read past the end of the allocated buffer (heap out-of-bounds
read). The sibling nvmet_auth_reply() already validates tl against the
structure size; the negotiate path did not.
Pass tl into nvmet_auth_negotiate(), reject a tl that does not cover the
negotiate data plus one full protocol descriptor, and reject halen/dhlen
larger than NVME_AUTH_DHCHAP_MAX_DH_IDS.
The Linux kernel CVE team has assigned CVE-2026-90230 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.0 with commit db1312dd95488b5e6ff362ff66fcf953a46b1821 and fixed in 6.6.157 with commit 89ff11b72f38976f3b5aea23a5228ee05e277209
Issue introduced in 6.0 with commit db1312dd95488b5e6ff362ff66fcf953a46b1821 and fixed in 6.12.110 with commit aaac783950b17c57df9b6f7344747cacb1a407ed
Issue introduced in 6.0 with commit db1312dd95488b5e6ff362ff66fcf953a46b1821 and fixed in 6.18.52 with commit c38a8186326799957d293d370136c128cd113916
Issue introduced in 6.0 with commit db1312dd95488b5e6ff362ff66fcf953a46b1821 and fixed in 7.2.6 with commit 7b81e4d2230e3d2d372c826180c4ef0efc244f31
Issue introduced in 6.0 with commit db1312dd95488b5e6ff362ff66fcf953a46b1821 and fixed in 7.3-rc1 with commit 5bb96cc218835769ab74ec7f3ea2bf81fbffe955
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-90230
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/fabrics-cmd-auth.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/89ff11b72f38976f3b5aea23a5228ee05e277209
https://git.kernel.org/stable/c/aaac783950b17c57df9b6f7344747cacb1a407ed
https://git.kernel.org/stable/c/c38a8186326799957d293d370136c128cd113916
https://git.kernel.org/stable/c/7b81e4d2230e3d2d372c826180c4ef0efc244f31
https://git.kernel.org/stable/c/5bb96cc218835769ab74ec7f3ea2bf81fbffe955
reply other threads:[~2026-09-17 16:21 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=2026091740-CVE-2026-90230-12fc@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.