CVE-2026-98920: Linux kernel · netfs: Fix missing alloc tagging of direct mempool allocations
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 02:28 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available that introduces a new helper function to properly tag direct mempool allocations in the netfs subsystem. Users should apply the updated Linux kernel versions that include this patch to resolve the issue.
Description
A vulnerability in the Linux kernel's netfs subsystem related to missing allocation tagging of direct mempool allocations has been fixed. The issue caused allocation tags to be unset during certain memory allocations, leading to warnings and missing allocation information in /proc/allocinfo. This was due to direct calls to allocation callbacks bypassing the alloc_hooks wrapper. The fix introduces a new helper to ensure proper tagging without changing allocation failure semantics.
References
- ubuntu.com/security/CVE-2026-98920 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98920 (opens in a new tab)
- git.kernel.org/stable/c/37a2042748bc880df03ff8315db86ed82991fbb8 (opens in a new tab)
- git.kernel.org/stable/c/5c03da745171485fd181f17b69213464f6d05f3d (opens in a new tab)
- git.kernel.org/stable/c/b78b728e21c32ec4c330b299f657fb1eb02dffc2 (opens in a new tab)