Kernel crash via missing ACPI companion check
Published Jul 24, 2026 · Updated Jul 24, 2026
NULL pointer dereference in Linux Kernel ACPI platform drivers in affected releases allows local users to crash the kernel. The probe paths in 13 core ACPI drivers assume ACPI_COMPANION() or ACPI_HANDLE() is non-NULL and dereference a missing companion after an override forces an unrelated match. The path requires local low-privileged access and a forced driver/device mismatch; the bounded impact is a kernel crash, with no published data exposure or modification.
Summary
What happened
NULL pointer dereference in Linux Kernel ACPI platform drivers in affected releases allows local users to crash the kernel. The probe paths in 13 core ACPI drivers assume ACPI_COMPANION() or ACPI_HANDLE() is non-NULL and dereference a missing companion after an override forces an unrelated match. The path requires local low-privileged access and a forced driver/device mismatch; the bounded impact is a kernel crash, with no published data exposure or modification.
The record
- CVE
- CVE-2026-64227
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- 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=0 <6.12.97
- Affected versionversion=0 <6.18.40
- Affected versionversion=0 <6.6.145
- Affected versionversion=0 <7.0.11
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <34f4d0e4e5065237d15651df759a99e81b7f9f51
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <612ddab8fce04394bd7aebe8e0f2599642e30859
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a9451bf561232314755baf69a5916e0ac77f33fc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e4865a56d013e86e46ea6acea15bb6eae01898ff
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1e12d81f9cd250e722da01c7670b518d4181406
What conditions does exploitation require?
What is affected?
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.
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