CVE-2026-98347 — IB/IPoIB: Avoid restoring OPER_UP after multicast flush
In the Linux kernel, the following vulnerability has been resolved: IB/IPoIB: Avoid restoring OPER_UP after multicast flush ipoib_ib_dev_flush_light() temporarily clears IPOIB_FLAG_OPER_UP to prevent multicast joins while ipoib_mcast_dev_flush() is running, and restores the flag afterwards if it was previously set. This restore races with ipoib_ib_dev_down(). If the interface is brought down while the flush is in progress, ipoib_ib_dev_down() clears IPOIB_FLAG_OPER_UP, but the flush path may set it again after the device has already gone down. Since commit 894021a75291 ("IB/ipoib: Make the carrier_on_task race aware"), ipoib_mcast_carrier_on_task() relies on IPOIB_FLAG_OPER_UP being cleared to terminate its rtnl_trylock() retry loop. If the flag is left set after shutdown, the workqueue retries forever, causing teardown to deadlock when ipoib_ndo_uninit() waits in destroy_workqueue() while holding RTNL. Instead of overloading IPOIB_FLAG_OPER_UP to block multicast joins during a light flush, introduce a dedicated IPOIB_FLAG_MCAST_FLUSH flag. Use it together with IPOIB_FLAG_OPER_UP to determine whether multicast joins are allowed, avoiding the race with device shutdown.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 8a9d8dc9ce83a90bfbbe69181acc4cf1beff46f5version 4.8≥ 4.7.7 and < 4.8≥ 4.4.24 and < 4.5≥ 3.16.39 and < 3.17≥ 3.12.65 and < 3.13≥ 3.10.105 and < 3.11≥ 3.2.84 and < 3.3 and 13 moreversion 749fd55dd210f9676f0d445a6efaaa3bec65174aversion 87160fb51bc343793cc8f5f031a87f1a35aecb82version dfe809702a11bd7fb91c882fb55620e39ce22109≥ 344bacca8cd811809fc33a249f2738ab757d327f and < f973769fb7cb33ba0d4a64b7dcfee0cabaead938version b81459c78935e4579a577b2366c5f8878d3c7feeversion a289c65ca49d2680a3d797e633e57a45573d1df2≥ 344bacca8cd811809fc33a249f2738ab757d327f and < 9a141d3dc869d18b2eab35e999f4790a9b84e40f≥ 344bacca8cd811809fc33a249f2738ab757d327f and < 1ff3add37c329704ec46181b4ae4f00f9f16ce6f≥ 344bacca8cd811809fc33a249f2738ab757d327f and < 188b334a6db36a8e0bfaaf59bc4020639a0f3aad≥ 344bacca8cd811809fc33a249f2738ab757d327f and < 5ad925d45f28464a5e043c9620880bb6a030da89≥ 344bacca8cd811809fc33a249f2738ab757d327f and < 326f7d34bd7e64de535566b65c0533b640df5a81≥ 344bacca8cd811809fc33a249f2738ab757d327f and < 1b11e4b55b41d9e69a8e8d07622614202e2eaca9≥ 344bacca8cd811809fc33a249f2738ab757d327f and < b72f38929f4b5aa83161fd3b22a7327207e51ec5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/9a141d3dc869d18b2eab35e999f4790a9b84e40f
- git.kernel.org/stable/c/b72f38929f4b5aa83161fd3b22a7327207e51ec5
- git.kernel.org/stable/c/1ff3add37c329704ec46181b4ae4f00f9f16ce6f
- git.kernel.org/stable/c/188b334a6db36a8e0bfaaf59bc4020639a0f3aad
- git.kernel.org/stable/c/326f7d34bd7e64de535566b65c0533b640df5a81
- git.kernel.org/stable/c/1b11e4b55b41d9e69a8e8d07622614202e2eaca9
- git.kernel.org/stable/c/5ad925d45f28464a5e043c9620880bb6a030da89
- git.kernel.org/stable/c/f973769fb7cb33ba0d4a64b7dcfee0cabaead938
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98347 is "IB/IPoIB: Avoid restoring OPER_UP after multicast flush", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.