CVE-2026-80866: tipc: avoid busy looping in tipc_exit_net()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 110bb16d37bdba03213156c0df37e7119c190936, 5.11, 5.13; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 110bb16d37bdba03213156c0df37e7119c190936, 5.11, 5.13; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- d1f76dfadaf8f47ed1753f97dbcbd41c16215ffa, 5195ec5e365a2a9331bfeb585b613a6e94f98dba, b9f5b7ad4ac3af006443f535b1ce7bff1d130d7d, 5.13affected
- 04c26faa51d1e2fe71cf13c45791f5174c37f986 and later · before 772769859226a5b004442403510acb58a1c32e72affected · git
- 04c26faa51d1e2fe71cf13c45791f5174c37f986 and later · before 99b82c8452887408ea908fdfa5df33c4a5dfa88faffected · git
- 04c26faa51d1e2fe71cf13c45791f5174c37f986 and later · before 110bb16d37bdba03213156c0df37e7119c190936affected · git
- 04c26faa51d1e2fe71cf13c45791f5174c37f986 and later · before 7672973957e3e20780afe5937a9fec70b72bc060affected · git
- 04c26faa51d1e2fe71cf13c45791f5174c37f986 and later · before 522d1d950b9e3b68190a6de7534827c8dccedb73affected · git
- 04c26faa51d1e2fe71cf13c45791f5174c37f986 and later · before c1481c94e74c955e0448ddf46b8615a44d840c1eaffected · git
- 5.4.124 and later · before 5.5affected · semver
- 5.10.42 and later · before 5.11affected · semver
- 5.12.9 and later · before 5.13affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80864Sep 4, 2026 · RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp0Monitor
- ← EarlierCVE-2026-80865Sep 4, 2026 · bpf: Add missing access_ok call to copy_user_syms0Monitor
- Later →CVE-2026-80867Sep 4, 2026 · alpha/PCI: Add security_locked_down() check to pci_mmap_resource()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 110bb16d37bdba03213156c0df37e7119c190936 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 522d1d950b9e3b68190a6de7534827c8dccedb73 | Vendor (CNA) |
| Linux Linux | 7672973957e3e20780afe5937a9fec70b72bc060 | Vendor (CNA) |
| Linux Linux | 772769859226a5b004442403510acb58a1c32e72 | Vendor (CNA) |
| Linux Linux | 99b82c8452887408ea908fdfa5df33c4a5dfa88f | Vendor (CNA) |
| Linux Linux | c1481c94e74c955e0448ddf46b8615a44d840c1e | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.1.5-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/522d1d950b9e3b68190a6de7534827c8dccedb73
- git.kernel.org/stable/c/7672973957e3e20780afe5937a9fec70b72bc060
- git.kernel.org/stable/c/772769859226a5b004442403510acb58a1c32e72
- git.kernel.org/stable/c/99b82c8452887408ea908fdfa5df33c4a5dfa88f
- git.kernel.org/stable/c/c1481c94e74c955e0448ddf46b8615a44d840c1e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.