Kernel crash via TIPC media-pointer race
Published Aug 15, 2026 · Updated Aug 15, 2026
Use-after-free in the Linux TIPC subsystem allows remote attackers to crash the kernel through a media-pointer race. The tipc_disable_l2_media() path leaves b->media_ptr valid while synchronize_net() waits, so a concurrent RCU reader can retain the device before bearer_disable() clears it and the device is freed. Reachability requires an enabled TIPC Layer 2 bearer and a race between bearer shutdown and message transmission; the bounded consequence is a kernel crash.
Summary
What happened
Use-after-free in the Linux TIPC subsystem allows remote attackers to crash the kernel through a media-pointer race. The tipc_disable_l2_media() path leaves b->media_ptr valid while synchronize_net() waits, so a concurrent RCU reader can retain the device before bearer_disable() clears it and the device is freed. Reachability requires an enabled TIPC Layer 2 bearer and a race between bearer shutdown and message transmission; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2026-74255
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, CWE-788, CWE-825
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=282b3a056225b35024246f63feb91d769d714dad <0d8a12d7143126afdf9fbe2e3d438650dd6603ed
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <35e0297a93c3c34a3924eeef816c03504e3ab5c5
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <50ff092633b06382e5091dd5b093ce943d4ac2f9
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <609ced2301be1df7e7ed2ef47d1d916674e6ba3b
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <71aafa16d79b107b33837f60b6cbc7d0cb8c5708
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <aef12b5ce793dea6b3a97a58fd0f946000ae8945
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <f4002f1c669cc02e3763f479fc25ff1dfa9e2420
- Affected versionversion=282b3a056225b35024246f63feb91d769d714dad <f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6
- Affected versionversion=4.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo