From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64072: nvme: fix bio leak on mapping failure
Date: Sun, 19 Jul 2026 17:38:54 +0200 [thread overview]
Message-ID: <2026071913-CVE-2026-64072-6fc4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nvme: fix bio leak on mapping failure
The local bio is always NULL, so we'd leak the bio if the integrity
mapping failed. Just get it directly from the request.
The Linux kernel CVE team has assigned CVE-2026-64072 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit d0d1d522316e91f2b935a78bbf962b8e529d8c4f and fixed in 6.18.34 with commit fea4b46f84c50caf93c6c0f2a54b1be2edfb4491
Issue introduced in 6.18 with commit d0d1d522316e91f2b935a78bbf962b8e529d8c4f and fixed in 7.0.11 with commit 51ec7fc4e10c5e332bf4007bdb7e4c6bf03c14c9
Issue introduced in 6.18 with commit d0d1d522316e91f2b935a78bbf962b8e529d8c4f and fixed in 7.1 with commit 2279cd9c61a330e5de4d6eb0bc422820dd6fdf36
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-64072
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/fea4b46f84c50caf93c6c0f2a54b1be2edfb4491
https://git.kernel.org/stable/c/51ec7fc4e10c5e332bf4007bdb7e4c6bf03c14c9
https://git.kernel.org/stable/c/2279cd9c61a330e5de4d6eb0bc422820dd6fdf36
reply other threads:[~2026-07-19 15:42 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=2026071913-CVE-2026-64072-6fc4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).