| 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-2022-49579: ipv4: Fix data-races around sysctl_fib_multipath_hash_policy. |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ipv4: Fix data-races around sysctl_fib_multipath_hash_policy. |
| |
| While reading sysctl_fib_multipath_hash_policy, it can be changed |
| concurrently. Thus, we need to add READ_ONCE() to its readers. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49579 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.12 with commit bf4e0a3db97eb882368fd82980b3b1fa0b5b9778 and fixed in 5.15.58 with commit 21fb844bc1dc1461f5038d655aa1a14f39e13049 |
| Issue introduced in 4.12 with commit bf4e0a3db97eb882368fd82980b3b1fa0b5b9778 and fixed in 5.18.15 with commit 918ee6592ab9a2ff5316d06cfd4aaef60ccabec6 |
| Issue introduced in 4.12 with commit bf4e0a3db97eb882368fd82980b3b1fa0b5b9778 and fixed in 5.19 with commit 7998c12a08c97cc26660532c9f90a34bd7d8da5a |
| |
| 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-49579 |
| 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: |
| drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c |
| net/ipv4/route.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/21fb844bc1dc1461f5038d655aa1a14f39e13049 |
| https://git.kernel.org/stable/c/918ee6592ab9a2ff5316d06cfd4aaef60ccabec6 |
| https://git.kernel.org/stable/c/7998c12a08c97cc26660532c9f90a34bd7d8da5a |
