linux-cve-announce - CVE-2025-38243: btrfs: fix invalid inode pointer dereferences during log replay

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: <2025070933-CVE-2025-38243-4b56@gregkh>
Date: Wed,  9 Jul 2025 12:42:35 +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-38243: btrfs: fix invalid inode pointer dereferences during log replay

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

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

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

btrfs: fix invalid inode pointer dereferences during log replay

In a few places where we call read_one_inode(), if we get a NULL pointer
we end up jumping into an error path, or fallthrough in case of
__add_inode_ref(), where we then do something like this:

   iput(&inode->vfs_inode);

which results in an invalid inode pointer that triggers an invalid memory
access, resulting in a crash.

Fix this by making sure we don't do such dereferences.

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


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

	Issue introduced in 6.15 with commit b4c50cbb01a1b6901d2b94469636dd80fa93de81 and fixed in 6.15.5 with commit ba8386d662cc51cc5382688bbf7a152b0b0b27cf
	Issue introduced in 6.15 with commit b4c50cbb01a1b6901d2b94469636dd80fa93de81 and fixed in 6.16-rc4 with commit 2dcf838cf5c2f0f4501edaa1680fcad03618d760

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-38243
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:
	fs/btrfs/tree-log.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/ba8386d662cc51cc5382688bbf7a152b0b0b27cf
	https://git.kernel.org/stable/c/2dcf838cf5c2f0f4501edaa1680fcad03618d760