CVE-2026-98920: Linux kernel · netfs: Fix missing alloc tagging of direct mempool allocations
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b78b728e21c32ec4c330b299f657fb1eb02dffc2 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 15:33 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b78b728e21c32ec4c330b299f657fb1eb02dffc2, 37a2042748bc880df03ff8315db86ed82991fbb8, 7.2 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 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– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 6.13, 7.2, and corresponding commits. Users should update to these fixed versions to resolve the missing allocation tagging issue. No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's netfs subsystem involved missing allocation tagging for direct mempool allocations. This caused warnings and missing allocation records when CONFIG_MEM_ALLOC_PROFILING_DEBUG was enabled, impacting memory allocation tracking during writeback operations on CIFS mounts. The issue was fixed by wrapping direct allocation calls with proper tagging hooks to ensure correct allocation profiling.