CVE-2026-98347
Last modified
CVE-2026-98347 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 344bacca8cd811809fc33a249f2738ab757d327f, < f973769fb7cb33ba0d4a64b7dcfee0cabaead938; >= 344bacca8cd811809fc33a249f2738ab757d327f, < b72f38929f4b5aa83161fd3b22a7327207e51ec5; >= 344bacca8cd811809fc33a249f2738ab757d327f, < 1b11e4b55b41d9e69a8e8d07622614202e2eaca9; >= 344bacca8cd811809fc33a249f2738ab757d327f, < 326f7d34bd7e64de535566b65c0533b640df5a81; >= 344bacca8cd811809fc33a249f2738ab757d327f, < 5ad925d45f28464a5e043c9620880bb6a030da89; >= 344bacca8cd811809fc33a249f2738ab757d327f, < 188b334a6db36a8e0bfaaf59bc4020639a0f3aad; >= 344bacca8cd811809fc33a249f2738ab757d327f, < 1ff3add37c329704ec46181b4ae4f00f9f16ce6f; >= 344bacca8cd811809fc33a249f2738ab757d327f, < 9a141d3dc869d18b2eab35e999f4790a9b84e40f; a289c65ca49d2680a3d797e633e57a45573d1df2; b81459c78935e4579a577b2366c5f8878d3c7fee; 8a9d8dc9ce83a90bfbbe69181acc4cf1beff46f5; dfe809702a11bd7fb91c882fb55620e39ce22109; 87160fb51bc343793cc8f5f031a87f1a35aecb82; 749fd55dd210f9676f0d445a6efaaa3bec65174a; >= 3.2.84, < 3.3; >= 3.10.105, < 3.11; >= 3.12.65, < 3.13; >= 3.16.39, < 3.17; >= 4.4.24, < 4.5; >= 4.7.7, < 4.8 |
| Linux | Linux | 4.8 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98347?
How severe is CVE-2026-98347?
How do I fix CVE-2026-98347?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98341In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98342In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98343In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98344In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98345In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98346In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98348In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98349In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98350In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98351In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98352In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98353In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98347?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
