| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-46751: btrfs: don't BUG_ON() when 0 reference count at btrfs_lookup_extent_info() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| btrfs: don't BUG_ON() when 0 reference count at btrfs_lookup_extent_info() |
| |
| Instead of doing a BUG_ON() handle the error by returning -EUCLEAN, |
| aborting the transaction and logging an error message. |
| |
| The Linux kernel CVE team has assigned CVE-2024-46751 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.238 with commit 9c309d2434abbe880712af7e60da9ead8b6703fe |
| Fixed in 5.15.184 with commit d64807ded1b6054f066e03d8add6d920f3db9e5d |
| Fixed in 6.1.140 with commit 18eb53a2734ff61b9a72c4fef5db7b38cb48ae16 |
| Fixed in 6.6.92 with commit 3cfec712a439c5c5f5c718c5c669ee41a898f776 |
| Fixed in 6.10.10 with commit ef9a8b73c8b60b27d9db4787e624a3438ffe8428 |
| Fixed in 6.11 with commit 28cb13f29faf6290597b24b728dc3100c019356f |
| |
| 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-46751 |
| 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/9c309d2434abbe880712af7e60da9ead8b6703fe |
| https://git.kernel.org/stable/c/d64807ded1b6054f066e03d8add6d920f3db9e5d |
| https://git.kernel.org/stable/c/18eb53a2734ff61b9a72c4fef5db7b38cb48ae16 |
| https://git.kernel.org/stable/c/3cfec712a439c5c5f5c718c5c669ee41a898f776 |
| https://git.kernel.org/stable/c/ef9a8b73c8b60b27d9db4787e624a3438ffe8428 |
| https://git.kernel.org/stable/c/28cb13f29faf6290597b24b728dc3100c019356f |