CVE-2026-74490
Linux kernel TIPC use-after-free in poll trace can crash or enable kernel compromise.
Is CVE-2026-74490 being exploited?
Not confirmed. CVE-2026-74490 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-74490?
CVE-2026-74490 is rated High with a CVSS score of 8.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-74490?
Yes. A fix has been recorded for CVE-2026-74490. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74490 affect?
CVE-2026-74490 affects Linux kernel (TIPC subsystem), Linux distributions with TIPC enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74490?
Apply vendor kernel updates immediately; disable TIPC if unused; restrict access to TIPC endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in TIPC poll trace: attackers interacting with TIPC sockets can cause kernel crash (DoS) or potentially achieve kernel code execution/privilege escalation.
Immediate action required
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < 3cd57c6b210d50fd1f7ac1720442ba5be5dc94f8
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < ae7fc824970888b4fdaa076819c9a6f2fcede275
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < 78706367fe1b98aee0a6de27c62b7f1e3035f38d
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < d7940bb6a8e7ab28f972c2875cb05783216312dc
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < 5e82beba4bc1f91d0e64c9c43f2b2fa9cd1c2a7d
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < bed792737b5f1ba773054dbe984502958bdfe6ce
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < ac2f787980fdf4364cd5651a4c8128e59b8de3aa
- affected>= b4b9771bcbbd5839b0f77aba55e2f85989ed6779 and < b4f1719dfea023220e0e6bd892b087d76b2a6a49
- affected5.0
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.