CVE-2026-80866
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 versions
Linux kernel versions
5.4.124,
5.10.42,
5.12.9,
5.13
and later are affected. Fixed in
6.18.57,
7.1.5,
7.2
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-80866?
CVE-2026-80866 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.4.124 onward and has been patched in 6.18.57, 7.1.5 and 7.2. CVE-2026-80866 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-80866?
Yes. CVE-2026-80866 has been patched. Fixed versions include 6.18.57, 7.1.5 and 7.2. If you are running Linux kernel 5.4.124 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-80866 actively exploited?
No. CVE-2026-80866 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.