CVE-2026-0193: Linux kernel TIPC double fetch information disclosure

CVE-2026-0193 · Severity: info · Published 2026-11-10

A race condition in the Linux kernel's TIPC networking component allows a local attacker to read sensitive kernel memory by exploiting a double fetch vulnerability in message handling. This could expose confidential data such as encryption keys or other protected information stored in kernel memory.

Technologies: Linux kernel.

Quick answers

Is CVE-2026-0193 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-0193 being exploited in the wild.
How severe is CVE-2026-0193?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Linux kernel TIPC subsystem.
Is there a fix for CVE-2026-0193?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-0193 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-0193?
Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A double fetch time-of-check-time-of-use (TOCTOU) vulnerability exists in handle_rx_msg of tipc_virtio_dev, where kernel memory is read twice without synchronization, allowing an attacker to change values between reads. Exploitation requires local execution privileges and user interaction, and permits information disclosure by reading uninitialized or protected kernel memory.

Affected products

  • Linux kernel TIPC subsystem

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.