dbcve.org
Jetson LinuxOperating system · Nvidia

CVE-2022-28195

MEDIUM · 5.7 CVSS v3.1 Published 2022-04-27
Fix available
A fix is available. Upgrade to 32.7.2 or later.
See remediation →
59/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 ext4_read_file function, where insufficient validation of untrusted data may allow a highly privileged local attacker to cause a integer overflow, which may lead to code execution, escalation of privileges, limited denial of service, and some impact to confidentiality and integrity. The scope of impact can extend to other components.

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

NVIDIA Jetson Linux Driver Package contains an integer overflow vulnerability in the Cboot bootloader ext4_read_file function due to insufficient validation of untrusted data. A highly privileged local attacker could exploit this to achieve code execution, privilege escalation, limited denial of service, and partial confidentiality/integrity impact, with potential scope extension to other components.

MitigationApply NVIDIA's security patches for the Jetson Linux Driver Package to update the Cboot bootloader; restrict local privileged access and monitor for indicators of compromise until patching is feasible.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/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. Confirm Jetson device platform
    Check /proc/device-tree/model or run 'cat /sys/firmware/devicetree/base/model' to verify the hardware is an NVIDIA Jetson product
    Affected if The system is not an NVIDIA Jetson device (this CVE only affects Jetson platforms)
  2. Identify Jetson Linux version
    Run 'cat /etc/nv_tegra_release' or check 'jetpack' package version via 'dpkg -l | grep -i jetpack' to obtain the installed Jetson Linux version
    Affected if The version reported is less than 32.7.2 (e.g., 32.7.1, 32.6.1, or earlier)
  3. Verify Cboot bootloader is in use
    Check bootloader logs or configuration files in /boot/extlinux/ or run 'fw_printenv' to confirm Cboot is the active bootloader. Cboot is the default bootloader for Jetson devices.
    Affected if Cboot bootloader is not being used (alternative bootloaders may not have this specific vulnerability)
  4. Check for ext4 filesystem usage
    Run 'mount | grep ext4' or inspect /etc/fstab to see if any partitions use the ext4 filesystem. The vulnerability exists in the ext4_read_file function within Cboot.
    Affected if ext4 filesystem is mounted or used on the device (the vulnerable code path requires ext4 file operations)

A user is affected if they are running NVIDIA Jetson Linux version 32.7.1 or earlier with Cboot as the bootloader and ext4 filesystem in use on the device.

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 NVIDIA's security patches for the Jetson Linux Driver Package to update the Cboot bootloader; restrict local privileged access and monitor for indicators of compromise until patching is feasible.

Recommended fix High confidence

Jetson Linux Driver Package 32.7.2

  1. 1. Back up all critical data and configurations on the Jetson device before performing the upgrade
  2. 2. Download the NVIDIA Jetson Linux Driver Package version 32.7.2 from the official NVIDIA developer website
  3. 3. Verify the integrity of the downloaded package using checksums provided by NVIDIA
  4. 4. Put the Jetson device into recovery mode by holding the FORCE_RECOVERY pin and powering on
  5. 5. Connect the device to a host computer via USB
  6. 6. On the host computer, run the NVIDIA Flash script with the appropriate board configuration and the new 32.7.2 image
  7. 7. Allow the flashing process to complete without interruption
  8. 8. After flashing, verify the new version by checking the L4T version number on the device
Caveat Upgrading the full L4T/Jetson Linux image may require reconfiguration of custom applications, device trees, or kernel modules; ensure compatibility with the new driver package before deployment

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
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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