Heap overflow via wrapped kernel length calculation
Published Jun 30, 2021 · Updated Aug 4, 2024
Integer overflow in NVIDIA Jetson TX1's TLK kernel before 32.5.1 allows local users to trigger a heap overflow via a wrapped length. The TLK kernel permits a length calculation to wrap, and the resulting value causes subsequent heap processing to overrun its allocation. Reachability requires local high privileges, user interaction, and a TX1 configuration using TLK; NVIDIA has not named the affected function or specified the post-corruption action.
Summary
What happened
Integer overflow in NVIDIA Jetson TX1's TLK kernel before 32.5.1 allows local users to trigger a heap overflow via a wrapped length. The TLK kernel permits a length calculation to wrap, and the resulting value causes subsequent heap processing to overrun its allocation. Reachability requires local high privileges, user interaction, and a TX1 configuration using TLK; NVIDIA has not named the affected function or specified the post-corruption action.
The record
- CVE
- CVE-2021-34385
- Published
- Jun 30, 2021
- Updated
- Aug 4, 2024
- Vendor
- DPDK Project
- Product
- NVIDIA Jetson TX1
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- admin
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