CVE-2026-98920

netfs: Fix missing alloc tagging of direct mempool allocations

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.

Key facts

Published
23 Oct 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.209% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • b343252d6f536203dd0660f676190dcbf6d2ecdc up to but excluding 6ba3d758cd40888908f96d68d69322dad65a871e (affected)
  • 15ed8a9b7c63e9171f5139a6aaa1ffb61809861f up to but excluding 5c03da745171485fd181f17b69213464f6d05f3d (affected)
  • 1d78d56c43ef3768183e8370e7367b162700e049 up to but excluding 37a2042748bc880df03ff8315db86ed82991fbb8 (affected)
  • 1d78d56c43ef3768183e8370e7367b162700e049 up to but excluding b78b728e21c32ec4c330b299f657fb1eb02dffc2 (affected)
  • 3f6d7f8a5416d852648d15a05e895f1195ee8a85 (affected)
  • 6.12.114 up to but excluding 6.12.117 (affected)
  • 7.1.8 up to but excluding 7.2 (affected)
LinuxLinux
  • Default status: affected
  • 7.2 (affected)
  • 0 up to but excluding 7.2 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References