tipc: avoid busy looping in tipc_exit_net()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 04c26faa51d1e2fe71cf13c45791f5174c37f986 · < c1481c94e74c955e0448ddf46b8615a44d840c1e| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s TIPC network namespace exit path can busy-wait while pending UDP bearer cleanup completes. If the exit runs in a high-priority task or on a kernel configured without preemption, it can waste CPU and cause soft lockups. The input does not specify attacker access or user-interaction requirements.
Engineers running Linux kernels with TIPC should check their versions against the vendor advisory; affected versions are not specified.