dbcve.org
Jetson LinuxOperating system · Nvidia

CVE-2022-28197

MEDIUM · 5.0 CVSS v3.1 Published 2022-04-27
Fix available
A fix is available. Upgrade to 32.7.2 or later.
See remediation →
52/100
Remediation priority · Moderate
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_mount function, where Insufficient validation of untrusted data may allow a highly privileged local attacker to cause an integer overflow. This difficult-to-exploit vulnerability 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 contains an integer overflow vulnerability in the Cboot bootloader ext4_mount function due to insufficient validation of untrusted data. A highly privileged local attacker can exploit this to achieve code execution, privilege escalation, limited DoS, and partial confidentiality/integrity impact. The vulnerability affects the boot process and scope may extend to other components.

MitigationApply NVIDIA's Jetson Linux security patches when available; prioritize patching given the code execution and privilege escalation potential despite the 'difficult-to-exploit' rating. Restrict local privileged access as a compensating control.

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

CVSS:3.1/AV:L/AC:H/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. Check Jetson Linux version
    Run 'cat /etc/nv_tegra_release' or check the kernel version with 'uname -a' to identify the installed Jetson Linux release
    Affected if The displayed version is earlier than 32.7.2 (for example, 32.7.1, 32.6.1, etc.)
  2. Verify Cboot bootloader is in use
    Inspect boot logs or UEFI/UEFI variables to confirm the Cboot bootloader is active on the Jetson device. This can be done by checking boot configuration files or boot output during startup
    Affected if Cboot is confirmed as the active bootloader (this is the default for affected Jetson devices)
  3. Check if ext4 filesystem is used in boot process
    Examine the boot configuration, device tree, or boot scripts for ext4_mount references or ext4 filesystem mount points during early boot stages
    Affected if ext4 filesystem is mounted or referenced in the boot process, making the ext4_mount function reachable

A Jetson device is affected if it runs Jetson Linux version earlier than 32.7.2, uses the Cboot bootloader, and employs ext4 filesystem in the boot path where the vulnerable ext4_mount function is invoked.

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 Jetson Linux security patches when available; prioritize patching given the code execution and privilege escalation potential despite the 'difficult-to-exploit' rating. Restrict local privileged access as a compensating control.

Recommended fix High confidence

32.7.2

  1. Identify the current Jetson Linux version running on the device using 'cat /etc/version' or 'cat /etc/nv_tegra_release'
  2. Download the Jetson Linux driver package version 32.7.2 or later from the official NVIDIA Jetson download center
  3. Follow NVIDIA's standard Jetson Linux upgrade procedure, which typically involves flashing the device with the new JetPack/L4T image
  4. Verify the upgrade was successful by checking the version after flashing
  5. Ensure any custom configurations or data are backed up before flashing as the upgrade process typically requires a 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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