Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 71dda1cb10702dc2859f00eb789b0502de2176a9, 74953f93f47a45296cc2a3fd04e2a3202ff3fa53, 98fdd2f612e949c652693f6df00442c81037776d.

Low priority for now. Upgrade to Linux Linux 71dda1cb10702dc2859f00eb789b0502de2176a9, 74953f93f47a45296cc2a3fd04e2a3202ff3fa53, 98fdd2f612e949c652693f6df00442c81037776d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38008

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.5 and later · before 6.6.92
  • linux linux kernel6.7 and later · before 6.12.30
  • linux linux kernel6.13 and later · before 6.14.8
  • linux linux kernel6.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.5affected
    • dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6 and later · before 98fdd2f612e949c652693f6df00442c81037776daffected · git
    • dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6 and later · before 74953f93f47a45296cc2a3fd04e2a3202ff3fa53affected · git
    • dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6 and later · before 71dda1cb10702dc2859f00eb789b0502de2176a9affected · git
    • dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6 and later · before fefc075182275057ce607effaa3daa9e6e3bdc73affected · git
    • before 6.5not affected · semver
    • 6.6.92 and later · up to and including 6.6.*not affected · semver
    • 6.12.30 and later · up to and including 6.12.*not affected · semver
    • 6.14.8 and later · up to and including 6.14.*not affected · semver
    • 6.15 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.30-16.12.30-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.6.1.160000.2.46.12.0-160000.6.1.160000.2.4
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.6.16.12.0-160000.6.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-symsbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.6.1.160000.2.46.12.0-160000.6.1.160000.2.4
SUSE:Linux Micro 6.2kernel-rtbefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro 6.2kernel-sourcebefore 6.12.0-160000.6.16.12.0-160000.6.1
SUSE:Linux Micro Extras 6.2kernel-obs-buildbefore 6.12.0-160000.6.16.12.0-160000.6.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38005Jun 18, 2025 · dmaengine: ti: k3-udma: Add missing locking
    22Monitor
  • ← EarlierCVE-2025-38007Jun 18, 2025 · HID: uclogic: Add NULL check in uclogic_input_configured()
    22Monitor
  • Later →CVE-2025-38009Jun 18, 2025 · wifi: mt76: disable napi on driver removal
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux71dda1cb10702dc2859f00eb789b0502de2176a9Vendor (CNA)
Linux Linux74953f93f47a45296cc2a3fd04e2a3202ff3fa53Vendor (CNA)
Linux Linux98fdd2f612e949c652693f6df00442c81037776dVendor (CNA)
Linux Linuxfefc075182275057ce607effaa3daa9e6e3bdc73Vendor (CNA)
debian:linux6.12.30-1 · Debian:13Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-zfcpdump6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.6.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default6.12.0-160000.6.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.6.1.160000.2.4 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.6.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.6.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.6.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-zfcpdump6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records