Widespread Linux kernel vulnerability affecting the TIPC subsystem; can allow remote kernel compromise across many distributions and enterprise systems.
CVE-2026-74255
Linux kernel TIPC use-after-free allows remote kernel compromise or crash.
Is CVE-2026-74255 being exploited?
Not confirmed. CVE-2026-74255 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-74255?
CVE-2026-74255 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74255?
Yes. A fix has been recorded for CVE-2026-74255. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74255 affect?
CVE-2026-74255 affects Linux kernel (TIPC subsystem), Linux distributions running affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74255?
Apply vendor kernel updates or upstream patch and restrict/ firewall TIPC exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can send crafted TIPC packets to trigger a kernel use-after-free, enabling RCE, privilege escalation, or denial of service.
Immediate action required
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < 609ced2301be1df7e7ed2ef47d1d916674e6ba3b
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < 71aafa16d79b107b33837f60b6cbc7d0cb8c5708
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < f4002f1c669cc02e3763f479fc25ff1dfa9e2420
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < 50ff092633b06382e5091dd5b093ce943d4ac2f9
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < aef12b5ce793dea6b3a97a58fd0f946000ae8945
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < 0d8a12d7143126afdf9fbe2e3d438650dd6603ed
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < 35e0297a93c3c34a3924eeef816c03504e3ab5c5
- affected>= 282b3a056225b35024246f63feb91d769d714dad and < f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6
- affected4.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.