Kernel crash via empty remoteproc phandle dereference
Published Aug 17, 2024 · Updated May 11, 2026
A NULL-pointer dereference in affected Linux kernel releases allows local users to crash the kernel through a malformed i.MX remoteproc device tree. In imx_rproc_addr_init(), the phandle counter includes empty entries, while the parsing loop dereferences the NULL value returned by of_parse_phandle(). Reachability requires local low-privileged access and an i.MX remoteproc configuration containing an empty memory-region phandle; the reported consequence is a kernel crash.
Summary
What happened
A NULL-pointer dereference in affected Linux kernel releases allows local users to crash the kernel through a malformed i.MX remoteproc device tree. In imx_rproc_addr_init(), the phandle counter includes empty entries, while the parsing loop dereferences the NULL value returned by of_parse_phandle(). Reachability requires local low-privileged access and an i.MX remoteproc configuration containing an empty memory-region phandle; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2024-43860
- Published
- Aug 17, 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
- Aug 17, 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.14
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <2fa26ca8b786888673689ccc9da6094150939982
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <4e13b7c23988c0a13fdca92e94296a3bc2ff9f21
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <6884fd0283e0831be153fb8d82d9eda8a55acaaa
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <6b50462b473fdccdc0dfad73001147e40ff19a66
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <6c9ea3547fad252fe9ae5d3ed7e066e2085bf3a2
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <84beb7738459cac0ff9f8a7c4654b8ff82a702c0
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <9a17cf8b2ce483fa75258bc2cdcf628f24bcf5f8
- Affected versionversion=a0ff4aa6f010801b2a61c203c6e09d01b110fddf <c877a5f5268d4ab8224b9c9fbce3d746e4e72bc9
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.
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