net: mvpp2: prevent buffer overflow in page_pool allocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in 5cefdb7acfc646fbded59ae77dfe0aac4c9e4a3c; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in 4ac1d5adc4f4dbafbfd270b55cc6d8bf9849d545; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in dfd46b5584a5881b131008767950e1ab82713c8c; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in 6569fd85b0ef9a8a6f20b7eb868420b8c7c0c2a0; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in e7f30dcfa6c64033bf9137362517bd248e5be384; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in f0e7d62c1eb984dd204095118973c59604144cd8; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in 1734c3fc0066e228ce1c11e434b7c2527f0a949a; From 7d04b0b13b1175ce0c4bdc77f1278c1f120f874f · fixed in 14cb1e7702e5cb3c58888f6aed498381a73927d2
- Linux Linux
5.4
- KernelLinux
From 5.4.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8
References 8
git.kernel.org
- stable/c/5cefdb7acfc646fbded59ae77dfe0aac4c9e4a3c
- stable/c/4ac1d5adc4f4dbafbfd270b55cc6d8bf9849d545
- stable/c/dfd46b5584a5881b131008767950e1ab82713c8c
- stable/c/6569fd85b0ef9a8a6f20b7eb868420b8c7c0c2a0
- stable/c/e7f30dcfa6c64033bf9137362517bd248e5be384
- stable/c/f0e7d62c1eb984dd204095118973c59604144cd8
- stable/c/1734c3fc0066e228ce1c11e434b7c2527f0a949a
- stable/c/14cb1e7702e5cb3c58888f6aed498381a73927d2