Boot-time crash via pre-initialization memory allocation
Published Jul 19, 2026 · Updated Jul 19, 2026
NULL pointer dereference in the Linux Kernel on ARM Integrator/CP allows local users to cause a crash during device-tree boot. During intcp_init_early, syscon_regmap_lookup_by_compatible reaches of_syscon_register, which allocates memory before memory management exists and can dereference a NULL allocator pointer. The condition requires an affected ARM Integrator/CP device-tree build; the crash was reproduced with GCC 10.x, 11.x, and 13.x, while some GCC 9.x builds return -ENOMEM and skip sched_clock_register.
Summary
What happened
NULL pointer dereference in the Linux Kernel on ARM Integrator/CP allows local users to cause a crash during device-tree boot. During intcp_init_early, syscon_regmap_lookup_by_compatible reaches of_syscon_register, which allocates memory before memory management exists and can dereference a NULL allocator pointer. The condition requires an affected ARM Integrator/CP device-tree build; the crash was reproduced with GCC 10.x, 11.x, and 13.x, while some GCC 9.x builds return -ENOMEM and skip sched_clock_register.
The record
- CVE
- CVE-2026-64165
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=4.9
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <22c738fb51f2d8b23ddff5cc0ccb2dd685bb39d3
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <33ad014abec90f37dade0e00560f28864187e21a
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <508b1193d63b5e073a3fe103eeb785fcba2d368c
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <58a112b0973f6cd6bcb8c503d1ff88be411ed0f0
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <6624854554c4c2bdfed3559e5c11bb03b16e7bd1
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <812103fb6da904bd03d62cf6a9826e537318ceed
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <90d77b30a666049ad24df463f52e5d529c44e8cd
- Affected versionversion=bdb249fce9ad44aab340be3b7a77060114f7193b <e984dc22e2c24dc34d6728e338c82b1ce7862753
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