In the Linux kernel, the following vulnerability has been resolved: tipc: destroy topsrv workqueues before closing connections tipc_top…
CVE-2026-99054 · GHSA-qw7p-7wvc-p5q5 · EUVD-2026-108849 · published 23 Oct 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-99054?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <fb717c536af2aafeca520ff11d1e0f25f7ab8fa9
- Linux Linux: c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <da9c16568bc79140a54c1f5fcf07a0305df47b37
- Linux Linux: patch: 7.2.11
- Linux Linux: c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <7f796bb3b440d7f1b14c0e3b520462eb34f553af
- Linux Linux: patch: 6.12.113
- Linux Linux: c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <0af8780bdfdfc91fb9127bddb9c48fab67dc9d9e
- Linux Linux: c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f <3acdd44385bc7e2e57605e073691ce69cc5a960d
- Linux Linux: patch: 6.18.57
- Linux Linux: patch: 6.6.160
- Linux Linux: patch: 0
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
tipc: destroy topsrv workqueues before closing connections
tipc_topsrv_stop() closed subscriber connections while the topology
server's send and receive workqueues were still running. Socket
callbacks and subscription events could then queue more work, and
in-flight send/recv work could drop the last connection reference
during the conn_idr walk.
That race produced several teardown failures: refcount_t addition on
0 from conn_get() on a connection whose release was blocked on
idr_lock, a subsequent use-after-free in tipc_conn_close(),
queue_work() on an already destroyed workqueue from the listener
data-ready callback, and an RCU stall in tipc_topsrv_exit_net()
while the walk spun under idr_lock.
Clear srv->listener under idr_lock so it acts as a shutdown flag,
skip queue_work() once it is NULL, destroy the workqueues to flush
in-flight work, and only then close the remaining connections.
Refuse tipc_conn_lookup() after that flag is cleared, and drop
idr_lock when the teardown walk finds no connection, so an
in-flight subscription event cannot pin idr_in_use while the
walk holds the lock.
v3 supersedes the narrower in-thread diff Tung Quang Nguyen
posted on 2026-09-23. It keeps his teardown order and adds the
lookup refusal and the empty-idr unlock.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/7f796bb3b440d7f1b14c0e3b520462eb34f553af
- git.kernel.org/stable/c/da9c16568bc79140a54c1f5fcf07a0305df47b37
- git.kernel.org/stable/c/0af8780bdfdfc91fb9127bddb9c48fab67dc9d9e
- git.kernel.org/stable/c/fb717c536af2aafeca520ff11d1e0f25f7ab8fa9
- git.kernel.org/stable/c/3acdd44385bc7e2e57605e073691ce69cc5a960d
- nvd.nist.gov/vuln/detail/CVE-2026-99054
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON