All reports
Low

kernel: tipc: avoid busy looping in tipc_exit_net()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-80866

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-18

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.

A flaw was found in the Linux kernel's TIPC (Transparent Inter-Process Communication) subsystem. A busy-wait loop in the tipc_exit_net() function, intended to wait for UDP bearer cleanup, can consume excessive CPU cycles. This issue arises when the cond_resched() function is ineffective, such as when a high-priority task executes the network namespace exit or on kernels configured without preemption. This can lead to system unresponsiveness, commonly known as a soft lockup, resulting in a Denial of Service (DoS).