Kernel memory corruption via stale TIPC crypto reference
Published Jun 18, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel TIPC encryption allows remote authenticated users to corrupt kernel memory through crafted peer traffic. During asynchronous AEAD completion, tipc_aead_encrypt_done dereferences a tipc_crypto object after namespace deletion frees it because the encrypt path fails to retain the network-namespace reference. Low-privileged namespace access and an enabled encrypted TIPC bearer are required; successful exploitation can disclose or corrupt kernel memory or panic the host.
Summary
What happened
Use-after-free in Linux kernel TIPC encryption allows remote authenticated users to corrupt kernel memory through crafted peer traffic. During asynchronous AEAD completion, tipc_aead_encrypt_done dereferences a tipc_crypto object after namespace deletion frees it because the encrypt path fails to retain the network-namespace reference. Low-privileged namespace access and an enabled encrypted TIPC bearer are required; successful exploitation can disclose or corrupt kernel memory or panic the host.
The record
- CVE
- CVE-2025-38052
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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 <4a0fddc2c0d5c28aec8c262ad4603be0bef1938c
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <689a205cd968a1572ab561b0c4c2d50a10e9d3b0
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <b19fc1d0be3c3397e5968fe2627f22e7f84673b1
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <b8fcae6d2e93c54cacb8f579a77d827c1c643eb5
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <d42ed4de6aba232d946d20653a70f79158a6535b
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <e279024617134c94fd3e37470156534d5f2b3472
- Affected versionversion=fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 <f5c2c4eaaa5a8e7e0685ec031d480e588e263e59
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
- Syzbot TIPC namespace-teardown reproducerproof of concept · demonstrated
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