CVE-2026-74623

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: 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: atlantic: free stranded TX buffers on ring deinit

aq_vec_deinit() drains the TX rings with a single aq_ring_tx_clean() call, which frees at most AQ_CFG_TX_CLEAN_BUDGET (256) descriptors and stops at hw_head, which no longer moves once aq_vec_stop() has stopped the hardware and NAPI. Completed descriptors beyond the budget and everything still posted in [hw_head, sw_tail) keep their skb or xdp_frame when the interface goes down: aq_vec_ring_free() then frees the buffer ring and the references are lost for good.

Today this is a silent memory leak on every interface down under TX/XDP_TX load. With the conversion of the RX path to page_pool posted for net-next it becomes much more visible: XDP_TX frames carry fragment references on the RX ring's page_pool, so a single stranded frame keeps the pool's inflight count above zero forever. page_pool_destroy() then never completes, the pool is leaked together with its pages, and "page_pool_release_retry() stalled pool shutdown" is warned every 60 seconds from that point on, on every ifdown, XDP detach or ring resize under XDP_TX load.

Bring back aq_ring_tx_deinit() as it was before the removal and use it for teardown again, with one extension: TX rings can hold xdp_frames nowadays, so release those too. They are returned with xdp_return_frame() since this runs in process context.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 23, 2026

Vendor Advisories for CVE-2026-74623(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 16× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 17:36 UTCGHSA enrichment
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 15:07 UTCEG score recompute
  6. 2026-08-26 15:07 UTCGHSA enrichment
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-24 14:18 UTCEPSS rescore
  10. 2026-08-23 13:19 UTCGHSA enrichment
  11. 2026-08-23 13:19 UTCNVD update
  12. 2026-08-23 13:06 UTCGHSA enrichment
  13. 2026-08-23 13:05 UTCMITRE cvelistV5
  14. 2026-08-22 16:24 UTCNVD update
  15. 2026-08-22 15:42 UTCEG score recompute
  16. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74623?
CVE-2026-74623 is a publicly disclosed vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net: atlantic: free stranded TX buffers on ring deinit aqvecdeinit() drains the TX rings with a single aqringtx_clean() call, which frees at most AQCFGTXCLEANBUDGET (256) descriptors and stops at hwhead, which no longer moves once…
When was CVE-2026-74623 disclosed?
CVE-2026-74623 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74623 actively exploited?
CVE-2026-74623 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 92.7% of all scored CVEs.
How do I remediate CVE-2026-74623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74623, 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-74623

Explore →

Is Your Infrastructure Affected by CVE-2026-74623?

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