CVE-2026-98347
IB/IPoIB: Avoid restoring OPER_UP after multicast flush
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 344bacca8cd811809fc33a249f2738ab757d327f, < f973769fb7cb33ba0d4a64b7dcfee0cabaead938Upgrade to: f973769fb7cb33ba0d4a64b7dcfee0cabaead938Affected: ≥ 344bacca8cd811809fc33a249f2738ab757d327f, < b72f38929f4b5aa83161fd3b22a7327207e51ec5Upgrade to: b72f38929f4b5aa83161fd3b22a7327207e51ec5Affected: ≥ 344bacca8cd811809fc33a249f2738ab757d327f, < 1b11e4b55b41d9e69a8e8d07622614202e2eaca9Upgrade to: 1b11e4b55b41d9e69a8e8d07622614202e2eaca9Affected: ≥ 344bacca8cd811809fc33a249f2738ab757d327f, < 326f7d34bd7e64de535566b65c0533b640df5a81Upgrade to: 326f7d34bd7e64de535566b65c0533b640df5a81 + 16 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/f973769fb7cb33ba0d4a64b7dcfee0cabaead938
- git.kernel.org/stable/c/b72f38929f4b5aa83161fd3b22a7327207e51ec5
- git.kernel.org/stable/c/1b11e4b55b41d9e69a8e8d07622614202e2eaca9
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI