| From bippy-1.1.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-2022-49770: ceph: avoid putting the realm twice when decoding snaps fails |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ceph: avoid putting the realm twice when decoding snaps fails |
| |
| When decoding the snaps fails it maybe leaving the 'first_realm' |
| and 'realm' pointing to the same snaprealm memory. And then it'll |
| put it twice and could cause random use-after-free, BUG_ON, etc |
| issues. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49770 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 4.19.268 with commit 274e4c79a3a2a24fba7cfe0e41113f1138785c37 |
| Fixed in 5.4.226 with commit cb7495fe957526555782ce0723f79ce92a6db22e |
| Fixed in 5.10.157 with commit 044bc6d3c2c0e9090b0841e7b723875756534b45 |
| Fixed in 5.15.81 with commit 2f6e2de3a5289004650118b61f138fe7c28e1905 |
| Fixed in 6.0.10 with commit fd879c83e87735ab8f00ef7755752cf0cbae24b2 |
| Fixed in 6.1 with commit 51884d153f7ec85e18d607b2467820a90e0f4359 |
| |
| 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-2022-49770 |
| 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/ceph/snap.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/274e4c79a3a2a24fba7cfe0e41113f1138785c37 |
| https://git.kernel.org/stable/c/cb7495fe957526555782ce0723f79ce92a6db22e |
| https://git.kernel.org/stable/c/044bc6d3c2c0e9090b0841e7b723875756534b45 |
| https://git.kernel.org/stable/c/2f6e2de3a5289004650118b61f138fe7c28e1905 |
| https://git.kernel.org/stable/c/fd879c83e87735ab8f00ef7755752cf0cbae24b2 |
| https://git.kernel.org/stable/c/51884d153f7ec85e18d607b2467820a90e0f4359 |
