Kernel crash via unchecked zynq_clk_setup allocation
Published May 1, 2024 · Updated May 11, 2026
Null pointer dereference in the Zynq clock driver in affected Linux kernel versions allows local users to crash the kernel. During zynq_clk_setup(), kmalloc() can return null under physical-memory exhaustion, after which snprintf() writes through the null pointer. Low-privileged local access and a Zynq platform using this clock setup path are required; the bounded consequence is a kernel crash and service interruption.
Summary
What happened
Null pointer dereference in the Zynq clock driver in affected Linux kernel versions allows local users to crash the kernel. During zynq_clk_setup(), kmalloc() can return null under physical-memory exhaustion, after which snprintf() writes through the null pointer. Low-privileged local access and a Zynq platform using this clock setup path are required; the bounded consequence is a kernel crash and service interruption.
The record
- CVE
- CVE-2024-27037
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 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=0ee52b157b8ed88550ddd6291e54bb4bfabde364 <01511ac7be8e45f80e637f6bf61af2d3d2dee9db
- Affected versionversion=0ee52b157b8ed88550ddd6291e54bb4bfabde364 <0801c893fd48cdba66a3c8f44c3fe43cc67d3b85
- Affected versionversion=0ee52b157b8ed88550ddd6291e54bb4bfabde364 <58a946ab43501f2eba058d24d96af0ad1122475b
- Affected versionversion=0ee52b157b8ed88550ddd6291e54bb4bfabde364 <7938e9ce39d6779d2f85d822cc930f73420e54a6
- Affected versionversion=0ee52b157b8ed88550ddd6291e54bb4bfabde364 <8c4889a9ea861d7be37463c10846eb75e1b49c9d
- Affected versionversion=0ee52b157b8ed88550ddd6291e54bb4bfabde364 <ca976c6a592f789700200069ef9052493c0b73d8
- Affected versionversion=3.11
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