CVE-2026-52993: tipc: fix double-free in tipc_buf_append()

Published Jun 24, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

Other sources

In tipcbufappend of msg.c, there is a possible remote code execution due to a double free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

— OSV

tipc: fix double-free in tipcbufappend()

— Microsoft

Affected Software

13 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.139.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=4.15<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10
debian/linux<=5.10.223-1
5.10.262-16.1.176-16.1.180-16.12.94-16.12.107-17.1.8-27.1.12-1
debian/linux-6.1
6.1.180-1~deb11u1
Google Android
android/:linux_kernel:>=:0<:2026-09-05
:2026-09-05

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.143.1-1
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.107-1Fixed in 7.1.8-2Fixed in 7.1.12-1
  3. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.180-1~deb11u1
  4. Upgrade

    Upgrade android/:linux_kernel: to a version that resolves this vulnerability.

    Fixed in :2026-09-05
  5. Compensating control

    Modify tipc_buf_append() to check whether head points to a newly allocated reassembled skb and, if so, reassign *headbuf to that skb before later freeing operations, preventing the error path from freeing the original skb pointer after it has been freed.

Event History

Jun 24, 2026
CVE Published
via MITRE·04:29 PM
Data Sourced
via MITRE·04:29 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·06:12 PM
DescriptionSeverityAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeaknessAffected Software
Sep 1, 2026
Advisory Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionAffected Software
Sep 8, 2026
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software

Frequently Asked Questions

1

What conditions trigger the double-free?

The issue occurs when tipc_msg_validate() reallocates the skb being validated and validation then fails. The error path in tipc_buf_append() can subsequently free the original skb pointer even though it was already freed during reallocation.

2

Does exploitation require local access, credentials, or user interaction?

The supplied CVSS vector rates the issue as network-reachable, low complexity, requiring no privileges and no user interaction. It also indicates potential high impact to confidentiality, integrity, and availability.

3

Which software is identified as affected?

The listed software includes the Linux kernel, Microsoft azl3 kernel 6.6.139.1-1, debian/linux, and debian/linux-6.1. The provided data does not identify affected or fixed version ranges for the general Linux kernel entries.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203