| 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-49815: erofs: fix missing xas_retry() in fscache mode |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| erofs: fix missing xas_retry() in fscache mode |
| |
| The xarray iteration only holds the RCU read lock and thus may encounter |
| XA_RETRY_ENTRY if there's process modifying the xarray concurrently. |
| This will cause oops when referring to the invalid entry. |
| |
| Fix this by adding the missing xas_retry(), which will make the |
| iteration wind back to the root node if XA_RETRY_ENTRY is encountered. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49815 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.19 with commit d435d53228dd039fffecae123b8c138af6f96f99 and fixed in 6.0.10 with commit dbc98fe99e17ed18f2f272d5fe880d844b1c68c3 |
| Issue introduced in 5.19 with commit d435d53228dd039fffecae123b8c138af6f96f99 and fixed in 6.1 with commit 37020bbb71d911431e16c2c940b97cf86ae4f2f6 |
| |
| 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-49815 |
| 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/erofs/fscache.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/dbc98fe99e17ed18f2f272d5fe880d844b1c68c3 |
| https://git.kernel.org/stable/c/37020bbb71d911431e16c2c940b97cf86ae4f2f6 |
