Kernel crash via normal memcpy to Tegra IRAM
Published Sep 12, 2025 · Updated Sep 12, 2025
Improper I/O memory access in the ARM Tegra reset path in Linux allows local users to crash a KASAN-enabled kernel during reset setup. The tegra_cpu_reset_handler_enable function passes the I/O-mapped IRAM destination to normal memcpy, causing KASAN to apply ordinary-memory boundary checks instead of using memcpy_toio. Exploitation requires low-privileged local access to an ARM Tegra system built with KASAN, and the documented consequence is a kernel crash.
Summary
What happened
Improper I/O memory access in the ARM Tegra reset path in Linux allows local users to crash a KASAN-enabled kernel during reset setup. The tegra_cpu_reset_handler_enable function passes the I/O-mapped IRAM destination to normal memcpy, causing KASAN to apply ordinary-memory boundary checks instead of using memcpy_toio. Exploitation requires low-privileged local access to an ARM Tegra system built with KASAN, and the documented consequence is a kernel crash.
The record
- CVE
- CVE-2025-39794
- Published
- Sep 12, 2025
- Updated
- Sep 12, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 12, 2025CVE publishedPublication date reported by the CVE source.
- Sep 12, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2499b0ac908eefbb8a217aae609b7a5b5174f330
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <30ef45b89a5961cdecf907ecff1ef3374d1de510
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <387435f4833f97aabfd74434ee526e31e8a626ea
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <398e67e0f5ae04b29bcc9cbf342e339fe9d3f6f1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <46b3a7a3a36d5833f14914d1b95c69d28c6a76d6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <75a3bdfeed2f129a2c7d9fd7779382b78e35b014
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <96d6605bf0561d6e568b1dd9265a0f73b5b94f51
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9b0b3b5e5cae95e09bf0ae4a9bcb58d9b6d57f87
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b28c1a14accc79ead1e87bbdae53309da60be1e7
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.
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