From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49593: tcp: Fix a data-race around sysctl_tcp_probe_interval.
Date: Wed, 26 Feb 2025 03:22:36 +0100 [thread overview]
Message-ID: <2025022610-CVE-2022-49593-b98d@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tcp: Fix a data-race around sysctl_tcp_probe_interval.
While reading sysctl_tcp_probe_interval, it can be changed concurrently.
Thus, we need to add READ_ONCE() to its reader.
The Linux kernel CVE team has assigned CVE-2022-49593 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 4.14.290 with commit 80dabd089086e6553b7acfcff2ec223bdada87a1
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 4.19.254 with commit b3798d3519eda9c409bb0815b0102f27ec42468d
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 5.4.208 with commit 73a11588751a2c13f25d9da8117efc9a79b1843f
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 5.10.134 with commit c61aede097d350d890fa1edc9521b0072e14a0b8
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 5.15.58 with commit e6b6f027e2854a51f345a5e3e808d7a88001d4f8
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 5.18.15 with commit b14cc8afbbcbc6dce4797913c0b85266b897f541
Issue introduced in 4.1 with commit 05cbc0db03e82128f2e7e353d4194dd24a1627fe and fixed in 5.19 with commit 2a85388f1d94a9f8b5a529118a2c5eaa0520d85c
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-49593
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_output.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/80dabd089086e6553b7acfcff2ec223bdada87a1
https://git.kernel.org/stable/c/b3798d3519eda9c409bb0815b0102f27ec42468d
https://git.kernel.org/stable/c/73a11588751a2c13f25d9da8117efc9a79b1843f
https://git.kernel.org/stable/c/c61aede097d350d890fa1edc9521b0072e14a0b8
https://git.kernel.org/stable/c/e6b6f027e2854a51f345a5e3e808d7a88001d4f8
https://git.kernel.org/stable/c/b14cc8afbbcbc6dce4797913c0b85266b897f541
https://git.kernel.org/stable/c/2a85388f1d94a9f8b5a529118a2c5eaa0520d85c
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=2025022610-CVE-2022-49593-b98d@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.