CVE-2025-40199

Boot crash via oversized page_pool pointer mask

Published Nov 12, 2025 · Updated Aug 5, 2026

Incorrect pointer tagging in Linux kernel page_pool code allows local users to crash affected 32-bit systems during boot. The PP_MAGIC_MASK reserves too many DMA-index bits, causing page_pool_page_is_pp() to misclassify arbitrary kernel pointers as page_pool-tagged pages. Reachability is limited to architecture configurations whose kernel pointers violate the assumed PAGE_OFFSET boundary, and the observed consequence is a boot crash.

CVSS severity7.8
High
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect pointer tagging in Linux kernel page_pool code allows local users to crash affected 32-bit systems during boot. The PP_MAGIC_MASK reserves too many DMA-index bits, causing page_pool_page_is_pp() to misclassify arbitrary kernel pointers as page_pool-tagged pages. Reachability is limited to architecture configurations whose kernel pointers violate the assumed PAGE_OFFSET boundary, and the observed consequence is a boot crash.

The record

CVE
CVE-2025-40199
Published
Nov 12, 2025
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 12, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4f51fb0d257ff4d406ec27966902de075e3b118e <15b8a5b4cdc16e9a8bb2a548e12a0fd92997605a
  2. Affected versionversion=6.12.34 <6.12.54
  3. Affected versionversion=6.15.3 <6.16
  4. Affected versionversion=6.16
  5. Affected versionversion=c30ae60f41f9edd6e1b5cad41cf28ce04dae39e4
  6. Affected versionversion=ee62ce7a1d909ccba0399680a03c2dee83bcae95 <95920c2ed02bde551ab654e9749c2ca7bc3100e0
  7. Affected versionversion=ee62ce7a1d909ccba0399680a03c2dee83bcae95 <f62934cea32c8f7b11b747975d69bf5afe4264cf

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=4f51fb0d257ff4d406ec27966902de075e3b118e <15b8a5b4cdc16e9a8bb2a548e12a0fd92997605a; version=6.12.34 <6.12.54; version=6.15.3 <6.16; version=6.16; version=c30ae60f41f9edd6e1b5cad41cf28ce04dae39e4; version=ee62ce7a1d909ccba0399680a03c2dee83bcae95 <95920c2ed02bde551ab654e9749c2ca7bc3100e0; version=ee62ce7a1d909ccba0399680a03c2dee83bcae95 <f62934cea32c8f7b11b747975d69bf5afe4264cf

Published CVSS scores

7.8kernel.orgCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo