From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49579: ipv4: Fix data-races around sysctl_fib_multipath_hash_policy.
Date: Wed, 26 Feb 2025 03:22:22 +0100 [thread overview]
Message-ID: <2025022608-CVE-2022-49579-4f40@gregkh> (raw)
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
reply other threads:[~2025-02-26 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022608-CVE-2022-49579-4f40@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.