Kernel crash via truncated console buffer pointer
Published Jul 24, 2026 · Updated Jul 24, 2026
Improper address handling in the Linux kernel allows local users to crash 64-bit MIPS DEC systems during bootstrap. The initial console handler passes a stack buffer from XKPHYS to 32-bit firmware printf, which truncates the 64-bit pointer and dereferences the wrong address. Exposure requires a 64-bit configuration where the initial console remains active after other kernel threads start, such as when no final console driver is enabled.
Summary
What happened
Improper address handling in the Linux kernel allows local users to crash 64-bit MIPS DEC systems during bootstrap. The initial console handler passes a stack buffer from XKPHYS to 32-bit firmware printf, which truncates the 64-bit pointer and dereferences the wrong address. Exposure requires a 64-bit configuration where the initial console remains active after other kernel threads start, such as when no final console driver is enabled.
The record
- CVE
- CVE-2026-64252
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <07c245bc39f94481fd75ff1ed54f7ab97111f3dd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1c80327dedf05b8c8ca025b76c21235b19dd3a86
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <35212f2adc2cf15122b96b987519de235b855e46
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e61fc2e06e44b6d30248cc5bc47a58e75c2b43e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7fb13fd35110ebe95eb053faf79d018f51144d85
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8a15826e5d3bdcfbef2f8e9330c69ea9ee7282e7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9e22b6fc6532cd566dad6d89d8fb3885248e364a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ab465495b1ed5efb7d2f9b90d8b20b1e0473e26f
- Affected versionversion=2.6.12
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