Kernel crash via unchecked clock-data allocation
Published May 21, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux MediaTek MT2701 clock driver before branch-specific fixes allows local users to crash the kernel. The MT2701 initialization path continues after mtk_alloc_clk_data returns NULL and passes the missing clock-data object to subsequent registration logic. Reachability requires the MT2701 driver and an allocation failure during clock initialization; the documented consequence is a system-interrupting kernel crash.
Summary
What happened
NULL pointer dereference in the Linux MediaTek MT2701 clock driver before branch-specific fixes allows local users to crash the kernel. The MT2701 initialization path continues after mtk_alloc_clk_data returns NULL and passes the missing clock-data object to subsequent registration logic. Reachability requires the MT2701 driver and an allocation failure during clock initialization; the documented consequence is a system-interrupting kernel crash.
The record
- CVE
- CVE-2023-52875
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 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.10
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <001e5def774fa1a8f2b29567c0b0cd3e3a859a96
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <0d6e24b422a2166a9297a8286ff2e6ab9a5e8cd3
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <1953e62366da5460dc712e045f94fb0d8918999d
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <1bf9c204aef4cc55ce46a7ff2d4dc7e5f86551a7
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <2a18dd653284550900b02107c3c7b3ac5e0eb802
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <6fccee2af400edaed9cf349d506c5971d4762739
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <d1175cf4bd2b4c5f7c43f677ea1ce9ad2c18d055
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <d1461f0c9ca0827c03730fe9652ebbf6316a2a95
- Affected versionversion=e9862118272aa528e35e54ef9f1e35c217870fd7 <e61934720af4a58ffd43a63ffdd6f3a0bd7d7b47
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.
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