Heimdall Security Logo

CVE-2026-74623

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.6.152, <b13202d401e1a20fec89b0cda733dcbaf279f79d, 5.15.217, 4.11, 0, <=7.1.*, <452636ea5410a96e02ebaaf80b21e3620b98e0dd, <7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c, <=5.10.*, <=6.6.*, <dd633280de7fdfd60dc4fcf63d04e2ad95b43269, 7.1.9, 5.10.266, 6.1.183, <4f1c20873f70b4b22ef86dc38dad1fda8e169bcd, <4.11, <=6.18.*, eb36bedf28be6d986bdbcfa375bab08ffa45efd8, 6.12.104, <3447641d361dcc5511841d986ad4d849b2900d9b, 6.18.45, <=*, <=5.15.*, <a14ceebd13bf857bfca052bc5a6bd49e737912be, 7.2, <307d80193b4a4a75b8dc4e0d3162be3755abbed7

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.

Gravité et risque d'exploitation

CVE-2026-74623 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 6.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.6.152, <b13202d401e1a20fec89b0cda733dcbaf279f79d, 5.15.217, 4.11, 0, <=7.1.*, <452636ea5410a96e02ebaaf80b21e3620b98e0dd, <7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c, <=5.10.*, <=6.6.*, <dd633280de7fdfd60dc4fcf63d04e2ad95b43269, 7.1.9, 5.10.266, 6.1.183, <4f1c20873f70b4b22ef86dc38dad1fda8e169bcd, <4.11, <=6.18.*, eb36bedf28be6d986bdbcfa375bab08ffa45efd8, 6.12.104, <3447641d361dcc5511841d986ad4d849b2900d9b, 6.18.45, <=*, <=5.15.*, <a14ceebd13bf857bfca052bc5a6bd49e737912be, 7.2, <307d80193b4a4a75b8dc4e0d3162be3755abbed7) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE