CVE-2026-63801
Linux kernel TIPC use-after-free in aead decrypt allows kernel crash/info leak.
Is CVE-2026-63801 being exploited?
Not confirmed. CVE-2026-63801 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-63801?
CVE-2026-63801 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-63801?
Yes. A fix has been recorded for CVE-2026-63801. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63801 affect?
CVE-2026-63801 affects Linux kernel (net/tipc/crypto), Kernels with TIPC_CRYPTO enabled, Systems using cryptd offload. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63801?
Apply vendor/kernel updates with the TIPC decrypt fix or disable TIPC/TIPC_CRYPTO if unused.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted encrypted TIPC frames can trigger slab use-after-free during netns teardown, causing kernel OOPS/DoS and possible memory disclosure.
Patch when possible
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < 171d31245d11bf84836fad3b394cb465a4d008ec
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < 2d1f21419ec121232c916d3a3fc9b6766473a0e7
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < 0a780653b2a7569a7af9be7d0b00b1251baca63a
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < eaca7dae02fab70c8d223cffe03cec1b93249ce2
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < dca7713fe044a2067387948557ea099056e1679e
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < e18769616fd5a90ec1e12aabbba544c488284292
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < 1eea5e1820a2f5164d706bd1277bc97ff31ce32d
- affected>= fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and < bda3348872a2ef0d19f2df6aa8cb5025adce2f20
- affected5.5
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.