Kernel crash via stale remoteproc resource-table size
Published Apr 18, 2025 · Updated May 11, 2026
NULL pointer dereference in Linux remoteproc allows local users to crash the kernel through a crafted firmware restart sequence. rproc_shutdown clears cached_table but leaves table_sz nonzero, so rproc_start passes a NULL source and stale length to memcpy when replacement firmware lacks a resource table. Triggering the fault requires an i.MX8MP or i.MX9 system, an initial U-Boot-started remote processor with a fixed-address table, and sufficient privilege to stop it, load firmware, and restart it.
Summary
What happened
NULL pointer dereference in Linux remoteproc allows local users to crash the kernel through a crafted firmware restart sequence. rproc_shutdown clears cached_table but leaves table_sz nonzero, so rproc_start passes a NULL source and stale length to memcpy when replacement firmware lacks a resource table. Triggering the fault requires an i.MX8MP or i.MX9 system, an initial U-Boot-started remote processor with a fixed-address table, and sufficient privilege to stop it, load firmware, and restart it.
The record
- CVE
- CVE-2025-38152
- Published
- Apr 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2025CVE 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.13
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <068f6648ff5b0c7adeb6c363fae7fb188aa178fa
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <2df19f5f6f72da6f6ebab7cdb3a3b9f7686bb476
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <6e66bca8cd51ebedd5d32426906a38e4a3c69c5f
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <7c6bb82a6f3da6ab2d3fbea03901482231708b98
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <8e0fd2a3b9852ac3cf540edb06ccc0153b38b5af
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <e6015ca453b82ec54aec9682dcc38773948fcc48
- Affected versionversion=9dc9507f1880fb6225e3e058cb5219b152cbf198 <efdde3d73ab25cef4ff2d06783b0aad8b093c0e4
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