CVE-2026-98571: Linux kernel · net: stmmac: clear stale buf->page after recycling on skb build failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 298673397ea3f6f5811b84f0d9f71eac71dda2e3 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium 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 298673397ea3f6f5811b84f0d9f71eac71dda2e3, 501baaeca7d128fa0a2f6953cf5873c5b0d7cf89, 0a7822e34a0bfde31b194ac3da3253e5032b44cc
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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 Linux kernel to 298673397ea3f6f5811b84f0d9f71eac71dda2e3, 501baaeca7d128fa0a2f6953cf5873c5b0d7cf89 or 0a7822e34a0bfde31b194ac3da3253e5032b44cc.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel source code as identified by the provided commit hashes. Users and administrators should update to a Linux kernel version that includes these fixes to resolve the issue.
Description
A vulnerability in the Linux kernel's stmmac network driver was fixed by clearing a stale buffer page pointer after a failed skb build. The issue involved a stale pointer to a recycled page, which could cause inconsistent buffer lifecycle handling in the RX descriptor processing.