From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-90227: nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed()
Date: Thu, 17 Sep 2026 17:10:57 +0100 [thread overview]
Message-ID: <2026091739-CVE-2026-90227-bbd7@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed()
Unlike IO_CMD / IO64_CMD, NVME_IOCTL_SUBMIT_IO never calls
nvme_cmd_allowed(). Unprivileged callers can thus issue I/O on a
partition device or write through a read-only file descriptor.
Pass flags and open_for_write through and reject disallowed commands
with -EACCES.
The Linux kernel CVE team has assigned CVE-2026-90227 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.157 with commit c35cd98eed1a863e8dd51073953563cd8c907f68
Fixed in 6.12.110 with commit 95b0591d51dbf9e618d7845883d535e88ad7c8af
Fixed in 6.18.52 with commit 736b7c6adc7a65c4411beff197b6a634f7a6ca27
Fixed in 7.2.6 with commit b116e9dae433ff631f94c36c61a7a78fe400ed1e
Fixed in 7.3-rc1 with commit b53d495c7f0db46b6748b5ade48371a10dd5d3bc
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-90227
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/host/ioctl.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/c35cd98eed1a863e8dd51073953563cd8c907f68
https://git.kernel.org/stable/c/95b0591d51dbf9e618d7845883d535e88ad7c8af
https://git.kernel.org/stable/c/736b7c6adc7a65c4411beff197b6a634f7a6ca27
https://git.kernel.org/stable/c/b116e9dae433ff631f94c36c61a7a78fe400ed1e
https://git.kernel.org/stable/c/b53d495c7f0db46b6748b5ade48371a10dd5d3bc
reply other threads:[~2026-09-17 16:20 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=2026091739-CVE-2026-90227-bbd7@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.