IB/IPoIB: Avoid restoring OPER_UP after multicast flush
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.18% (FIRST EPSS).
- Fixed version: Linux Linux 188b334a6db36a8e0bfaaf59bc4020639a0f3aad, 1b11e4b55b41d9e69a8e8d07622614202e2eaca9, 1ff3add37c329704ec46181b4ae4f00f9f16ce6f; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 188b334a6db36a8e0bfaaf59bc4020639a0f3aad, 1b11e4b55b41d9e69a8e8d07622614202e2eaca9, 1ff3add37c329704ec46181b4ae4f00f9f16ce6f; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: 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.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- a289c65ca49d2680a3d797e633e57a45573d1df2, b81459c78935e4579a577b2366c5f8878d3c7fee, 8a9d8dc9ce83a90bfbbe69181acc4cf1beff46f5, dfe809702a11bd7fb91c882fb55620e39ce22109, 87160fb51bc343793cc8f5f031a87f1a35aecb82, 749fd55dd210f9676f0d445a6efaaa3bec65174a, 4.8affected
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before f973769fb7cb33ba0d4a64b7dcfee0cabaead938affected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before b72f38929f4b5aa83161fd3b22a7327207e51ec5affected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before 1b11e4b55b41d9e69a8e8d07622614202e2eaca9affected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before 326f7d34bd7e64de535566b65c0533b640df5a81affected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before 5ad925d45f28464a5e043c9620880bb6a030da89affected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before 188b334a6db36a8e0bfaaf59bc4020639a0f3aadaffected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before 1ff3add37c329704ec46181b4ae4f00f9f16ce6faffected · git
- 344bacca8cd811809fc33a249f2738ab757d327f and later · before 9a141d3dc869d18b2eab35e999f4790a9b84e40faffected · git
- 3.2.84 and later · before 3.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98345Oct 6, 2026 · wifi: cfg80211: check IP header size in cfg80211_classify8021d()0Monitor
- ← EarlierCVE-2026-98346Oct 6, 2026 · wifi: cfg80211: don't get the radio mask for netdev-less wdevs0Monitor
- Later →CVE-2026-98348Oct 6, 2026 · wifi: libipw: reject too-short association responses28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 188b334a6db36a8e0bfaaf59bc4020639a0f3aad | Vendor (CNA) |
| Linux Linux | 1b11e4b55b41d9e69a8e8d07622614202e2eaca9 | Vendor (CNA) |
| Linux Linux | 1ff3add37c329704ec46181b4ae4f00f9f16ce6f | Vendor (CNA) |
| Linux Linux | 3.11 | Vendor (CNA) |
| Linux Linux | 3.13 | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 326f7d34bd7e64de535566b65c0533b640df5a81 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4.8 | Vendor (CNA) |
| Linux Linux | 5ad925d45f28464a5e043c9620880bb6a030da89 | Vendor (CNA) |
| Linux Linux | 9a141d3dc869d18b2eab35e999f4790a9b84e40f | Vendor (CNA) |
| Linux Linux | b72f38929f4b5aa83161fd3b22a7327207e51ec5 | Vendor (CNA) |
| Linux Linux | f973769fb7cb33ba0d4a64b7dcfee0cabaead938 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package 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.
- Published
- Fix recordedsame day
- TodayOct 23, 2026+17 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1b11e4b55b41d9e69a8e8d07622614202e2eaca9
- git.kernel.org/stable/c/1ff3add37c329704ec46181b4ae4f00f9f16ce6f
- git.kernel.org/stable/c/326f7d34bd7e64de535566b65c0533b640df5a81
- git.kernel.org/stable/c/5ad925d45f28464a5e043c9620880bb6a030da89
- git.kernel.org/stable/c/9a141d3dc869d18b2eab35e999f4790a9b84e40f
- git.kernel.org/stable/c/b72f38929f4b5aa83161fd3b22a7327207e51ec5
- git.kernel.org/stable/c/f973769fb7cb33ba0d4a64b7dcfee0cabaead938
Vendor advisories and official records. Exploit/PoC links are deliberately left out.