blob: ccf1fb53372b37063094fb9e675f0e680bad8581 [file] [log] [blame]
From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-46841: btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc()
We handle errors here properly, ENOMEM isn't fatal, return the error.
The Linux kernel CVE team has assigned CVE-2024-46841 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.231 with commit c1406d8329f500e4594cd9730cd313aebc3a4333
Fixed in 5.15.174 with commit 6a0648f96c3ca647c71c6c1ddbc7c353bab79f64
Fixed in 6.1.120 with commit 44a2c518ab221c0cadcb8c45ca86f83a52dd4da6
Fixed in 6.6.64 with commit 135b4819f6fba87fd5a2693023133e78ac73f1d3
Fixed in 6.10.10 with commit 704c359b4093a2af650a20eaa030c435d7c30f91
Fixed in 6.11 with commit a580fb2c3479d993556e1c31b237c9e5be4944a3
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-2024-46841
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-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/c1406d8329f500e4594cd9730cd313aebc3a4333
https://git.kernel.org/stable/c/6a0648f96c3ca647c71c6c1ddbc7c353bab79f64
https://git.kernel.org/stable/c/44a2c518ab221c0cadcb8c45ca86f83a52dd4da6
https://git.kernel.org/stable/c/135b4819f6fba87fd5a2693023133e78ac73f1d3
https://git.kernel.org/stable/c/704c359b4093a2af650a20eaa030c435d7c30f91
https://git.kernel.org/stable/c/a580fb2c3479d993556e1c31b237c9e5be4944a3