Memory disclosure or crash via asynchronous TIPC use-after-free
Published Jul 19, 2026 · Updated Jul 19, 2026
Use-after-free in Linux Kernel TIPC crypto allows attackers to disclose kernel memory or crash systems through crafted encrypted network traffic. tipc_aead_decrypt() starts asynchronous decryption without holding a network-namespace reference, so tipc_aead_decrypt_done() reads freed per-namespace crypto state after teardown. Exploitation requires TIPC crypto with a bearer and cluster key, asynchronous crypto offload, crafted encrypted frames, and control over repeated network-namespace teardown; observed consequences are disclosure or a kernel crash.
Summary
What happened
Use-after-free in Linux Kernel TIPC crypto allows attackers to disclose kernel memory or crash systems through crafted encrypted network traffic. tipc_aead_decrypt() starts asynchronous decryption without holding a network-namespace reference, so tipc_aead_decrypt_done() reads freed per-namespace crypto state after teardown. Exploitation requires TIPC crypto with a bearer and cluster key, asynchronous crypto offload, crafted encrypted frames, and control over repeated network-namespace teardown; observed consequences are disclosure or a kernel crash.
The record
- CVE
- CVE-2026-63801
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=5.5
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <0a780653b2a7569a7af9be7d0b00b1251baca63a
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <171d31245d11bf84836fad3b394cb465a4d008ec
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <1eea5e1820a2f5164d706bd1277bc97ff31ce32d
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <2d1f21419ec121232c916d3a3fc9b6766473a0e7
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <bda3348872a2ef0d19f2df6aa8cb5025adce2f20
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <dca7713fe044a2067387948557ea099056e1679e
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <e18769616fd5a90ec1e12aabbba544c488284292
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <eaca7dae02fab70c8d223cffe03cec1b93249ce2
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.
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