CVE Catalog

CVE-2026-98272

Low risk· EPSS 10%
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.20%

10th percentile - higher than 10% of all known CVEs

Summary

In the Linux kernel, the mvpp2 network driver has a vulnerability where mvpp2_change_mtu() may call mvpp2_bm_switch_buffers(priv, true) without checking whether the number of pools (nrxqs * 2) exceeds MVPP2_BM_MAX_POOLS (8). This can lead to an out-of-bounds access in the priv->page_pool array in mvpp2_bm_init(), as the array is sized to hold MVPP2_PORT_MAX_RXQ entries and the per-CPU scheme doubles the count.

Risk Assessment

This can lead to kernel memory corruption, potentially causing system crashes or privilege escalation if an attacker can control MTU size.

Recommendation

Apply the Linux kernel patch that adds a check for hardware version (MVPP22 or newer) and the pool count limit before switching to per-CPU mode.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: prevent buffer overflow in page_pool allocation The per‑processor buffering scheme is supported only if the number of pools (nrxqs * 2) does not exceed MVPP2_BM_MAX_POOLS (8). This is already checked in mvpp2_probe() during the initial activation of percpu_pools. However, mvpp2_change_mtu() may later call mvpp2_bm_switch_buffers(priv, true) without this check, which can lead to an out-of-bounds access in the priv->page_pool array in mvpp2_bm_init(). The array is sized to hold MVPP2_PORT_MAX_RXQ entries, and mvpp2_get_nrxqs() may return exactly that value. The per-CPU scheme then doubles it to nrxqs * 2, exceeding the array bounds. Check that the hardware version is MVPP22 or newer and that the number of pools (nrxqs * 2) does not exceed MVPP2_BM_MAX_POOLS before switching to per-CPU mode. Found by Linux Verification Center (linuxtesting.org) with SVACE.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS