High [CVE-2026-52993] fix double-free in tipc_buf_append
This high-severity Red Hat Linux advisory covers CVE-2026-52993 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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. A flaw was found in the Linux kernel's Transparent Inter-Process Communication (TIPC) module.
This vulnerability, a double-free, occurs when the `tipc_buf_append()` function incorrectly handles memory after a socket buffer (skb) reallocation. An attacker could potentially exploit this to cause system instability or a denial of service.
In some scenarios, this type of memory corruption could also lead to arbitrary code execution. Red Hat severity: Important — CVSS 7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).
Weakness: CWE-763.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
- kernel-0:6.12.0-211.40.1.el10_2
- kernel-rt-0:4.18.0-553.147.1.rt7.488.el8_10
- kernel-0:4.18.0-553.147.1.el8_10
- kernel-0:4.18.0-305.208.1.el8_4
- kernel-0:4.18.0-372.216.1.el8_6
- kernel-0:4.18.0-477.168.1.el8_8
- kernel-0:5.14.0-687.33.1.el9_8
- RHSA-2026:47017
- RHSA-2026:45116
- RHSA-2026:45115
- RHSA-2026:69874
- RHSA-2026:69906
- RHSA-2026:69837
- RHSA-2026:49212
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Mitigation
Upgrade to a fixed release: kernel-0:6.12.0-211.40.1.el10_2, kernel-rt-0:4.18.0-553.147.1.rt7.488.el8_10, kernel-0:4.18.0-553.147.1.el8_10, kernel-0:4.18.0-305.208.1.el8_4, kernel-0:4.18.0-372.216.1.el8_6, kernel-0:4.18.0-477.168.1.el8_8. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.