CVE-2026-98272: Linux kernel · net: mvpp2: prevent buffer overflow in page_pool allocation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f0e7d62c1eb984dd204095118973c59604144cd8 : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f0e7d62c1eb984dd204095118973c59604144cd8, e7f30dcfa6c64033bf9137362517bd248e5be384, dfd46b5584a5881b131008767950e1ab82713c8c +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
This vulnerability has been fixed in the Linux kernel. Users should apply the available patches identified by the fixed commit hashes to resolve the issue. No additional mitigation is required once the fix is applied.
Description
A buffer overflow vulnerability in the Linux kernel's mvpp2 network driver was resolved. The issue occurs due to an out-of-bounds access in the page_pool array when switching to per-CPU buffering mode without proper bounds checking. This can happen if the number of pools exceeds the maximum allowed, leading to memory corruption.
References
- git.kernel.org/stable/c/5cefdb7acfc646fbded59ae77dfe0aac4c9e4a3c (opens in a new tab)
- git.kernel.org/stable/c/4ac1d5adc4f4dbafbfd270b55cc6d8bf9849d545 (opens in a new tab)
- git.kernel.org/stable/c/dfd46b5584a5881b131008767950e1ab82713c8c (opens in a new tab)
- git.kernel.org/stable/c/6569fd85b0ef9a8a6f20b7eb868420b8c7c0c2a0 (opens in a new tab)
- git.kernel.org/stable/c/e7f30dcfa6c64033bf9137362517bd248e5be384 (opens in a new tab)
- git.kernel.org/stable/c/f0e7d62c1eb984dd204095118973c59604144cd8 (opens in a new tab)
- git.kernel.org/stable/c/1734c3fc0066e228ce1c11e434b7c2527f0a949a (opens in a new tab)
- git.kernel.org/stable/c/14cb1e7702e5cb3c58888f6aed498381a73927d2 (opens in a new tab)