dbcve.org
Jetson LinuxOperating system · Nvidia

CVE-2021-34384

HIGH · 7.8 CVSS v3.1 Published 2021-06-30
Fix available
A fix is available. Upgrade to 32.5.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Bootloader contains a vulnerability in NVIDIA MB2 where a potential heap overflow could cause memory corruption, which might lead to denial of service or code execution.

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 · moderate confidence

Heap overflow vulnerability in NVIDIA MB2 bootloader that can cause memory corruption, potentially leading to denial of service or arbitrary code execution.

MitigationApply firmware updates from NVIDIA or affected OEM vendors that address this bootloader vulnerability; if no update is available, consider compensating controls such as restricting physical access and ensuring secure boot configurations.

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
Jetson LinuxOperating system
Affected:< 32.5.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the device runs NVIDIA Jetson Linux
    Inspect system information via 'cat /proc/version' or check for Jetson-specific files in /etc/nv_tegra_release
    Affected if The system is not running NVIDIA Jetson Linux, the vulnerability does not apply
  2. Identify the installed Jetson Linux version
    Run 'cat /etc/nv_tegra_release' or use 'dpkg -l | grep -i nvidia-l4t' to list installed NVIDIA L4T packages and their version numbers
    Affected if The version number returned is below 32.5.1 (for example, 32.4.4, 32.5.0, etc.)
  3. Verify the MB2 bootloader is in use
    Check boot logs or examine /boot partition for MB2 bootloader files; the MB2 (MLB2) is the secondary bootloader on Jetson platforms
    Affected if The device uses the MB2 bootloader as its secondary bootloader, which is standard on affected Jetson devices

The system is affected if it runs NVIDIA Jetson Linux with a version lower than 32.5.1 and utilizes the MB2 bootloader.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 32.5.1 or later
Fixed in 32.5.1
Interim mitigation

Apply firmware updates from NVIDIA or affected OEM vendors that address this bootloader vulnerability; if no update is available, consider compensating controls such as restricting physical access and ensuring secure boot configurations.

Fix this in Jetson Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34384 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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