What’s Vulnerable › Vulnerabilities
CVE-2026-80866: tipc: avoid busy looping in tipc_exit_net()
- Severity: unknown
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-09-04 · updated 2026-10-30
Description
In the Linux kernel, the following vulnerability has been resolved: tipc: avoid busy looping in tipc_exit_net() Blamed commit introduced a busy-wait loop in tipc_exit_net() to wait for pending UDP bearer cleanup works to complete: while (atomic_read(&tn->wq_count)) cond_resched(); This loop can busy-wait for a long time if cond_resched() is a NOP. This typically happens if the netns exit is executed by a high priority task, or under kernels configured without preemption (CONFIG_PREEMPT_NONE). In such cases, it wastes CPU cycles and can lead to soft lockups. Fix this by replacing the busy loop with wait_var_event(), allowing the thread to sleep properly until the work queue count reaches zero. Accordingly, update cleanup_bearer() to use atomic_dec_and_test() and wake_up_var() to wake up the waiter when the count drops to zero. This uses the global wait queue hash table, avoiding the need to bloat struct tipc_net with a wait_queue_head_t. The atomic_dec_and_test() provides the necessary memory barrier to ensure the wakeup is not missed.
Affected products
- Linux: from 5.4.124 before 5.5; from 5.10.42 before 5.11; from 5.12.9 before 5.13 — fixed in 5.5, 5.11, 5.13
How to fix
Upgrade to a fixed version: Linux 5.5, 5.11, 5.13. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/110bb16d37bdba03213156c0df37e7119c190936
- https://git.kernel.org/stable/c/522d1d950b9e3b68190a6de7534827c8dccedb73
- https://git.kernel.org/stable/c/7672973957e3e20780afe5937a9fec70b72bc060
- https://git.kernel.org/stable/c/772769859226a5b004442403510acb58a1c32e72
- https://git.kernel.org/stable/c/99b82c8452887408ea908fdfa5df33c4a5dfa88f
- https://git.kernel.org/stable/c/c1481c94e74c955e0448ddf46b8615a44d840c1e
Get alerted when CVE-2026-80866 or the next vulnerability affects your stack