CVE-2026-52993

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
—
EPSS
28.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 16, 2026
Patch available. Sources: redhat.
redhat

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

https://bugzilla.redhat.com/show_bug.cgi?id=2492437
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-52993
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d3556656c6daebf8def751c7e71d11dd0a180d24
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d293ca716e7d5dffdaecaf6b9b2f857a33dc3d3a
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a438975a6dcdbd70865978c021650d1485586f0b
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ee4deadaae7cb2e3d53af0fc889cf92a73413c0
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d104882bc815d4ec666ace9155f5f52715879a6
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/29940fff14110ca48c5ccc168d121665b51bb778
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d5e589055880fae229e229e1929e087dbe08cf3
generic

tipc: fix double-free in tipc_buf_append() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0274f24485fc38032d4093e463dc3ff5c7a667c9

Vendor Advisories for CVE-2026-52993(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 174× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 174 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 04:49 UTCVendor advisory
  9. 2026-07-17 04:49 UTCGHSA enrichment
  10. 2026-07-17 00:38 UTCVendor advisory
  11. 2026-07-17 00:38 UTCGHSA enrichment
  12. 2026-07-16 20:28 UTCVendor advisory
  13. 2026-07-16 20:28 UTCGHSA enrichment
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-16 16:24 UTCVendor advisory
  16. 2026-07-16 16:24 UTCGHSA enrichment
  17. 2026-07-16 11:16 UTCVendor advisory
  18. 2026-07-16 11:16 UTCGHSA enrichment
  19. 2026-07-16 07:11 UTCVendor advisory
  20. 2026-07-16 07:11 UTCGHSA enrichment
  21. 2026-07-16 02:59 UTCVendor advisory
  22. 2026-07-16 02:59 UTCGHSA enrichment
  23. 2026-07-15 22:55 UTCVendor advisory
  24. 2026-07-15 22:55 UTCGHSA enrichment
  25. 2026-07-15 18:50 UTCVendor advisory
Show 75 more
  1. 2026-07-15 18:50 UTCGHSA enrichment
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 14:24 UTCVendor advisory
  5. 2026-07-15 14:24 UTCGHSA enrichment
  6. 2026-07-15 10:18 UTCVendor advisory
  7. 2026-07-15 10:18 UTCGHSA enrichment
  8. 2026-07-15 06:11 UTCVendor advisory
  9. 2026-07-15 06:11 UTCGHSA enrichment
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 01:28 UTCVendor advisory
  13. 2026-07-15 01:28 UTCGHSA enrichment
  14. 2026-07-14 21:25 UTCVendor advisory
  15. 2026-07-14 21:24 UTCGHSA enrichment
  16. 2026-07-14 17:21 UTCVendor advisory
  17. 2026-07-14 17:21 UTCGHSA enrichment
  18. 2026-07-14 13:16 UTCVendor advisory
  19. 2026-07-14 13:16 UTCGHSA enrichment
  20. 2026-07-14 09:11 UTCVendor advisory
  21. 2026-07-14 09:11 UTCGHSA enrichment
  22. 2026-07-14 05:05 UTCVendor advisory
  23. 2026-07-14 05:05 UTCGHSA enrichment
  24. 2026-07-14 00:59 UTCVendor advisory
  25. 2026-07-14 00:59 UTCGHSA enrichment
  26. 2026-07-13 22:31 UTCEPSS rescore
  27. 2026-07-13 20:56 UTCGHSA enrichment
  28. 2026-07-13 16:52 UTCGHSA enrichment
  29. 2026-07-13 11:58 UTCGHSA enrichment
  30. 2026-07-13 07:53 UTCGHSA enrichment
  31. 2026-07-13 06:13 UTCEPSS rescore
  32. 2026-07-13 06:13 UTCEPSS rescore
  33. 2026-07-13 03:49 UTCVendor advisory
  34. 2026-07-13 03:49 UTCGHSA enrichment
  35. 2026-07-12 23:44 UTCVendor advisory
  36. 2026-07-12 23:44 UTCGHSA enrichment
  37. 2026-07-12 19:40 UTCVendor advisory
  38. 2026-07-12 19:40 UTCGHSA enrichment
  39. 2026-07-12 15:36 UTCVendor advisory
  40. 2026-07-12 15:36 UTCGHSA enrichment
  41. 2026-07-12 11:19 UTCVendor advisory
  42. 2026-07-12 11:19 UTCGHSA enrichment
  43. 2026-07-12 07:15 UTCVendor advisory
  44. 2026-07-12 07:15 UTCGHSA enrichment
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-12 03:11 UTCVendor advisory
  47. 2026-07-12 03:10 UTCGHSA enrichment
  48. 2026-07-11 23:06 UTCVendor advisory
  49. 2026-07-11 23:06 UTCGHSA enrichment
  50. 2026-07-11 19:03 UTCVendor advisory
  51. 2026-07-11 19:03 UTCGHSA enrichment
  52. 2026-07-11 14:58 UTCVendor advisory
  53. 2026-07-11 14:58 UTCGHSA enrichment
  54. 2026-07-11 10:54 UTCVendor advisory
  55. 2026-07-11 10:54 UTCGHSA enrichment
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-11 06:50 UTCVendor advisory
  59. 2026-07-11 06:50 UTCGHSA enrichment
  60. 2026-07-11 02:46 UTCVendor advisory
  61. 2026-07-11 02:46 UTCGHSA enrichment
  62. 2026-07-10 22:42 UTCVendor advisory
  63. 2026-07-10 22:42 UTCGHSA enrichment
  64. 2026-07-10 18:32 UTCVendor advisory
  65. 2026-07-10 18:32 UTCGHSA enrichment
  66. 2026-07-10 14:28 UTCVendor advisory
  67. 2026-07-10 14:28 UTCGHSA enrichment
  68. 2026-07-10 10:24 UTCVendor advisory
  69. 2026-07-10 10:24 UTCGHSA enrichment
  70. 2026-07-10 06:20 UTCGHSA enrichment
  71. 2026-07-10 02:17 UTCGHSA enrichment
  72. 2026-07-09 22:12 UTCGHSA enrichment
  73. 2026-07-09 19:10 UTCEPSS rescore
  74. 2026-07-09 19:10 UTCEPSS rescore
  75. 2026-07-09 18:08 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-52993?
CVE-2026-52993 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipcbufappend() tipcmsgvalidate() can potentially reallocate the skb it is validating, freeing the old one. In tipcbufappend(), it was being called with a pointer to a local variable which was a copy of the…
When was CVE-2026-52993 disclosed?
CVE-2026-52993 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52993 actively exploited?
CVE-2026-52993 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52993?
CVE-2026-52993 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-52993?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52993, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52993

Explore →

Is Your Infrastructure Affected by CVE-2026-52993?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs