CVE-2026-98103 PUBLISHED

igmp: convert struct ip_sf_list to RCU

Assigner: Linux
Reserved: 25.09.2026 Published: 25.09.2026 Updated: 25.09.2026

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.

Product Status

Vendor Linux
Product Linux
Versions Default: unaffected
  • affected from 23d2b94043ca8835bd1e67749020e839f396a1c2 to f5182dfad54277267a8cb0c004a9cd4cf35aeebb (excl.)
  • affected from 23d2b94043ca8835bd1e67749020e839f396a1c2 to d3011d1f293478c730aa0870490afa145c37600e (excl.)
  • affected from 23d2b94043ca8835bd1e67749020e839f396a1c2 to e3206419bdb04e2087d8cc6be324df8639b3fac5 (excl.)
  • affected from 23d2b94043ca8835bd1e67749020e839f396a1c2 to 2987ee196c88dbde0463dc87d5fb209c684e34a2 (excl.)
  • Version b24065948ae6c48c9e20891f8cfe9850f1d748be is affected
  • Version e9924c4204ede999b0515fd31a370a1e27f676bc is affected
  • Version 78967749984cf3614de346c90f3e259ff8272735 is affected
  • Version 4768973dffed4d0126854514335ed4fe87bec1ab is affected
  • Version d84708451d9041dff8a81e3718f821f12d2eb6c5 is affected
  • Version ddd7e8b7b84836c584a284b98ca9bd7a348a0558 is affected
  • Version 961447ff60291b91e27d5c32fa549c1411ad3b70 is affected
  • Version d1a3c6d5925a8d00a32c5ef2d674dd9c0ce89c95 is affected
  • affected from 4.4.284 to 4.5 (excl.)
  • affected from 4.9.283 to 4.10 (excl.)
  • affected from 4.14.247 to 4.15 (excl.)
  • affected from 4.19.207 to 4.20 (excl.)
  • affected from 5.4.145 to 5.5 (excl.)
  • affected from 5.10.64 to 5.11 (excl.)
  • affected from 5.13.16 to 5.14 (excl.)
  • affected from 5.14.3 to 5.15 (excl.)
Vendor Linux
Product Linux
Versions Default: affected
  • Version 5.15 is affected
  • unaffected from 0 to 5.15 (excl.)
  • unaffected from 6.12.111 to 6.12.* (incl.)
  • unaffected from 6.18.53 to 6.18.* (incl.)
  • unaffected from 7.2.7 to 7.2.* (incl.)
  • unaffected from 7.3-rc2 to * (incl.)

References