Kernel crash via invalid SLUB metadata access
Published Oct 1, 2025 · Updated Aug 5, 2026
Invalid-pointer dereference in the Linux kernel allows local users to crash the kernel through corrupted SLUB freelist data. When alloc_consistency_checks detects an invalid object pointer, object_err accesses freelist, redzone, and other metadata without first rejecting NULL or otherwise invalid pointers. Reaching the flaw requires local low-privileged access and freelist corruption; the documented consequence is a kernel crash during diagnostic handling.
Summary
What happened
Invalid-pointer dereference in the Linux kernel allows local users to crash the kernel through corrupted SLUB freelist data. When alloc_consistency_checks detects an invalid object pointer, object_err accesses freelist, redzone, and other metadata without first rejecting NULL or otherwise invalid pointers. Reaching the flaw requires local low-privileged access and freelist corruption; the documented consequence is a kernel crash during diagnostic handling.
The record
- CVE
- CVE-2025-39902
- Published
- Oct 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=2.6.22
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <0ef7058b4dc6fcef622ac23b45225db57f17b83f
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <1f0797f17927b5cad0fb7eced422f9a7c30a3191
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <3baa1da473e6e50281324ff1d332d1a07a3bb02e
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <7e287256904ee796c9477e3ec92b07f236481ef3
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <872f2c34ff232af1e65ad2df86d61163c8ffad42
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <b4efccec8d06ceb10a7d34d7b1c449c569d53770
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <dda6ec365ab04067adae40ef17015db447e90736
- Affected versionversion=81819f0fc8285a2a5a921c019e3e3d7b6169d225 <f66012909e7bf383fcdc5850709ed5716073fdc4
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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