Answer in brief
CVE-2026-53215 records a Critical severity (CVSS 9.8) vulnerability in net: mvpp2: refill RX buffers before XDP or skb use. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53215 records a Critical severity (CVSS 9.8) vulnerability in net: mvpp2: refill RX buffers before XDP or skb use. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=07dd0a7aae7f72af7cec18909581c2bb570edddc <a88b3293b556f4d8fba11db9a8061a6b0d3b69e6 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <a03cdcedb2cbcc42551dc3e4746929e93c5352d5 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <580f92f27cb8724bcc4be98ee89890eab524a2ae || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <d0c8c4fbd22d260fe28530260656c5fb3c20ce84 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <8a2126c5afe89f8ceeb60a3afb9f075b736194cd || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <02e1b5c4d3b4c658b72c145427cded1bba613fc1 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6 || 95a936364f2685e9e040c6b179b553604d96de22 || fba2cf348d9eb50b2049a73cc09313dab6d293f1 || >=5.7.15 <5.8 || >=5.8.2 <5.9 | a88b3293b556f4d8fba11db9a8061a6b0d3b69e6, a03cdcedb2cbcc42551dc3e4746929e93c5352d5, 580f92f27cb8724bcc4be98ee89890eab524a2ae, d0c8c4fbd22d260fe28530260656c5fb3c20ce84, 8a2126c5afe89f8ceeb60a3afb9f075b736194cd, 02e1b5c4d3b4c658b72c145427cded1bba613fc1, 5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6, 5.8, 5.9 |
| Linux/Linuxgeneric | 5.9 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=07dd0a7aae7f72af7cec18909581c2bb570edddc <a88b3293b556f4d8fba11db9a8061a6b0d3b69e6 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <a03cdcedb2cbcc42551dc3e4746929e93c5352d5 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <580f92f27cb8724bcc4be98ee89890eab524a2ae || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <d0c8c4fbd22d260fe28530260656c5fb3c20ce84 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <8a2126c5afe89f8ceeb60a3afb9f075b736194cd || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <02e1b5c4d3b4c658b72c145427cded1bba613fc1 || >=07dd0a7aae7f72af7cec18909581c2bb570edddc <5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6 || 95a936364f2685e9e040c6b179b553604d96de22 || fba2cf348d9eb50b2049a73cc09313dab6d293f1 || >=5.7.15 <5.8 || >=5.8.2 <5.9 | a88b3293b556f4d8fba11db9a8061a6b0d3b69e6, a03cdcedb2cbcc42551dc3e4746929e93c5352d5, 580f92f27cb8724bcc4be98ee89890eab524a2ae, d0c8c4fbd22d260fe28530260656c5fb3c20ce84, 8a2126c5afe89f8ceeb60a3afb9f075b736194cd, 02e1b5c4d3b4c658b72c145427cded1bba613fc1, 5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6, 5.8, 5.9 |
| Linux/Linuxgeneric | 5.9 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.