Local kernel crash via unchecked clock-data allocation
Published May 21, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel's MT6797 clock driver allows local users to crash the kernel during clock initialization. The clk-mt6797 initialization path fails to test whether mtk_alloc_clk_data() returned NULL before using the result. Public records do not explain how a low-privileged local user forces the allocation failure; the reported consequence is limited to availability.
Summary
What happened
NULL pointer dereference in the Linux kernel's MT6797 clock driver allows local users to crash the kernel during clock initialization. The clk-mt6797 initialization path fails to test whether mtk_alloc_clk_data() returned NULL before using the result. Public records do not explain how a low-privileged local user forces the allocation failure; the reported consequence is limited to availability.
The record
- CVE
- CVE-2023-52865
- Published
- May 21, 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
- 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.12
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <122ac6496e4975ddd7ec1edba4f6fc1e15e39478
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <2705c5b97f504e831ae1935c05f0e44f80dfa6b3
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <357df1c2f6ace96defd557fad709ed1f9f70e16c
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <3aefc6fcfbada57fac27f470602d5565e5b76cb4
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <4c79cbfb8e9e2311be77182893fda5ea4068c836
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <606f6366a35a3329545e38129804d65ef26ed7d2
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <81b16286110728674dcf81137be0687c5055e7bf
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <be3f12f16038a558f08fa93cc32fa715746a5235
- Affected versionversion=96596aa06628e86ea0e1c08c34b0ccc7619e43ac <c26feedbc561f2a3cee1a4f717e61bdbdfb4fa92
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