dbcve.org
Jetson LinuxOperating system · Nvidia

CVE-2022-28193

MEDIUM · 5.6 CVSS v3.1 Published 2022-04-27
Fix available
A fix is available. Upgrade to 32.7.2 or later.
See remediation →
58/100
Remediation priority · Elevated
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
NVIDIA Jetson Linux Driver Package contains a vulnerability in the Cboot module tegrabl_cbo.c, where insufficient validation of untrusted data may allow a local attacker with elevated privileges to cause a memory buffer overflow, which may lead to code execution, loss of integrity, limited denial of service, and some impact to confidentiality.

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

A buffer overflow vulnerability exists in the Cboot (secondary bootloader) module tegrabl_cbo.c of the NVIDIA Jetson Linux Driver Package. The vulnerability stems from insufficient validation of untrusted data, which can be exploited by a local attacker with elevated privileges to trigger the overflow, potentially achieving code execution, integrity compromise, limited denial of service, and some confidentiality impact.

MitigationApply the NVIDIA firmware/security patch for CVE-2022-28193 to the Jetson device. Additionally, implement proper input validation and bounds checking in the Cboot module code to prevent buffer overflows when processing untrusted data.

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.7.2

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L

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. Check Jetson Linux version
    Run 'head -n 1 /etc/nv_tegra_release' or check '/etc/nv_tegra_release' file to identify the installed Jetson Linux Driver Package version
    Affected if The version shown is less than 32.7.2 (for example, 32.7.1, 32.6.1, etc.)
  2. Identify Cboot as secondary bootloader
    Check boot configuration or boot logs to confirm Cboot (secondary bootloader) is in use on the Jetson device
    Affected if Cboot is enabled and used as the secondary bootloader in the boot chain
  3. Verify tegrabl_cbo module presence
    Inspect the bootloader partition or firmware files for the tegrabl_cbo.c compiled module or associated binary
    Affected if The tegrabl_cbo module exists in the bootloader and the system is running an unpatched version
  4. Confirm patch status
    Check NVIDIA security bulletin or device firmware patch level for CVE-2022-28193 reference
    Affected if No specific security patch for CVE-2022-28193 has been applied to the device firmware

The device is affected if it runs Jetson Linux version prior to 32.7.2 with an unpatched Cboot bootloader containing the vulnerable tegrabl_cbo.c module.

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.

dbcve · scoped
Upgrade available Upgrade to 32.7.2 or later
Fixed in 32.7.2
Interim mitigation

Apply the NVIDIA firmware/security patch for CVE-2022-28193 to the Jetson device. Additionally, implement proper input validation and bounds checking in the Cboot module code to prevent buffer overflows when processing untrusted data.

Recommended fix High confidence

32.7.2

  1. Identify the current Jetson Linux version using 'head -n 1 /etc/nv_tegra_release' or 'cat /etc/nv_tegra_release'
  2. Download Jetson Linux version 32.7.2 or later from NVIDIA's official Jetson download center (developer.nvidia.com/embedded/jetson-linux)
  3. Follow NVIDIA's official flashing instructions to update the Jetson device, typically using the SDK Manager or manual flashing with the new JetPack version
  4. After flashing, verify the upgrade was successful by checking the version with 'head -n 1 /etc/nv_tegra_release' - it should show r32 (releases), where the second version number is 7.2 or higher
  5. Ensure the Cboot module is updated as part of the full system flash

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jetson Linux Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28193 — 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-2022-28193 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