CVE-2026-98103

igmp: convert struct ip_sf_list to RCU

State
Published
Severity
Not scored
Published
Sep 25, 2026
Updated
Oct 21, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 23d2b94043ca8835bd1e67749020e839f396a1c2 to before 01131daffc4b64f1652e23dc3e6e2f601eda781dAffected
  • 23d2b94043ca8835bd1e67749020e839f396a1c2 to before f5182dfad54277267a8cb0c004a9cd4cf35aeebbAffected
  • 23d2b94043ca8835bd1e67749020e839f396a1c2 to before d3011d1f293478c730aa0870490afa145c37600eAffected
  • 23d2b94043ca8835bd1e67749020e839f396a1c2 to before e3206419bdb04e2087d8cc6be324df8639b3fac5Affected
  • 23d2b94043ca8835bd1e67749020e839f396a1c2 to before 2987ee196c88dbde0463dc87d5fb209c684e34a2Affected
  • b24065948ae6c48c9e20891f8cfe9850f1d748beAffected
  • e9924c4204ede999b0515fd31a370a1e27f676bcAffected
  • 78967749984cf3614de346c90f3e259ff8272735Affected
  • 4768973dffed4d0126854514335ed4fe87bec1abAffected
  • d84708451d9041dff8a81e3718f821f12d2eb6c5Affected
  • ddd7e8b7b84836c584a284b98ca9bd7a348a0558Affected
  • 961447ff60291b91e27d5c32fa549c1411ad3b70Affected
  • d1a3c6d5925a8d00a32c5ef2d674dd9c0ce89c95Affected
  • 4.4.284 to before 4.5Affected
  • 4.9.283 to before 4.10Affected
  • 4.14.247 to before 4.15Affected
  • 4.19.207 to before 4.20Affected
  • 5.4.145 to before 5.5Affected
  • 5.10.64 to before 5.11Affected
  • 5.13.16 to before 5.14Affected
  • 5.14.3 to before 5.15Affected
LinuxLinux
  • 5.15Affected
  • before 5.15Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.111 through 6.12.*Not affected
  • 6.18.53 through 6.18.*Not affected
  • 7.2.7 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.