linux-cve-announce - CVE-2025-38405: nvmet: fix memory leak of bio integrity

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025072511-CVE-2025-38405-014e@gregkh>
Date: Fri, 25 Jul 2025 15:12:11 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38405: nvmet: fix memory leak of bio integrity

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

nvmet: fix memory leak of bio integrity

If nvmet receives commands with metadata there is a continuous memory
leak of kmalloc-128 slab or more precisely bio->bi_integrity.

Since commit bf4c89fc8797 ("block: don't call bio_uninit from bio_endio")
each user of bio_init has to use bio_uninit as well. Otherwise the bio
integrity is not getting free. Nvmet uses bio_init for inline bios.

Uninit the inline bio to complete deallocation of integrity in bio.

The Linux kernel CVE team has assigned CVE-2025-38405 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.11 with commit bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f and fixed in 6.12.37 with commit 431e58d56fcb5ff1f9eb630724a922e0d2a941df
	Issue introduced in 6.11 with commit bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f and fixed in 6.15.6 with commit 2e2028fcf924d1c6df017033c8d6e28b735a0508
	Issue introduced in 6.11 with commit bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f and fixed in 6.16-rc5 with commit 190f4c2c863af7cc5bb354b70e0805f06419c038
	Issue introduced in 6.10.10 with commit 64149da0fddbbfe43e11c0348d8c8b4171dae3a2

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-2025-38405
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/nvmet.h


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/431e58d56fcb5ff1f9eb630724a922e0d2a941df
	https://git.kernel.org/stable/c/2e2028fcf924d1c6df017033c8d6e28b735a0508
	https://git.kernel.org/stable/c/190f4c2c863af7cc5bb354b70e0805f06419c038