Kernel panic via zero-count SCPI allocation
Published Dec 24, 2024 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernels allows local users to crash the system when SCPI firmware reports zero DVFS OPPs. The arm_scpi DVFS path accepts an OPP count of zero, passes it to kcalloc, and later dereferences the resulting zero-size allocation in scpi_dvfs_recalc_rate. Reachability requires an ARM platform using SCPI firmware that can return zero OPPs during reboot; the bounded consequence is a kernel panic and system interruption.
Summary
What happened
NULL pointer dereference in affected Linux kernels allows local users to crash the system when SCPI firmware reports zero DVFS OPPs. The arm_scpi DVFS path accepts an OPP count of zero, passes it to kcalloc, and later dereferences the resulting zero-size allocation in scpi_dvfs_recalc_rate. Reachability requires an ARM platform using SCPI firmware that can return zero OPPs during reboot; the bounded consequence is a kernel panic and system interruption.
The record
- CVE
- CVE-2024-53157
- Published
- Dec 24, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1529
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 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=4.4
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <025067eeb945aa17c7dd483a63960125b7efb577
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <06258e57fee253f4046d3a6a86d7fde09f596eac
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <109aa654f85c5141e813b2cd1bd36d90be678407
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <12e2c520a0a4202575e4a45ea41f06a8e9aa3417
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <2a5b8de6fcb944f9af0c5fcb30bb0c039705e051
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <380c0e1d96f3b522f3170c18ee5e0f1a28fec5d6
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <8be4e51f3ecfb0915e3510b600c4cce0dc68a383
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <9beaff47bcea5eec7d4ead98f5043057161fd71a
- Affected versionversion=8cb7cf56c9fe5412de238465b27ef35b4d2801aa <dfc9c2aa7f04f7db7e7225a5e118a24bf1c3b325
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