[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022608-CVE-2022-49580-c398@gregkh>
Date: Wed, 26 Feb 2025 03:22:23 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49580: ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.
While reading sysctl_fib_multipath_use_neigh, it can be changed
concurrently. Thus, we need to add READ_ONCE() to its reader.
The Linux kernel CVE team has assigned CVE-2022-49580 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.7 with commit a6db4494d218c2e559173661ee972e048dc04fdd and fixed in 5.4.208 with commit 6727f39e99e0f545d815edebb6c94228485427ec
Issue introduced in 4.7 with commit a6db4494d218c2e559173661ee972e048dc04fdd and fixed in 5.10.134 with commit e045d672ba06e1d35bacb56374d350de0ac99066
Issue introduced in 4.7 with commit a6db4494d218c2e559173661ee972e048dc04fdd and fixed in 5.15.58 with commit b8d345db03b4deffb4f04219a51d3b1e94171b76
Issue introduced in 4.7 with commit a6db4494d218c2e559173661ee972e048dc04fdd and fixed in 5.18.15 with commit 14e996577ed2799a1ed6ffeb71c76d63acb28444
Issue introduced in 4.7 with commit a6db4494d218c2e559173661ee972e048dc04fdd and fixed in 5.19 with commit 87507bcb4f5de16bb419e9509d874f4db6c0ad0f
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-49580
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/fib_semantics.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/6727f39e99e0f545d815edebb6c94228485427ec
https://git.kernel.org/stable/c/e045d672ba06e1d35bacb56374d350de0ac99066
https://git.kernel.org/stable/c/b8d345db03b4deffb4f04219a51d3b1e94171b76
https://git.kernel.org/stable/c/14e996577ed2799a1ed6ffeb71c76d63acb28444
https://git.kernel.org/stable/c/87507bcb4f5de16bb419e9509d874f4db6c0ad0f
Powered by blists - more mailing lists