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-49638: icmp: Fix data-races around sysctl.
Date: Wed, 26 Feb 2025 03:23:21 +0100	[thread overview]
Message-ID: <2025022618-CVE-2022-49638-e524@gregkh> (raw)

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

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

icmp: Fix data-races around sysctl.

While reading icmp sysctl variables, they can be changed concurrently.
So, we need to add READ_ONCE() to avoid data-races.

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


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

	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 4.9.324 with commit 1740e5922fbb705637ae9fa5203db132fc45f9f6
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 4.14.289 with commit 53ecd09ef2fb35fa69667ae8e414ef6b00fd3bf6
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 4.19.253 with commit edeec63b13c252193d626c2a48d7a2f0e7016dc2
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 5.4.207 with commit 0cba7ca667ceb06934746ddd9833a25847bde81d
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 5.10.132 with commit e088ceb73c24ab4774da391d54a6426f4bfaefce
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 5.15.56 with commit e2828e8c605853f71267825c9415437c0a93e4f2
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 5.18.13 with commit 798c2cf57c63ab39c8aac24d6a3d50f4fa5eeb06
	Issue introduced in 3.18 with commit 4cdf507d54525842dfd9f6313fdafba039084046 and fixed in 5.19 with commit 48d7ee321ea5182c6a70782aa186422a70e67e22

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-49638
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/icmp.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/1740e5922fbb705637ae9fa5203db132fc45f9f6
	https://git.kernel.org/stable/c/53ecd09ef2fb35fa69667ae8e414ef6b00fd3bf6
	https://git.kernel.org/stable/c/edeec63b13c252193d626c2a48d7a2f0e7016dc2
	https://git.kernel.org/stable/c/0cba7ca667ceb06934746ddd9833a25847bde81d
	https://git.kernel.org/stable/c/e088ceb73c24ab4774da391d54a6426f4bfaefce
	https://git.kernel.org/stable/c/e2828e8c605853f71267825c9415437c0a93e4f2
	https://git.kernel.org/stable/c/798c2cf57c63ab39c8aac24d6a3d50f4fa5eeb06
	https://git.kernel.org/stable/c/48d7ee321ea5182c6a70782aa186422a70e67e22

                 reply	other threads:[~2025-02-26  2:27 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=2025022618-CVE-2022-49638-e524@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.