Local availability loss via probe resource leaks
Published Oct 22, 2025 · Updated Oct 22, 2025
A memory leak in the i.MX8MP clock driver in the Linux kernel allows local users to degrade system availability through resource exhaustion. imx8mp_clocks_probe() used unmanaged mappings and allocations and failed to unregister clock hardware when provider registration returned an error, leaving resources allocated on failure or removal paths. Exposure requires an affected kernel using the i.MX8MP clock driver and reaching a device or driver removal, unload, or failed-registration path; the reported consequence is limited to reduced availability.
Summary
What happened
A memory leak in the i.MX8MP clock driver in the Linux kernel allows local users to degrade system availability through resource exhaustion. imx8mp_clocks_probe() used unmanaged mappings and allocations and failed to unregister clock hardware when provider registration returned an error, leaving resources allocated on failure or removal paths. Exposure requires an affected kernel using the i.MX8MP clock driver and reaching a device or driver removal, unload, or failed-registration path; the reported consequence is limited to reduced availability.
The record
- CVE
- CVE-2023-53704
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record 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.6
- Affected versionversion=9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 <5bcf140e9e6cf76f1f1bd1f489a14ca4d49f9a1a
- Affected versionversion=9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 <6317d0302655f7e854cd4f31e93b47d35cb058bb
- Affected versionversion=9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 <878b02d5f3b56cb090dbe2c70c89273be144087f
- Affected versionversion=9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 <92ce7629a11ae62292e1cfaa6132dab081fc80ee
- Affected versionversion=9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 <bcea444ab4c045864b55d67313833d606676602a
- Affected versionversion=9c140d9926761b0f5d329ff6c09a1540f3d5e1d3 <cb047c13bbf9018693ae31f03a5a26b212d02f13
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.
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