| 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-49585: tcp: Fix data-races around sysctl_tcp_fastopen_blackhole_timeout. |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| tcp: Fix data-races around sysctl_tcp_fastopen_blackhole_timeout. |
| |
| While reading sysctl_tcp_fastopen_blackhole_timeout, it can be changed |
| concurrently. Thus, we need to add READ_ONCE() to its readers. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49585 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.12 with commit cf1ef3f0719b4dcb74810ed507e2a2540f9811b4 and fixed in 5.10.134 with commit 0dc2f19d8c2636cebda7976b5ea40c6d69f0d891 |
| Issue introduced in 4.12 with commit cf1ef3f0719b4dcb74810ed507e2a2540f9811b4 and fixed in 5.15.58 with commit a77a75a0e7f397550ab039f96115103e78dd5c69 |
| Issue introduced in 4.12 with commit cf1ef3f0719b4dcb74810ed507e2a2540f9811b4 and fixed in 5.18.15 with commit 8afa5604e295046c02b79ccf9e2bbbf8d969d60e |
| Issue introduced in 4.12 with commit cf1ef3f0719b4dcb74810ed507e2a2540f9811b4 and fixed in 5.19 with commit 021266ec640c7a4527e6cd4b7349a512b351de1d |
| |
| 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-49585 |
| 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: |
| net/ipv4/tcp_fastopen.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/0dc2f19d8c2636cebda7976b5ea40c6d69f0d891 |
| https://git.kernel.org/stable/c/a77a75a0e7f397550ab039f96115103e78dd5c69 |
| https://git.kernel.org/stable/c/8afa5604e295046c02b79ccf9e2bbbf8d969d60e |
| https://git.kernel.org/stable/c/021266ec640c7a4527e6cd4b7349a512b351de1d |
