CVE-2026-53215

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.5%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 6.12.94, <a88b3293b556f4d8fba11db9a8061a6b0d3b69e6, 07dd0a7aae7f72af7cec18909581c2bb570edddc, 0, 95a936364f2685e9e040c6b179b553604d96de22, <5.8, 6.1.176, 5.15.210, <=6.6.*, 7.0.13, 6.18.36, <8a2126c5afe89f8ceeb60a3afb9f075b736194cd, 5.8.2, 7.1, <a03cdcedb2cbcc42551dc3e4746929e93c5352d5, <=6.18.*, 5.9, <5.9, <5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6, fba2cf348d9eb50b2049a73cc09313dab6d293f1, <=*, <=5.15.*, <02e1b5c4d3b4c658b72c145427cded1bba613fc1, <d0c8c4fbd22d260fe28530260656c5fb3c20ce84, 6.6.143, <580f92f27cb8724bcc4be98ee89890eab524a2ae, 5.7.15

Description

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: refill RX buffers before XDP or skb use The RX error path returns the current descriptor buffer to the hardware BM pool. That is only valid while the driver still owns the buffer. mvpp2_rx_refill() can fail after the current buffer has been handed to XDP or attached to an skb. In those cases mvpp2_run_xdp() may have recycled, redirected, or queued the page for XDP_TX, and an skb free also retires the data buffer. Returning such a buffer to BM lets hardware DMA into memory that is no longer owned by the RX ring. Refill the BM pool before handing the current buffer to XDP or to the skb. If the allocation fails there, drop the packet and return the still-owned current buffer to BM, preserving the pool depth. Once the refill succeeds, later local drops retire/free the current buffer instead of returning it to BM.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 6.12.94, <a88b3293b556f4d8fba11db9a8061a6b0d3b69e6, 07dd0a7aae7f72af7cec18909581c2bb570edddc, 0, 95a936364f2685e9e040c6b179b553604d96de22, <5.8, 6.1.176, 5.15.210, <=6.6.*, 7.0.13, 6.18.36, <8a2126c5afe89f8ceeb60a3afb9f075b736194cd, 5.8.2, 7.1, <a03cdcedb2cbcc42551dc3e4746929e93c5352d5, <=6.18.*, 5.9, <5.9, <5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6, fba2cf348d9eb50b2049a73cc09313dab6d293f1, <=*, <=5.15.*, <02e1b5c4d3b4c658b72c145427cded1bba613fc1, <d0c8c4fbd22d260fe28530260656c5fb3c20ce84, 6.6.143, <580f92f27cb8724bcc4be98ee89890eab524a2ae, 5.7.15) 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