CVE-2026-74623 — net: atlantic: free stranded TX buffers on ring deinit
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < a14ceebd13bf857bfca052bc5a6bd49e737912be≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < 4f1c20873f70b4b22ef86dc38dad1fda8e169bcd≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < 307d80193b4a4a75b8dc4e0d3162be3755abbed7≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < 7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < 3447641d361dcc5511841d986ad4d849b2900d9b≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < b13202d401e1a20fec89b0cda733dcbaf279f79d≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < dd633280de7fdfd60dc4fcf63d04e2ad95b43269≥ eb36bedf28be6d986bdbcfa375bab08ffa45efd8 and < 452636ea5410a96e02ebaaf80b21e3620b98e0dd and 1 moreversion 4.11 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
10 on the record
- git.kernel.org/stable/c/3447641d361dcc5511841d986ad4d849b2900d9b
- git.kernel.org/stable/c/7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c
- nvd.nist.gov/vuln/detail/CVE-2026-74623
- git.kernel.org/stable/c/4f1c20873f70b4b22ef86dc38dad1fda8e169bcd
- git.kernel.org/stable/c/dd633280de7fdfd60dc4fcf63d04e2ad95b43269
- github.com/advisories/GHSA-98pj-4qrw-8mcj
- git.kernel.org/stable/c/452636ea5410a96e02ebaaf80b21e3620b98e0dd
- git.kernel.org/stable/c/b13202d401e1a20fec89b0cda733dcbaf279f79d
- git.kernel.org/stable/c/a14ceebd13bf857bfca052bc5a6bd49e737912be
- git.kernel.org/stable/c/307d80193b4a4a75b8dc4e0d3162be3755abbed7
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74623 is "net: atlantic: free stranded TX buffers on ring deinit", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.