IB/IPoIB: Avoid restoring OPER_UP after multicast flush
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3, 3.11, 3.13, 3.17, 4.5, and 8 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in f973769fb7cb33ba0d4a64b7dcfee0cabaead938; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in b72f38929f4b5aa83161fd3b22a7327207e51ec5; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in 1b11e4b55b41d9e69a8e8d07622614202e2eaca9; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in 326f7d34bd7e64de535566b65c0533b640df5a81; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in 5ad925d45f28464a5e043c9620880bb6a030da89; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in 188b334a6db36a8e0bfaaf59bc4020639a0f3aad; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in 1ff3add37c329704ec46181b4ae4f00f9f16ce6f; From 344bacca8cd811809fc33a249f2738ab757d327f · fixed in 9a141d3dc869d18b2eab35e999f4790a9b84e40f; From 3.2.84 · fixed in 3.3; From 3.10.105 · fixed in 3.11; From 3.12.65 · fixed in 3.13; From 3.16.39 · fixed in 3.17; From 4.4.24 · fixed in 4.5; From 4.7.7 · fixed in 4.8
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 8
git.kernel.org
- stable/c/f973769fb7cb33ba0d4a64b7dcfee0cabaead938
- stable/c/b72f38929f4b5aa83161fd3b22a7327207e51ec5
- stable/c/1b11e4b55b41d9e69a8e8d07622614202e2eaca9
- stable/c/326f7d34bd7e64de535566b65c0533b640df5a81
- stable/c/5ad925d45f28464a5e043c9620880bb6a030da89
- stable/c/188b334a6db36a8e0bfaaf59bc4020639a0f3aad
- stable/c/1ff3add37c329704ec46181b4ae4f00f9f16ce6f
- stable/c/9a141d3dc869d18b2eab35e999f4790a9b84e40f