| 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-2025-22114: btrfs: don't clobber ret in btrfs_validate_super() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| btrfs: don't clobber ret in btrfs_validate_super() |
| |
| Commit 2a9bb78cfd36 ("btrfs: validate system chunk array at |
| btrfs_validate_super()") introduces a call to validate_sys_chunk_array() |
| in btrfs_validate_super(), which clobbers the value of ret set earlier. |
| This has the effect of negating the validity checks done earlier, making |
| it so btrfs could potentially try to mount invalid filesystems. |
| |
| The Linux kernel CVE team has assigned CVE-2025-22114 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.14 with commit 2a9bb78cfd367fdeff74f15b1e98969912292d9e and fixed in 6.14.2 with commit ef6800a2015e706e9852a5ec15263fec9990d012 |
| Issue introduced in 6.14 with commit 2a9bb78cfd367fdeff74f15b1e98969912292d9e and fixed in 6.15 with commit 9db9c7dd5b4e1d3205137a094805980082c37716 |
| |
| 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-22114 |
| 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/disk-io.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/ef6800a2015e706e9852a5ec15263fec9990d012 |
| https://git.kernel.org/stable/c/9db9c7dd5b4e1d3205137a094805980082c37716 |
