CVE-2026-98920netfs: Fix missing alloc tagging of direct mempool allocations
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing alloc tagging of direct mempool allocations Commit 1d78d56c43ef ("netfs: Fix folio_queue ENOMEM in writeback by adding a mempool") added a mempool for the folio_queues and made the request, subrequest and folio_queue allocations distinguish between writeback and everything else. Writeback is part of memory reclaim and must not fail due to ENOMEM, so it allocates under GFP_NOFS through mempool_alloc(), which may dip into the pool's reserve and, if that runs empty, wait for elements to be returned. The GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke the pool's ->alloc() callback directly instead. The direct call, however, skips the alloc_hooks() wrapper that the mempool_alloc() macro provides. The pool callbacks, mempool_alloc_slab() and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof() and rely on current->alloc_tag having been set by the caller. With CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to current->alloc_tag not set WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook alloc_tag was not set WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook at allocation and free time respectively, as reported when reading files on a CIFS mount. The allocations are also missing from /proc/allocinfo. Wrap the direct ->alloc() invocations in alloc_hooks() with a new mempool_alloc_noreserve() helper in include/linux/mempool.h, next to the other alloc_hooks()-wrapped macros such as mempool_alloc(). The GFP_KERNEL paths keep their failable allocation semantics, they just get tagged now.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
- 18 days later
· 18 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b343252d6f536203dd0660f676190dcbf6d2ecdc – < 6ba3d758cd40888908f96d68d69322dad65a871e
- affected 15ed8a9b7c63e9171f5139a6aaa1ffb61809861f – < 5c03da745171485fd181f17b69213464f6d05f3d
- affected 1d78d56c43ef3768183e8370e7367b162700e049 – < 37a2042748bc880df03ff8315db86ed82991fbb8
- affected 1d78d56c43ef3768183e8370e7367b162700e049 – < b78b728e21c32ec4c330b299f657fb1eb02dffc2
- affected 3f6d7f8a5416d852648d15a05e895f1195ee8a85
- affected 6.12.114 – < 6.12.117
- affected 7.1.8 – < 7.2
- affected 7.2
- unaffected < 7.2
- unaffected 6.12.117 – ≤ 6.12.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/6ba3d758cd40888908f96d68d69322dad65a871e (opens in a new tab)
- https://git.kernel.org/stable/c/5c03da745171485fd181f17b69213464f6d05f3d (opens in a new tab)
- https://git.kernel.org/stable/c/37a2042748bc880df03ff8315db86ed82991fbb8 (opens in a new tab)
- https://git.kernel.org/stable/c/b78b728e21c32ec4c330b299f657fb1eb02dffc2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108884 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98920)Record last updated .