CVE-2026-53215: Linux kernel · Use After Free
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in d0c8c4fbd22d260fe28530260656c5fb3c20ce84 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in d0c8c4fbd22d260fe28530260656c5fb3c20ce84, a88b3293b556f4d8fba11db9a8061a6b0d3b69e6, a03cdcedb2cbcc42551dc3e4746929e93c5352d5 +6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 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– |
Description
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.
References
- git.kernel.org/stable/c/a88b3293b556f4d8fba11db9a8061a6b0d3b69e6 (opens in a new tab)
- git.kernel.org/stable/c/a03cdcedb2cbcc42551dc3e4746929e93c5352d5 (opens in a new tab)
- git.kernel.org/stable/c/580f92f27cb8724bcc4be98ee89890eab524a2ae (opens in a new tab)
- git.kernel.org/stable/c/d0c8c4fbd22d260fe28530260656c5fb3c20ce84 (opens in a new tab)
- git.kernel.org/stable/c/8a2126c5afe89f8ceeb60a3afb9f075b736194cd (opens in a new tab)
- git.kernel.org/stable/c/02e1b5c4d3b4c658b72c145427cded1bba613fc1 (opens in a new tab)
- git.kernel.org/stable/c/5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6 (opens in a new tab)