CVE-2026-80866tipc: avoid busy looping in tipc_exit_net()
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 56 days later
· 56 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.20% · top 91% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 04c26faa51d1e2fe71cf13c45791f5174c37f986 – < 772769859226a5b004442403510acb58a1c32e72
- affected 04c26faa51d1e2fe71cf13c45791f5174c37f986 – < 99b82c8452887408ea908fdfa5df33c4a5dfa88f
- affected 04c26faa51d1e2fe71cf13c45791f5174c37f986 – < 110bb16d37bdba03213156c0df37e7119c190936
- affected 04c26faa51d1e2fe71cf13c45791f5174c37f986 – < 7672973957e3e20780afe5937a9fec70b72bc060
- affected 04c26faa51d1e2fe71cf13c45791f5174c37f986 – < 522d1d950b9e3b68190a6de7534827c8dccedb73
- affected 04c26faa51d1e2fe71cf13c45791f5174c37f986 – < c1481c94e74c955e0448ddf46b8615a44d840c1e
- affected d1f76dfadaf8f47ed1753f97dbcbd41c16215ffa
- affected 5195ec5e365a2a9331bfeb585b613a6e94f98dba
- affected b9f5b7ad4ac3af006443f535b1ce7bff1d130d7d
- affected 5.4.124 – < 5.5
- affected 5.10.42 – < 5.11
- affected 5.12.9 – < 5.13
- affected 5.13
- unaffected < 5.13
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/772769859226a5b004442403510acb58a1c32e72 (opens in a new tab)
- https://git.kernel.org/stable/c/99b82c8452887408ea908fdfa5df33c4a5dfa88f (opens in a new tab)
- https://git.kernel.org/stable/c/110bb16d37bdba03213156c0df37e7119c190936 (opens in a new tab)
- https://git.kernel.org/stable/c/7672973957e3e20780afe5937a9fec70b72bc060 (opens in a new tab)
- https://git.kernel.org/stable/c/522d1d950b9e3b68190a6de7534827c8dccedb73 (opens in a new tab)
- https://git.kernel.org/stable/c/c1481c94e74c955e0448ddf46b8615a44d840c1e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71496 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80866)Record last updated .