{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-98920",
  "modified": "2026-11-06T05:30:01Z",
  "upstream": [
    "CVE-2026-98920"
  ],
  "published": "2026-10-23T12:06:24Z",
  "summary": "netfs: Fix missing alloc tagging of direct mempool allocations",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix missing alloc tagging of direct mempool allocations\n\nCommit 1d78d56c43ef (\"netfs: Fix folio_queue ENOMEM in writeback by\nadding a mempool\") added a mempool for the folio_queues and made the\nrequest, subrequest and folio_queue allocations distinguish between\nwriteback and everything else.  Writeback is part of memory reclaim\nand must not fail due to ENOMEM, so it allocates under GFP_NOFS\nthrough mempool_alloc(), which may dip into the pool's reserve and,\nif that runs empty, wait for elements to be returned.  The\nGFP_KERNEL paths, which can return -ENOMEM to their callers, invoke\nthe pool's ->alloc() callback directly instead.\n\nThe direct call, however, skips the alloc_hooks() wrapper that the\nmempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab()\nand mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof()\nand rely on current->alloc_tag having been set by the caller.  With\nCONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to\n\n    current->alloc_tag not set\n    WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook\n    alloc_tag was not set\n    WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook\n\nat allocation and free time respectively, as reported when reading\nfiles on a CIFS mount.  The allocations are also missing from\n/proc/allocinfo.\n\nWrap the direct ->alloc() invocations in alloc_hooks() with a new\nmempool_alloc_noreserve() helper in include/linux/mempool.h, next to\nthe other alloc_hooks()-wrapped macros such as mempool_alloc().  The\nGFP_KERNEL paths keep their failable allocation semantics, they just\nget tagged now.",
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.12.115-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.12.115+rpt-rpi-2712",
            "binary_version": "1:6.12.115-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.12.115+rpt-rpi-v6",
            "binary_version": "1:6.12.115-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.12.115+rpt-rpi-v7",
            "binary_version": "1:6.12.115-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.12.115+rpt-rpi-v7l",
            "binary_version": "1:6.12.115-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.12.115+rpt-rpi-v8",
            "binary_version": "1:6.12.115-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.12.115+rpt-rpi-v8-rt",
            "binary_version": "1:6.12.115-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.12.115-1+rpt1": {
            "linux_commit": "2569533d6c33c15231fbc21704c87fcebc67173c",
            "upstream_version": "6.12.115",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-98920"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5c03da745171485fd181f17b69213464f6d05f3d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/37a2042748bc880df03ff8315db86ed82991fbb8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b78b728e21c32ec4c330b299f657fb1eb02dffc2"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-10-23T12:06:24Z"
  }
}