CVE-2026-99054

tipc: destroy topsrv workqueues before closing connections

State
Published
Severity
7.8 High
Published
Oct 23, 2026
Updated
Oct 30, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before 09dbd610f78aaed65d7b379c270ce4090a8151acAffected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before 21622e5ae8b232c2e64eb1adf5546cf078d2987dAffected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before 7167afaaaee37191f8b6afa0c91e0fef41460705Affected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before 7f796bb3b440d7f1b14c0e3b520462eb34f553afAffected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before da9c16568bc79140a54c1f5fcf07a0305df47b37Affected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before 0af8780bdfdfc91fb9127bddb9c48fab67dc9d9eAffected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before fb717c536af2aafeca520ff11d1e0f25f7ab8fa9Affected
  • c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f to before 3acdd44385bc7e2e57605e073691ce69cc5a960dAffected
LinuxLinux
  • 3.11Affected
  • before 3.11Not affected
  • 5.10.273 through 5.10.*Not affected
  • 5.15.224 through 5.15.*Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.113 through 6.12.*Not affected
  • 6.18.57 through 6.18.*Not affected
  • 7.2.11 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.