dbcve.org
Jetson LinuxOperating system · Nvidia

CVE-2022-42270

HIGH · 7.8 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 32.7.2 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
NVIDIA distributions of Linux contain a vulnerability in nvdla_emu_task_submit, where unvalidated input may allow a local attacker to cause stack-based buffer overflow in kernel code, which may lead to escalation of privileges, compromised integrity and confidentiality, 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 confidence

This is a kernel-level vulnerability in NVIDIA's Linux driver for the NVDLA (Deep Learning Accelerator) emulation component. The nvdla_emu_task_submit function fails to validate input properly, allowing a local attacker to overflow a stack-based buffer, potentially achieving privilege escalation.

MitigationApply the NVIDIA security patch or update to a patched driver version; if the nvdla_emu component is not required, consider disabling it to reduce attack surface.

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
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. Identify Jetson Linux version
    Check the file /etc/nv_tegra-release or run 'cat /proc/version' to determine the installed Jetson Linux version. Compare the version number to the affected range (< 32.7.2).
    Affected if The installed Jetson Linux version is below 32.7.2
  2. Verify nvdla_emu module presence
    Run 'lsmod | grep nvdla' to list loaded NVDLA modules, or check /proc/modules for nvdla entries. Also examine /sys/module/ for nvdla* directories.
    Affected if The nvdla_emu module is loaded or the nvdla_emu module directory exists in /sys/module/
  3. Confirm NVDLA device nodes exist
    Check for NVDLA device files by running 'ls -la /dev/nvdla*' and examining /sys/class/nvdla/ for device entries.
    Affected if NVDLA device nodes exist in /dev/ or device entries appear in /sys/class/nvdla/
  4. Locate vulnerable function in kernel
    Inspect the kernel image or module file for the nvdla_emu_task_submit function. On Jetson, this may be in a kernel module in /lib/modules/$(uname -r)/kernel/drivers/ or within the main kernel image.
    Affected if The nvdla_emu_task_submit function is present in the loaded kernel or available modules

The system is affected if it runs Jetson Linux version below 32.7.2 AND has the nvdla_emu component enabled (module loaded or device nodes present).

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 security patch or update to a patched driver version; if the nvdla_emu component is not required, consider disabling it to reduce attack surface.

Recommended fix High confidence

Jetson Linux 32.7.2

  1. Backup all critical data on the Jetson device before proceeding with the upgrade
  2. Download the Jetson Linux version 32.7.2 or later from the official NVIDIA Jetson download center
  3. Follow the standard NVIDIA Jetson Linux flashing procedure, typically using the SDK Manager or the flash.sh script
  4. Ensure the device remains powered throughout the flashing process to prevent corruption
  5. After flashing, verify the system boots correctly and all peripherals function as expected
  6. Validate that the nvdla_emu_task_submit vulnerability is resolved by confirming the kernel version matches 32.7.2 or later

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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