| 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-49590: igmp: Fix data-races around sysctl_igmp_llm_reports. |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| igmp: Fix data-races around sysctl_igmp_llm_reports. |
| |
| While reading sysctl_igmp_llm_reports, it can be changed concurrently. |
| Thus, we need to add READ_ONCE() to its readers. |
| |
| This test can be packed into a helper, so such changes will be in the |
| follow-up series after net is merged into net-next. |
| |
| if (ipv4_is_local_multicast(pmc->multiaddr) && |
| !READ_ONCE(net->ipv4.sysctl_igmp_llm_reports)) |
| |
| The Linux kernel CVE team has assigned CVE-2022-49590 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 4.9.325 with commit a84b4afaca2573ed3aed1f8854aefe3ca5a82e72 |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 4.14.290 with commit d77969e7d4ccc26bf1f414a39ef35050a83ba6d5 |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 4.19.254 with commit ed876e99ccf417b8bd7fd8408ba5e8b008e46cc8 |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 5.4.208 with commit 1656ecaddf90e2a070ec2d2404cdae3edf80faca |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 5.10.134 with commit 473aad9ad57ff760005377e6f45a2ad4210e08ce |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 5.15.58 with commit 260446eb8e5541402b271343a4516f2b33dec1e4 |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 5.18.15 with commit 46307adceb67bdf2ec38408dd9cebc378a6b5c46 |
| Issue introduced in 4.3 with commit df2cf4a78e488d26728590cb3c6b4fe4c4862c77 and fixed in 5.19 with commit f6da2267e71106474fbc0943dc24928b9cb79119 |
| |
| 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-49590 |
| 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/igmp.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/a84b4afaca2573ed3aed1f8854aefe3ca5a82e72 |
| https://git.kernel.org/stable/c/d77969e7d4ccc26bf1f414a39ef35050a83ba6d5 |
| https://git.kernel.org/stable/c/ed876e99ccf417b8bd7fd8408ba5e8b008e46cc8 |
| https://git.kernel.org/stable/c/1656ecaddf90e2a070ec2d2404cdae3edf80faca |
| https://git.kernel.org/stable/c/473aad9ad57ff760005377e6f45a2ad4210e08ce |
| https://git.kernel.org/stable/c/260446eb8e5541402b271343a4516f2b33dec1e4 |
| https://git.kernel.org/stable/c/46307adceb67bdf2ec38408dd9cebc378a6b5c46 |
| https://git.kernel.org/stable/c/f6da2267e71106474fbc0943dc24928b9cb79119 |
