From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49571: tcp: Fix data-races around sysctl_tcp_max_reordering.
Date: Wed, 26 Feb 2025 03:22:14 +0100 [thread overview]
Message-ID: <2025022606-CVE-2022-49571-74ee@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tcp: Fix data-races around sysctl_tcp_max_reordering.
While reading sysctl_tcp_max_reordering, it can be changed
concurrently. Thus, we need to add READ_ONCE() to its readers.
The Linux kernel CVE team has assigned CVE-2022-49571 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.19 with commit dca145ffaa8d39ea1904491ac81b92b7049372c0 and fixed in 4.19.254 with commit 5e38cee24f19d19280c68f1ac8bf6790d607f60a
Issue introduced in 3.19 with commit dca145ffaa8d39ea1904491ac81b92b7049372c0 and fixed in 5.4.208 with commit 50a1d3d097503a90cf84ebe120afcde37e9c33b3
Issue introduced in 3.19 with commit dca145ffaa8d39ea1904491ac81b92b7049372c0 and fixed in 5.10.134 with commit 064852663308c801861bd54789d81421fa4c2928
Issue introduced in 3.19 with commit dca145ffaa8d39ea1904491ac81b92b7049372c0 and fixed in 5.15.58 with commit ce3731c61589ed73364a5b55ce34131762ef9b60
Issue introduced in 3.19 with commit dca145ffaa8d39ea1904491ac81b92b7049372c0 and fixed in 5.18.15 with commit 46deb91ac8a790286ad6d24cf92e7ab0ab2582bb
Issue introduced in 3.19 with commit dca145ffaa8d39ea1904491ac81b92b7049372c0 and fixed in 5.19 with commit a11e5b3e7a59fde1a90b0eaeaa82320495cf8cae
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-49571
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_input.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/5e38cee24f19d19280c68f1ac8bf6790d607f60a
https://git.kernel.org/stable/c/50a1d3d097503a90cf84ebe120afcde37e9c33b3
https://git.kernel.org/stable/c/064852663308c801861bd54789d81421fa4c2928
https://git.kernel.org/stable/c/ce3731c61589ed73364a5b55ce34131762ef9b60
https://git.kernel.org/stable/c/46deb91ac8a790286ad6d24cf92e7ab0ab2582bb
https://git.kernel.org/stable/c/a11e5b3e7a59fde1a90b0eaeaa82320495cf8cae
reply other threads:[~2025-02-26 2:24 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=2025022606-CVE-2022-49571-74ee@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.