linux-cve-announce - CVE-2025-37978: block: integrity: Do not call set_page_dirty

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: <2025052040-CVE-2025-37978-79b0@gregkh>
Date: Tue, 20 May 2025 18:56:42 +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-37978: block: integrity: Do not call set_page_dirty_lock()

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

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

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

block: integrity: Do not call set_page_dirty_lock()

Placing multiple protection information buffers inside the same page
can lead to oopses because set_page_dirty_lock() can't be called from
interrupt context.

Since a protection information buffer is not backed by a file there is
no point in setting its page dirty, there is nothing to synchronize.
Drop the call to set_page_dirty_lock() and remove the last argument to
bio_integrity_unpin_bvec().

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


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

	Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 6.12.25 with commit c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4
	Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 6.14.4 with commit 9487fc1a10b3aa89feb24e7cedeccaaf63074617
	Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 6.15-rc3 with commit 39e160505198ff8c158f11bce2ba19809a756e8b

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-37978
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/bio-integrity.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/c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4
	https://git.kernel.org/stable/c/9487fc1a10b3aa89feb24e7cedeccaaf63074617
	https://git.kernel.org/stable/c/39e160505198ff8c158f11bce2ba19809a756e8b