From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49632: icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.
Date: Wed, 26 Feb 2025 03:23:15 +0100 [thread overview]
Message-ID: <2025022617-CVE-2022-49632-ea1e@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.
While reading sysctl_icmp_errors_use_inbound_ifaddr, it can be changed
concurrently. Thus, we need to add READ_ONCE() to its reader.
The Linux kernel CVE team has assigned CVE-2022-49632 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.12 with commit 1c2fb7f93cb20621772bf304f3dba0849942e5db and fixed in 5.15.56 with commit de9490c32bc10020efdd1509689a28f197d6dfb8
Issue introduced in 2.6.12 with commit 1c2fb7f93cb20621772bf304f3dba0849942e5db and fixed in 5.18.13 with commit f9617844e4d5d6331dbce3fb19a24e5bda201e58
Issue introduced in 2.6.12 with commit 1c2fb7f93cb20621772bf304f3dba0849942e5db and fixed in 5.19 with commit d2efabce81db7eed1c98fa1a3f203f0edd738ac3
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-49632
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
net/ipv4/sysctl_net_ipv4.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/de9490c32bc10020efdd1509689a28f197d6dfb8
https://git.kernel.org/stable/c/f9617844e4d5d6331dbce3fb19a24e5bda201e58
https://git.kernel.org/stable/c/d2efabce81db7eed1c98fa1a3f203f0edd738ac3
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=2025022617-CVE-2022-49632-ea1e@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.