Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-98103: igmp: convert struct ip_sf_list to RCU

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 01131daffc4b64f1652e23dc3e6e2f601eda781d, 2987ee196c88dbde0463dc87d5fb209c684e34a2, 4.10; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 01131daffc4b64f1652e23dc3e6e2f601eda781d, 2987ee196c88dbde0463dc87d5fb209c684e34a2, 4.10; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Sep 25, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98103

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • b24065948ae6c48c9e20891f8cfe9850f1d748be, e9924c4204ede999b0515fd31a370a1e27f676bc, 78967749984cf3614de346c90f3e259ff8272735, 4768973dffed4d0126854514335ed4fe87bec1ab, d84708451d9041dff8a81e3718f821f12d2eb6c5, ddd7e8b7b84836c584a284b98ca9bd7a348a0558, 961447ff60291b91e27d5c32fa549c1411ad3b70, d1a3c6d5925a8d00a32c5ef2d674dd9c0ce89c95, 5.15affected
    • 23d2b94043ca8835bd1e67749020e839f396a1c2 and later · before 01131daffc4b64f1652e23dc3e6e2f601eda781daffected · git
    • 23d2b94043ca8835bd1e67749020e839f396a1c2 and later · before f5182dfad54277267a8cb0c004a9cd4cf35aeebbaffected · git
    • 23d2b94043ca8835bd1e67749020e839f396a1c2 and later · before d3011d1f293478c730aa0870490afa145c37600eaffected · git
    • 23d2b94043ca8835bd1e67749020e839f396a1c2 and later · before e3206419bdb04e2087d8cc6be324df8639b3fac5affected · git
    • 23d2b94043ca8835bd1e67749020e839f396a1c2 and later · before 2987ee196c88dbde0463dc87d5fb209c684e34a2affected · git
    • 4.4.284 and later · before 4.5affected · semver
    • 4.9.283 and later · before 4.10affected · semver
    • 4.14.247 and later · before 4.15affected · semver
    • 4.19.207 and later · before 4.20affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.7-17.2.7-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98101Sep 25, 2026 · ipv6: mcast: use copy-on-write RCU updates in ip6_mc_source()
    0Monitor
  • ← EarlierCVE-2026-98102Sep 25, 2026 · ipv6: mcast: fix RCU list diversion in ip6_mc_del1_src()
    0Monitor
  • Later →CVE-2026-98104Sep 25, 2026 · net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux01131daffc4b64f1652e23dc3e6e2f601eda781dVendor (CNA)
Linux Linux2987ee196c88dbde0463dc87d5fb209c684e34a2Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux5.11Vendor (CNA)
Linux Linux5.14Vendor (CNA)
Linux Linux5.15Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linuxd3011d1f293478c730aa0870490afa145c37600eVendor (CNA)
Linux Linuxe3206419bdb04e2087d8cc6be324df8639b3fac5Vendor (CNA)
Linux Linuxf5182dfad54277267a8cb0c004a9cd4cf35aeebbVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.06.6.161.1-1 · Release NotesMicrosoft (MSRC)
azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.00:6.18.57-1.1.azl4 · Release NotesMicrosoft (MSRC)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records