Linux
tipc: fix double-free in tipc_buf_append()
In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < a438975a6dcdbd70865978c021650d1485586f0b
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < 4ee4deadaae7cb2e3d53af0fc889cf92a73413c0
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < d3556656c6daebf8def751c7e71d11dd0a180d24
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < 0274f24485fc38032d4093e463dc3ff5c7a667c9
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < 4d104882bc815d4ec666ace9155f5f52715879a6
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < 1d5e589055880fae229e229e1929e087dbe08cf3
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < 29940fff14110ca48c5ccc168d121665b51bb778
- >= d618d09a68e4eed7a435beb2e355250f6f40664a, < d293ca716e7d5dffdaecaf6b9b2f857a33dc3d3a
Fixed in a438975a6dcdbd70865978c021650d1485586f0b, 4ee4deadaae7cb2e3d53af0fc889cf92a73413c0, d3556656c6daebf8def751c7e71d11dd0a180d24, 0274f24485fc38032d4093e463dc3ff5c7a667c9, 4d104882bc815d4ec666ace9155f5f52715879a6, 1d5e589055880fae229e229e1929e087dbe08cf3, 29940fff14110ca48c5ccc168d121665b51bb778, d293ca716e7d5dffdaecaf6b9b2f857a33dc3d3a
- 4.15
Fixed in 0, 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, 7.1
Mitigation
Upgrade Linux to a438975a6dcdbd70865978c021650d1485586f0b or 4ee4deadaae7cb2e3d53af0fc889cf92a73413c0 or d3556656c6daebf8def751c7e71d11dd0a180d24 or 0274f24485fc38032d4093e463dc3ff5c7a667c9 or 4d104882bc815d4ec666ace9155f5f52715879a6 or 1d5e589055880fae229e229e1929e087dbe08cf3 or 29940fff14110ca48c5ccc168d121665b51bb778 or d293ca716e7d5dffdaecaf6b9b2f857a33dc3d3a or later.
Upgrade Linux to 0 or 5.10.258 or 5.15.209 or 6.1.175 or 6.6.141 or 6.12.91 or 6.18.33 or 7.0.10 or 7.1 or later.
Timeline
Days relative to CVE publicationFirst public PoC 98 days after publication; not in CISA KEV. First PoC: CaptainAI-Labs/CaptainAI-LPE-CVE-2026-52993 (created 30 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| CaptainAI-Labs/CaptainAI-LPE-CVE-2026-52993 | 30 Sep 2026 +98 d | 0 | PoC
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.