CVE-2026-98920

netfs: Fix missing alloc tagging of direct mempool allocations

Products / packages Linux

Published 23/10/2026, 12:02:06 UTC

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 21:10:34 UTC

Severity

unknown

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

The Linux kernel has a vulnerability in netfs where direct mempool allocations are missing alloc tagging. This affects versions 6.12.114 to 6.12.117 and 7.1.8 to 7.2. The weakness may lead to untagged allocations.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

7 ranges

Linux version evidence

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

b343252d6f536203dd0660f676190dcbf6d2ecdc → before 6ba3d758cd40888908f96d68d69322dad65a871e

git versions

15ed8a9b7c63e9171f5139a6aaa1ffb61809861f → before 5c03da745171485fd181f17b69213464f6d05f3d

git versions

1d78d56c43ef3768183e8370e7367b162700e049 → before 37a2042748bc880df03ff8315db86ed82991fbb8

git versions

1d78d56c43ef3768183e8370e7367b162700e049 → before b78b728e21c32ec4c330b299f657fb1eb02dffc2

git versions

3f6d7f8a5416d852648d15a05e895f1195ee8a85

git versions

6.12.114 → before 6.12.117

semver versions

7.1.8 → before 7.2

semver versions

Other versions: unaffected

Linux · Linux

Linux

5 ranges

Linux version evidence

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

7.2

unaffected

0 → before 7.2

semver versions

6.12.117 → through 6.12.*

semver versions

7.2.9 → through 7.2.*

semver versions

7.3 → through *

original_commit_for_fix versions

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

4 sources

git.kernel.org/stable/c/6ba3d758cd40888908f96d68d69322dad65a871e

Source referenceLinux

git.kernel.org/stable/c/5c03da745171485fd181f17b69213464f6d05f3d

Source referenceLinux

git.kernel.org/stable/c/37a2042748bc880df03ff8315db86ed82991fbb8

Source referenceLinux

git.kernel.org/stable/c/b78b728e21c32ec4c330b299f657fb1eb02dffc2

Source referenceLinux

Inside the record

Evidence available

Package identity · not supplied

Version evidence

Remediation guidance · not supplied

Weakness classification · not supplied

Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-98920

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 6.12.114

After:

Through (inclusive):

Before: 6.12.117

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 7.2

After:

Through (inclusive):

Before: 7.2.9

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 7.2

After:

Through (inclusive):

Before: 7.3

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 7.1.8

After:

Through (inclusive):

Before:

Applicability preview

[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.12.114",
            "versionEndExcluding": "6.12.117"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "7.2",
            "versionEndExcluding": "7.2.9"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "7.2",
            "versionEndExcluding": "7.3"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "7.1.8"
          }
        ]
      }
    ]
  }
]

Contributing organizations · 1

Linux

Assigning organization

2026-11-10

Timeline

All times UTC

23 Oct 2026, 12:02
Advisory published
Publication date supplied by the source.
10 Nov 2026, 18:15
Source updated
Latest modification date supplied by the source.
10 Nov 2026, 18:25
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

Reading the signals

Severity · CVSS: Technical impact and attack conditions. No numeric assessment supplied.
Observed exploitation · KEV: An absent or unavailable KEV listing does not establish that exploitation has not occurred.
Predicted exploitation · EPSS: No EPSS estimate available in this record.

Record identifiers

Aliases: None recorded

Source evidence

Request a correction or dispute

Start with the assigning organization for this record. Include the CVE ID, the disputed information, and supporting evidence. A dispute does not itself reject a record.

Find the responsible CNA →Official dispute and escalation process ↗

CVE CVE-2026-98920

Enrichment coverage

NVDNot fully checked

GHSANot fully checked

EUVDNot fully checked

EPSSNot fully checked

Sponsored by MoxsoBuild security habits with adaptive training and phishing simulations.View as JSON

netfs: Fix missing alloc tagging of direct mempool allocations

Severity and exploitation

What this means

Attack conditions

Affected versions

Linux

affected

unaffected

unknown

Linux

affected

unaffected

unknown

What to do

Public exploit evidence

Original source description

References

Inside the record

Evidence available

Original records

Environment requirements

Timeline

Advisory published

Source updated

Last imported by cve.new

What changed