HIGH Introduced in 5.4
mvpp2 PagePool Overflow
CVE-2026-98272
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
01Description
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.
02KernelScan AI Analysis
Risk summary
An out-of-bounds write in the Marvell PP2 ethernet driver can be triggered by changing the MTU on a network interface, corrupting kernel heap memory. This requires CAP_NET_ADMIN (obtainable in a user namespace) and only affects systems with Marvell MVPP22 or newer ethernet hardware. Successful exploitation could lead to kernel code execution, privilege escalation, or system crash.
Vulnerability analysis
The Marvell PP2 ethernet driver's MTU change handler can switch the device to per-CPU buffer pool mode without verifying that the required number of pools fits within the allocated array. When the number of receive queues is at its maximum, the per-CPU scheme doubles it, exceeding the array bounds and causing an out-of-bounds write during buffer pool initialization. The fix adds the same hardware-version and pool-count bounds check that already exists in the driver probe path, ensuring the per-CPU scheme is only activated when it is safe to do so. The vulnerable code path is reached by changing the network interface MTU, which requires CAP_NET_ADMIN — obtainable in a user namespace — and only affects systems with Marvell PP2 (MVPP22 or newer) ethernet hardware.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 5.10 | 5.4 | 5.10.271 | 5cefdb7acfc6 |
| 5.15 | 5.4 | 5.15.222 | 4ac1d5adc4f4 |
| 6.1 | 5.4 | 6.1.189 | dfd46b5584a5 |
| 6.12 | 5.4 | 6.12.112 | e7f30dcfa6c6 |
| 6.18 | 5.4 | 6.18.54 | f0e7d62c1eb9 |
| 6.6 | 5.4 | 6.6.158 | 6569fd85b0ef |
| 7.2 | 5.4 | 7.2.8 | 1734c3fc0066 |
| mainline | 5.4 | 7.3 | 14cb1e7702e5 |
| cip/5.10 | 5.4 | 5.10.271-cip78 | 5cefdb7acfc6 |
| cip/5.10-rt | 5.4 | 5.10.272-cip79-rt35 | 5cefdb7acfc6 |
| cip/6.1 | 5.4 | 6.1.189-cip61 | dfd46b5584a5 |
| cip/6.1-rt | 5.4 | 6.1.189-cip61-rt32 | dfd46b5584a5 |
| cip/6.12 | 5.4 | 6.12.112-cip33 | e7f30dcfa6c6 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.112-cip33 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |
| cip/5.10 | Fixed in 5.10.271-cip78 |
| cip/5.10-rt | Fixed in 5.10.272-cip79-rt35 |