net: atlantic: free stranded TX buffers on ring deinit
Summary
| CVE | CVE-2026-74623 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-22 16:16:35 UTC |
| Updated | 2026-08-22 16:16:35 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected eb36bedf28be6d986bdbcfa375bab08ffa45efd8 307d80193b4a4a75b8dc4e0d3162be3755abbed7 git |
Not specified |
| CNA |
Linux |
Linux |
affected eb36bedf28be6d986bdbcfa375bab08ffa45efd8 7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c git |
Not specified |
| CNA |
Linux |
Linux |
affected eb36bedf28be6d986bdbcfa375bab08ffa45efd8 3447641d361dcc5511841d986ad4d849b2900d9b git |
Not specified |
| CNA |
Linux |
Linux |
affected eb36bedf28be6d986bdbcfa375bab08ffa45efd8 b13202d401e1a20fec89b0cda733dcbaf279f79d git |
Not specified |
| CNA |
Linux |
Linux |
affected eb36bedf28be6d986bdbcfa375bab08ffa45efd8 dd633280de7fdfd60dc4fcf63d04e2ad95b43269 git |
Not specified |
| CNA |
Linux |
Linux |
affected eb36bedf28be6d986bdbcfa375bab08ffa45efd8 452636ea5410a96e02ebaaf80b21e3620b98e0dd git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.11 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.11 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.183 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.152 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.104 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.45 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.9 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/307d80193b4a4a75b8dc4e0d3162be3755abbed7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3447641d361dcc5511841d986ad4d849b2900d9b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/452636ea5410a96e02ebaaf80b21e3620b98e0dd |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b13202d401e1a20fec89b0cda733dcbaf279f79d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/dd633280de7fdfd60dc4fcf63d04e2ad95b43269 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.