[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025071007-CVE-2025-38269-fb65@gregkh>
Date: Thu, 10 Jul 2025 09:42:10 +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-38269: btrfs: exit after state insertion failure at btrfs_convert_extent_bit()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
btrfs: exit after state insertion failure at btrfs_convert_extent_bit()
If insert_state() state failed it returns an error pointer and we call
extent_io_tree_panic() which will trigger a BUG() call. However if
CONFIG_BUG is disabled, which is an uncommon and exotic scenario, then
we fallthrough and call cache_state() which will dereference the error
pointer, resulting in an invalid memory access.
So jump to the 'out' label after calling extent_io_tree_panic(), it also
makes the code more clear besides dealing with the exotic scenario where
CONFIG_BUG is disabled.
The Linux kernel CVE team has assigned CVE-2025-38269 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.34 with commit 58c50f45e1821a04d61b62514f9bd34afe67c622
Fixed in 6.15.3 with commit 8d9d32088e304e2bc444a3087cab0bbbd9951866
Fixed in 6.16-rc1 with commit 3bf179e36da917c5d9bec71c714573ed1649b7c1
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-38269
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/extent-io-tree.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/58c50f45e1821a04d61b62514f9bd34afe67c622
https://git.kernel.org/stable/c/8d9d32088e304e2bc444a3087cab0bbbd9951866
https://git.kernel.org/stable/c/3bf179e36da917c5d9bec71c714573ed1649b7c1
Powered by blists - more mailing lists