Kernel crash via missing ACPI CPU entry
Published Sep 27, 2024 · Updated May 11, 2026
NULL pointer dereference in the arm64 ACPI CPU-mapping path in Linux 3.7 and later causes a kernel crash when a CPU entry is missing. get_cpu_for_acpi_id() maps an ACPI identifier back to a CPU and dereferences cpu_madt_gicc[cpu] without rejecting a missing entry left when the MPIDR check fails. No trigger path has been established, and the affected code is confined to arm64 systems using ACPI CPU enumeration, so practical reachability remains unverified.
Summary
What happened
NULL pointer dereference in the arm64 ACPI CPU-mapping path in Linux 3.7 and later causes a kernel crash when a CPU entry is missing. get_cpu_for_acpi_id() maps an ACPI identifier back to a CPU and dereferences cpu_madt_gicc[cpu] without rejecting a missing entry left when the MPIDR check fails. No trigger path has been established, and the affected code is confined to arm64 systems using ACPI CPU enumeration, so practical reachability remains unverified.
The record
- CVE
- CVE-2024-46822
- Published
- Sep 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <2488444274c70038eb6b686cba5f1ce48ebb9cdd
- Affected versionversion=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <40cae0df42e5e7f7a1c0f32deed9c4027c1ba94e
- Affected versionversion=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <4c3b21204abb4fa3ab310fbbb5cf7f0e85f3a1bc
- Affected versionversion=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <62ca6d3a905b4c40cd942f3cc645a6718f8bc7e7
- Affected versionversion=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <945be49f4e832a9184c313fdf8917475438a795b
- Affected versionversion=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <bc7fbb37e3d2df59336eadbd6a56be632e3c7df7
- Affected versionversion=0be7320a635c2e434e8b67e0e9474a85ceb421c4 <f57769ff6fa7f97f1296965f20e8a2bb3ee9fd0f
- Affected versionversion=3.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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