CVE-2026-53389

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-45511 (ENISA EUVD) · GHSA-x37v-hm75-xvf9 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Jul 21, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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.

Patch Availability(14)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)
  • every version up to 6.12.95-1: fixed in 6.12.95-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)
  • every version up to 7.1.3-1: fixed in 7.1.3-1
—

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 243 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 143 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53389?
CVE-2026-53389 is a high-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2026-53389 published?
The CVE record for CVE-2026-53389 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-53389 actively exploited?
CVE-2026-53389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53389?
CVE-2026-53389 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53389?
A fix for CVE-2026-53389 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53389 are linked in the Vendor Advisories panel on this page.

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.