Kernel memory corruption via size integer overflow
Published Jun 30, 2021 · Updated Aug 4, 2024
Integer overflow in NVIDIA Jetson TX1 Trusty TLK before 32.5.1 allows local users to write arbitrary kernel addresses. The tz_map_shared_mem function performs unchecked size arithmetic, causing its request and logging buffers to overflow into arbitrary kernel memory. Exploitation requires low local privileges, user interaction, high attack complexity, and a Jetson TX1 configuration that uses TLK.
Summary
What happened
Integer overflow in NVIDIA Jetson TX1 Trusty TLK before 32.5.1 allows local users to write arbitrary kernel addresses. The tz_map_shared_mem function performs unchecked size arithmetic, causing its request and logging buffers to overflow into arbitrary kernel memory. Exploitation requires low local privileges, user interaction, high attack complexity, and a Jetson TX1 configuration that uses TLK.
The record
- CVE
- CVE-2021-34382
- Published
- Jun 30, 2021
- Updated
- Aug 4, 2024
- Vendor
- DPDK Project
- Product
- NVIDIA Jetson TX1
- Classifications
- CWE-190, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=All Jetson Linux versions prior to r32.5.1
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