Kernel hang via 64-bit prom_printf stack
Published Aug 15, 2026 · Updated Aug 15, 2026
Incorrect numeric conversion in Linux kernel MIPS DEC builds allows local users to hang the kernel via an o32 prom_printf() call. The o32 wrapper passes an XKPHYS 64-bit stack pointer to 32-bit firmware, whose 32-bit ALU operations produce an invalid stack address and divert control. Reachability requires a 64-bit DEC configuration where the initial console remains active after other kernel threads start; the result is a boot hang.
Summary
What happened
Incorrect numeric conversion in Linux kernel MIPS DEC builds allows local users to hang the kernel via an o32 prom_printf() call. The o32 wrapper passes an XKPHYS 64-bit stack pointer to 32-bit firmware, whose 32-bit ALU operations produce an invalid stack address and divert control. Reachability requires a 64-bit DEC configuration where the initial console remains active after other kernel threads start; the result is a boot hang.
The record
- CVE
- CVE-2026-72215
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-681, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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 <1ed18b5c3be9657fe288fa4dae0bef2470598683
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <27857db30c98583e12dd8d939ba2370bce08a5be
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3394757c5d3970ab36d2aafa6dd40952b43f0d16
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3ae86630b94f72bf4012c6322f81f622dc4fdf24
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ff79e8bdc75db51e30298a75939e2308e7658e0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9cd4a8ed12d2a6313592e43c14cca5eca6717bee
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d3fd2d358df0ca712183509cbbed6a16bde1d17e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d828bca84311e278093e60b2864a54f4bbb0c2ad
- 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