From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49588: tcp: Fix data-races around sysctl_tcp_migrate_req.
Date: Wed, 26 Feb 2025 03:22:31 +0100 [thread overview]
Message-ID: <2025022609-CVE-2022-49588-9a52@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tcp: Fix data-races around sysctl_tcp_migrate_req.
While reading sysctl_tcp_migrate_req, it can be changed concurrently.
Thus, we need to add READ_ONCE() to its readers.
The Linux kernel CVE team has assigned CVE-2022-49588 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit f9ac779f881c2ec3d1cdcd7fa9d4f9442bf60e80 and fixed in 5.15.58 with commit fcf6c6d8aeffebca66f37b17ef1b57112e5e09c1
Issue introduced in 5.14 with commit f9ac779f881c2ec3d1cdcd7fa9d4f9442bf60e80 and fixed in 5.18.15 with commit 6e569a11eea20a1ccebc3c4e6366bf0574a449e1
Issue introduced in 5.14 with commit f9ac779f881c2ec3d1cdcd7fa9d4f9442bf60e80 and fixed in 5.19 with commit 4177f545895b1da08447a80692f30617154efa6e
Issue introduced in 5.10.188 with commit cf6c06ac74879726c88fe1ec013727006cdbdd58
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-49588
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/core/sock_reuseport.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/fcf6c6d8aeffebca66f37b17ef1b57112e5e09c1
https://git.kernel.org/stable/c/6e569a11eea20a1ccebc3c4e6366bf0574a449e1
https://git.kernel.org/stable/c/4177f545895b1da08447a80692f30617154efa6e
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=2025022609-CVE-2022-49588-9a52@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.