linux-cve-announce - CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2025122453-CVE-2025-68348-2088@gregkh>
Date: Wed, 24 Dec 2025 11:34:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero_pages

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

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

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

block: fix memory leak in __blkdev_issue_zero_pages

Move the fatal signal check before bio_alloc() to prevent a memory
leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.

Previously, the bio was allocated before checking for a fatal signal.
If a signal was pending, the code would break out of the loop without
freeing or chaining the just-allocated bio, causing a memory leak.

This matches the pattern already used in __blkdev_issue_write_zeroes()
where the signal check precedes the allocation.

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


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

	Issue introduced in 6.11 with commit bf86bcdb40123ee99669ee91b67e023669433a1a and fixed in 6.12.63 with commit 453e4b0c84d0db1454ff0adf655d91179e6fca3a
	Issue introduced in 6.11 with commit bf86bcdb40123ee99669ee91b67e023669433a1a and fixed in 6.17.13 with commit 7957635c679e8a01147163a3a4a1f16e1210fa03
	Issue introduced in 6.11 with commit bf86bcdb40123ee99669ee91b67e023669433a1a and fixed in 6.18.2 with commit 7193407bc4457212fa38ec3aff9c640e63a8dbef
	Issue introduced in 6.11 with commit bf86bcdb40123ee99669ee91b67e023669433a1a and fixed in 6.19-rc1 with commit f7e3f852a42d7cd8f1af2c330d9d153e30c8adcf

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-68348
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:
	block/blk-lib.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/453e4b0c84d0db1454ff0adf655d91179e6fca3a
	https://git.kernel.org/stable/c/7957635c679e8a01147163a3a4a1f16e1210fa03
	https://git.kernel.org/stable/c/7193407bc4457212fa38ec3aff9c640e63a8dbef
	https://git.kernel.org/stable/c/f7e3f852a42d7cd8f1af2c330d9d153e30c8adcf