CVE-2021-34372
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTrusty (the trusted OS produced by NVIDIA for Jetson devices) driver contains a vulnerability in the NVIDIA OTE protocol message parsing code where an integer overflow in a malloc() size calculation leads to a buffer overflow on the heap, which might result in information disclosure, escalation of privileges, and denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInteger overflow in NVIDIA OTE protocol message parsing code within Trusty (the trusted OS for Jetson devices) causes malloc() to allocate an undersized buffer, leading to heap-based buffer overflow. This can enable information disclosure, privilege escalation, or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 32.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the device is a Jetson platformInspect /proc/cpuinfo for NVIDIA Tegra identifiers, or check /sys/firmware/devicetree/base/model for Jetson model informationAffected if The device is not an NVIDIA Jetson product (the vulnerability only affects Jetson devices running Trusty)
-
Identify the Jetson Linux versionCheck the L4T version by reviewing /etc/nv_tegra_release or running 'dpkg -l | grep -i nvidia-l4t' on the deviceAffected if The installed Jetson Linux version is earlier than 32.5.1 (versions prior to 32.5.1 contain the vulnerable code)
-
Verify Trusty trusted OS is presentInspect /trusty or /vendor for Trusty-related directories and binaries, or check the bootloader configuration for Trusty initializationAffected if Trusty is not present (the vulnerability exists specifically within the Trusty OTE protocol message parsing code)
-
Check if OTE protocol handling is enabledReview running Trusty services or check configuration files under /trusty for OTE protocol message parsing componentsAffected if OTE protocol handling is actively used by the system (the flaw triggers during OTE message parsing when Trusty processes these messages)
The environment is affected if it is a Jetson device running Jetson Linux version 32.5 or earlier, with Trusty and OTE protocol processing enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data32.5.1
Apply NVIDIA firmware updates for affected Jetson devices once available; monitor NVIDIA security advisories for patch releases. Consider restricting network exposure of affected devices until firmware is updated.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34372 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data