CVE-2026-53389

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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:

net/tcp-ao: fix use-after-free of key in del_async path

In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN.

When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key->sndid and rnext_key->rcvid from freed slab memory.

Clear current_key and rnext_key in the del_async path when they reference the key being deleted.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

net/tcp-ao: fix use-after-free of key in del_async path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/tcp-ao: fix use-after-free of key in del_async path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ddc29a094d96e9b3aa280433c6dc443df9eabf2
generic

net/tcp-ao: fix use-after-free of key in del_async path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ce7ef41743740ce15c2061561b784148b565b3f
generic

net/tcp-ao: fix use-after-free of key in del_async path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ba9950bc9078e19b69cca1e56d1553b125c6857

Vendor Advisories for CVE-2026-53389(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (153 versions)7.1.3-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 106× 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 141 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53389?
CVE-2026-53389 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcpaodeletekey(), the delasync path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN…
When was CVE-2026-53389 disclosed?
CVE-2026-53389 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53389 actively exploited?
CVE-2026-53389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53389?
CVE-2026-53389 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53389?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53389, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53389

Explore →

Is Your Infrastructure Affected by CVE-2026-53389?

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