Kernel crash via unchecked clock-data allocation
Published May 21, 2024 · Updated May 11, 2026
NULL-pointer dereference in Linux 5.4 through 5.4.260 and other affected stable branches allows local users to crash the system. The clk_mt6779_apmixed_probe and clk_mt6779_top_probe paths pass a failed mtk_alloc_clk_data allocation into clock-registration helpers instead of returning an error. Exploitation requires local access, the MT6779 clock driver, and an allocation failure; the reported consequence is service interruption, not data access or privilege gain.
Summary
What happened
NULL-pointer dereference in Linux 5.4 through 5.4.260 and other affected stable branches allows local users to crash the system. The clk_mt6779_apmixed_probe and clk_mt6779_top_probe paths pass a failed mtk_alloc_clk_data allocation into clock-registration helpers instead of returning an error. Exploitation requires local access, the MT6779 clock driver, and an allocation failure; the reported consequence is service interruption, not data access or privilege gain.
The record
- CVE
- CVE-2023-52873
- 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=5.4
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <1f57f78fbacf630430bf954e5a84caafdfea30c0
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <3994387ba3564976731179c4d4a6d7850ddda71a
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <a90239551abc181687f8c0ba60b276f7d75c141e
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <ca6d565a2319d69d9766e6ecbb5af827fc4afb2b
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <df1c4a9efa3f5b6fb5e0ae63890230dbe2190b7e
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <f6a7c51cf07a399ec067d39f0a22f1817c5c7d2b
- Affected versionversion=710774e048614c761a39a98e8d0fa75f688c83b6 <fbe466f06d4ea18745da0d57540539b7b36936ae
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