From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49599: tcp: Fix data-races around sysctl_tcp_l3mdev_accept.
Date: Wed, 26 Feb 2025 03:22:42 +0100 [thread overview]
Message-ID: <2025022611-CVE-2022-49599-4a64@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tcp: Fix data-races around sysctl_tcp_l3mdev_accept.
While reading sysctl_tcp_l3mdev_accept, it can be changed concurrently.
Thus, we need to add READ_ONCE() to its readers.
The Linux kernel CVE team has assigned CVE-2022-49599 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.5 with commit 6dd9a14e92e54895e143f10fef4d0b9abe109aa9 and fixed in 5.10.137 with commit 1d9c81833dec46ccb52a1d0db970fefb7c4fa071
Issue introduced in 4.5 with commit 6dd9a14e92e54895e143f10fef4d0b9abe109aa9 and fixed in 5.15.58 with commit 9ba9cd43b5776c27d25e5a32dde9e80bdeb1c6a1
Issue introduced in 4.5 with commit 6dd9a14e92e54895e143f10fef4d0b9abe109aa9 and fixed in 5.18.15 with commit 7d38d86b818104cf88961f3aebea34da89364a8e
Issue introduced in 4.5 with commit 6dd9a14e92e54895e143f10fef4d0b9abe109aa9 and fixed in 5.19 with commit 08a75f10679470552a3a443f9aefd1399604d31d
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-49599
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:
include/net/inet_hashtables.h
include/net/inet_sock.h
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/1d9c81833dec46ccb52a1d0db970fefb7c4fa071
https://git.kernel.org/stable/c/9ba9cd43b5776c27d25e5a32dde9e80bdeb1c6a1
https://git.kernel.org/stable/c/7d38d86b818104cf88961f3aebea34da89364a8e
https://git.kernel.org/stable/c/08a75f10679470552a3a443f9aefd1399604d31d
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=2025022611-CVE-2022-49599-4a64@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.