All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49595: tcp: Fix a data-race around sysctl_tcp_probe_threshold.
Date: Wed, 26 Feb 2025 03:22:38 +0100	[thread overview]
Message-ID: <2025022610-CVE-2022-49595-6abc@gregkh> (raw)

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

tcp: Fix a data-race around sysctl_tcp_probe_threshold.

While reading sysctl_tcp_probe_threshold, it can be changed concurrently.
Thus, we need to add READ_ONCE() to its reader.

The Linux kernel CVE team has assigned CVE-2022-49595 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 4.9.325 with commit 9b5dc7ad6da1373d3c60d4b869d688f996e5d219
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 4.14.290 with commit 44768749980d53bc01980d9c060f736808d11af0
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 4.19.254 with commit 96900fa61777402eb5056269d8000aace33a8b6c
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 5.4.208 with commit b04817c94fbd285a967d9b830b274fe9998c9c0b
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 5.10.134 with commit d452ce36f2d4c402fa3f5275c9677f80166e7fc6
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 5.15.58 with commit f524c3e7f6cdad66b3b6a912cef47b656f8b0de3
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 5.18.15 with commit fa5fb2cf9393db898772db8cb897ed5fd265eb78
	Issue introduced in 4.1 with commit 6b58e0a5f32dedb609438bb9c9c82aa6e23381f2 and fixed in 5.19 with commit 92c0aa4175474483d6cf373314343d4e624e882a

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-49595
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/9b5dc7ad6da1373d3c60d4b869d688f996e5d219
	https://git.kernel.org/stable/c/44768749980d53bc01980d9c060f736808d11af0
	https://git.kernel.org/stable/c/96900fa61777402eb5056269d8000aace33a8b6c
	https://git.kernel.org/stable/c/b04817c94fbd285a967d9b830b274fe9998c9c0b
	https://git.kernel.org/stable/c/d452ce36f2d4c402fa3f5275c9677f80166e7fc6
	https://git.kernel.org/stable/c/f524c3e7f6cdad66b3b6a912cef47b656f8b0de3
	https://git.kernel.org/stable/c/fa5fb2cf9393db898772db8cb897ed5fd265eb78
	https://git.kernel.org/stable/c/92c0aa4175474483d6cf373314343d4e624e882a

                 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-49595-6abc@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.