igmp: convert struct ip_sf_list to RCU Fix available

CVE-2026-98103

Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
kernel.org (opens in new tab)
Published
Last modified
NVD status
Analyzed
CVSS 3.17.8High

Description

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

igmp: convert struct ip_sf_list to RCU

Commit 23d2b94043ca ("igmp: Add ip_mc_list lock in ip_check_mc_rcu")
added spin_lock_bh(&im->lock) to ip_check_mc_rcu() to prevent a
use-after-free while iterating im->sources during concurrent deletions.

However, ip_check_mc_rcu() is called from RCU read-side critical
sections in packet receive and route lookup fast paths (e.g.
__mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()).

When igmpv3_send_cr() or igmpv3_send_report() holds &pmc->lock and
calls add_grec() -> igmpv3_newpack() -> ip_route_output_ports(),
an XFRM policy matching a multicast destination triggers
xfrm_tmpl_resolve_one() -> xfrm4_get_saddr() -> __mkroute_output() ->
ip_check_mc_rcu(). This attempts to acquire &im->lock while &pmc->lock
is already held on the same CPU, triggering a lockdep recursive locking
warning / deadlock.

Fix this by converting IPv4 struct ip_sf_list to RCU, mirroring the
IPv6 implementation in net/ipv6/mcast.c:

  1. Add struct rcu_head to struct ip_sf_list and annotate sf_next,
    sources, and tomb as __rcu pointers.
  2. Use rcu_assign_pointer() and kfree_rcu() for list updates and
    deletions.
  3. Remove spin_lock_bh(&im->lock) from ip_check_mc_rcu() and traverse
    im->sources locklessly with for_each_psf_rcu(), reading and writing
    counter fields with READ_ONCE() and WRITE_ONCE().

Note: RCU conversion of /proc/net/mcfilter will be done in a
separate patch.

Exploitation

Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.

FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)

FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.

Probability of exploitationIt predicts attempts, not success, and is updated daily.
0.125%
Compared with other CVEs
At or above 2.199% of scored CVEs
Scored

Affected products

The products and versions with the vulnerability.

Listed by CNA

The products and versions affected, according to the organization that published this CVE.

VendorProductAffected versions
LinuxLinux
  • 4.4.284 to < 4.5
  • 4.9.283 to < 4.10
  • 4.14.247 to < 4.15
  • 4.19.207 to < 4.20
  • 5.4.145 to < 5.5
  • 5.10.64 to < 5.11
  • 5.13.16 to < 5.14
  • 5.14.3 to < 5.15
  • 5.15

13 commit ranges

Not affected: < 5.15, 6.6.160, 6.12.111, 6.18.53, 7.2.7, 7.3

How to fix the vulnerability, or reduce the risk until you can.

Severity

How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).

  • 7.8 HighCVSS 3.1 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Local
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    Privileges requiredThe access the attacker needs before attacking.
    Low
    User interactionWhether someone other than the attacker has to do something, like open a link.
    None
    ScopeWhether the attack can reach beyond the vulnerable component.
    Unchanged
    ConfidentialityHow much data the attacker can read.
    High
    IntegrityHow much data the attacker can change.
    High
    AvailabilityHow much the attacker can disrupt the system or service.
    High

    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HView in FIRST's calculator (opens in new tab)

Weaknesses and attack patterns

The type of bug behind the vulnerability, and how attackers exploit that type.

  • Use After Free · CWE-416 (opens in new tab)

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

    Likelihood of exploitHow likely MITRE rates attacks on this type of weakness, in general rather than for this vulnerability.
    High
    Abstraction
    Variant
    Mapping guidance
    Allowed
    Part of

References

Advisories, patches, exploits and more about this vulnerability.

This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data