Kernel hang via topology-server teardown race
Published Oct 23, 2026 · Updated Oct 23, 2026
A teardown race in Linux TIPC allows local users to hang the kernel during network namespace shutdown via concurrent subscription activity. In net/tipc/topsrv.c, tipc_topsrv_stop() closes connections before draining send and receive workqueues, allowing concurrent work to release connection references and callbacks to queue work during shutdown. Exposure requires active TIPC teardown; the upstream report describes an unprivileged user-namespace reproduction mode but captured traces under root, and establishes use-after-free and RCU stalls rather than privilege escalation.
Summary
What happened
A teardown race in Linux TIPC allows local users to hang the kernel during network namespace shutdown via concurrent subscription activity. In net/tipc/topsrv.c, tipc_topsrv_stop() closes connections before draining send and receive workqueues, allowing concurrent work to release connection references and callbacks to queue work during shutdown. Exposure requires active TIPC teardown; the upstream report describes an unprivileged user-namespace reproduction mode but captured traces under root, and establishes use-after-free and RCU stalls rather than privilege escalation.
The record
- CVE
- CVE-2026-99054
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11
- Affected versionversion=c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <0af8780bdfdfc91fb9127bddb9c48fab67dc9d9e
- Affected versionversion=c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <3acdd44385bc7e2e57605e073691ce69cc5a960d
- Affected versionversion=c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <7f796bb3b440d7f1b14c0e3b520462eb34f553af
- Affected versionversion=c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <da9c16568bc79140a54c1f5fcf07a0305df47b37
- Affected versionversion=c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <fb717c536af2aafeca520ff11d1e0f25f7ab8fa9
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us