From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49589: igmp: Fix data-races around sysctl_igmp_qrv.
Date: Wed, 26 Feb 2025 03:22:32 +0100 [thread overview]
Message-ID: <2025022609-CVE-2022-49589-fb90@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
igmp: Fix data-races around sysctl_igmp_qrv.
While reading sysctl_igmp_qrv, it can be changed concurrently.
Thus, we need to add READ_ONCE() to its readers.
This test can be packed into a helper, so such changes will be in the
follow-up series after net is merged into net-next.
qrv ?: READ_ONCE(net->ipv4.sysctl_igmp_qrv);
The Linux kernel CVE team has assigned CVE-2022-49589 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.18 with commit a9fe8e29945d56f35235a3a0fba99b4cf181d211 and fixed in 4.19.255 with commit 9eeb3a7702998bdccbfcc37997b5dd9215b9a7f7
Issue introduced in 3.18 with commit a9fe8e29945d56f35235a3a0fba99b4cf181d211 and fixed in 5.4.209 with commit e20dd1b0e0ea15bee1e528536a0840dba972ca0e
Issue introduced in 3.18 with commit a9fe8e29945d56f35235a3a0fba99b4cf181d211 and fixed in 5.10.135 with commit b399ffafffba39f47b731b26a5da1dc0ffc4b3ad
Issue introduced in 3.18 with commit a9fe8e29945d56f35235a3a0fba99b4cf181d211 and fixed in 5.15.59 with commit c721324afc589f8ea54bae04756b150aeaae5fa4
Issue introduced in 3.18 with commit a9fe8e29945d56f35235a3a0fba99b4cf181d211 and fixed in 5.18.15 with commit c2954671010cd1127d1ffa328c6e6f8e99930982
Issue introduced in 3.18 with commit a9fe8e29945d56f35235a3a0fba99b4cf181d211 and fixed in 5.19 with commit 8ebcc62c738f68688ee7c6fec2efe5bc6d3d7e60
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-49589
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:
drivers/net/amt.c
net/ipv4/igmp.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/9eeb3a7702998bdccbfcc37997b5dd9215b9a7f7
https://git.kernel.org/stable/c/e20dd1b0e0ea15bee1e528536a0840dba972ca0e
https://git.kernel.org/stable/c/b399ffafffba39f47b731b26a5da1dc0ffc4b3ad
https://git.kernel.org/stable/c/c721324afc589f8ea54bae04756b150aeaae5fa4
https://git.kernel.org/stable/c/c2954671010cd1127d1ffa328c6e6f8e99930982
https://git.kernel.org/stable/c/8ebcc62c738f68688ee7c6fec2efe5bc6d3d7e60
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-49589-fb90@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.