Kernel memory corruption via TIPC skb double-free
Published Jun 24, 2026 · Updated Jun 24, 2026
Double-free in Linux Kernel TIPC allows remote attackers to corrupt kernel memory through malformed TIPC message reassembly. tipc_buf_append() passes a copied skb pointer to tipc_msg_validate(), which reallocates and frees the buffer before failure handling frees the stale original pointer again. The condition requires TIPC to be enabled and network-reachable; successful triggering performs the second free and corrupts kernel memory.
Summary
What happened
Double-free in Linux Kernel TIPC allows remote attackers to corrupt kernel memory through malformed TIPC message reassembly. tipc_buf_append() passes a copied skb pointer to tipc_msg_validate(), which reallocates and frees the buffer before failure handling frees the stale original pointer again. The condition requires TIPC to be enabled and network-reachable; successful triggering performs the second free and corrupts kernel memory.
The record
- CVE
- CVE-2026-52993
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-415, CWE-763, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=4.15
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <0274f24485fc38032d4093e463dc3ff5c7a667c9
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <1d5e589055880fae229e229e1929e087dbe08cf3
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <29940fff14110ca48c5ccc168d121665b51bb778
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <4d104882bc815d4ec666ace9155f5f52715879a6
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <4ee4deadaae7cb2e3d53af0fc889cf92a73413c0
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <a438975a6dcdbd70865978c021650d1485586f0b
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <d293ca716e7d5dffdaecaf6b9b2f857a33dc3d3a
- Affected versionversion=d618d09a68e4eed7a435beb2e355250f6f40664a <d3556656c6daebf8def751c7e71d11dd0a180d24
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
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