Skip to content
Heist/ feed
Back to feed
UnratedFix available

mm/page_alloc: fix race condition in unaccepted memory handling

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix race condition in unaccepted memory handling The page allocator tracks the number of zones that have unaccepted memory using static_branch_enc/dec() and uses that static branch in hot paths to determine if it needs to deal with unaccepted memory. Borislav and Thomas pointed out that the tracking is racy: operations on static_branch are not serialized against adding/removing unaccepted pages to/from the zone. Sanity checks inside static_branch machinery detects it: WARNING: CPU: 0 PID: 10 at kernel/jump_label.c:276 __static_key_slow_dec_cpuslocked+0x8e/0xa0 The comment around the WARN() explains the problem: /* * Warn about the '-1' case though; since that means a * decrement is concurrent with a first (0->1) increment. IOW * people are trying to disable something that wasn't yet fully * enabled. This suggests an ordering problem on the user side. */ The effect of this static_branch optimization is only visible on microbenchmark. Instead of adding more complexity around it, remove it altogether.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.30, 6.14.8, 6.6.92
CVEs
CVE-2025-38008
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 08:07 UTC · Revision 1

Source evidence

mm/page_alloc: fix race condition in unaccepted memory handling

core-osv · Original source

Published 18 Jun 2025, 09:28 UTC

In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix race condition in unaccepted memory handling The page allocator tracks the number of zones that have unaccepted memory using static_branch_enc/dec() and uses that static branch in hot paths to determine if it needs to deal with unaccepted memory. Borislav and Thomas pointed out that the tracking is racy: operations on static_branch are not serialized against adding/removing unaccepted pages to/from the zone. Sanity checks inside static_branch machinery detects it: WARNING: CPU: 0 PID: 10 at kernel/jump_label.c:276 __static_key_slow_dec_cpuslocked+0x8e/0xa0 The comment around the WARN() explains the problem: /* * Warn about the '-1' case though; since that means a * decrement is concurrent with a first (0->1) increment. IOW * people are trying to disable something that wasn't yet fully * enabled. This suggests an ordering problem on the user side. */ The effect of this static_branch optimization is only visible on microbenchmark. Instead of adding more complexity around it, remove it altogether.

osv:CVE-2025-38008

Kernel

Fixed versions: 6.6.92, 6.12.30, 6.14.8

Complete source record
{
  "id": "054bb18106c3949aab0d56f1d480eb143aa84380e85fbbe08c1f9b28bdd1a234",
  "url": "https://osv.dev/vulnerability/CVE-2025-38008",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "mm/page_alloc: fix race condition in unaccepted memory handling",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: fix race condition in unaccepted memory handling The page allocator tracks the number of zones that have unaccepted memory using static_branch_enc/dec() and uses that static branch in hot paths to determine if it needs to deal with unaccepted memory. Borislav and Thomas pointed out that the tracking is racy: operations on static_branch are not serialized against adding/removing unaccepted pages to/from the zone. Sanity checks inside static_branch machinery detects it: WARNING: CPU: 0 PID: 10 at kernel/jump_label.c:276 __static_key_slow_dec_cpuslocked+0x8e/0xa0 The comment around the WARN() explains the problem: /* * Warn about the '-1' case though; since that means a * decrement is concurrent with a first (0->1) increment. IOW * people are trying to disable something that wasn't yet fully * enabled. This suggests an ordering problem on the user side. */ The effect of this static_branch optimization is only visible on microbenchmark. Instead of adding more complexity around it, remove it altogether.",
    "evidence": "osv:CVE-2025-38008",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.6.92",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.30",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.14.8",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-38008",
      "aliases": [
        "CVE-2025-38008"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6"
                },
                {
                  "fixed": "98fdd2f612e949c652693f6df00442c81037776d"
                },
                {
                  "fixed": "74953f93f47a45296cc2a3fd04e2a3202ff3fa53"
                },
                {
                  "fixed": "71dda1cb10702dc2859f00eb789b0502de2176a9"
                },
                {
                  "fixed": "fefc075182275057ce607effaa3daa9e6e3bdc73"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38008.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.5.0"
                },
                {
                  "fixed": "6.6.92"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.30"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.14.8"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38008.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:27.465941318Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/71dda1cb10702dc2859f00eb789b0502de2176a9",
        "https://git.kernel.org/stable/c/74953f93f47a45296cc2a3fd04e2a3202ff3fa53",
        "https://git.kernel.org/stable/c/98fdd2f612e949c652693f6df00442c81037776d",
        "https://git.kernel.org/stable/c/fefc075182275057ce607effaa3daa9e6e3bdc73",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38008.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-38008",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38008.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-38008",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 493634,
  "published_at": "2025-06-18T09:28:19.358+00:00"
}