dbcve.org
Jetson LinuxOperating system · Nvidia

CVE-2026-24154

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 35.6.4 / 36.5 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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 has vulnerability in initrd, where an unprivileged attacker with physical access coul inject incorrect command line arguments. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, data tampering, and information disclosure.

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 a vulnerability in the initrd (initial ramdisk) component where an unprivileged attacker with physical access can inject incorrect command line arguments during the boot process. This manipulation of boot parameters can compromise the system's security chain, potentially allowing arbitrary code execution, privilege escalation, denial of service, data tampering, or information disclosure.

MitigationImplement boot integrity mechanisms such as secure boot with signed initrd images, TPM-based measurement, and hardware-rooted trust to prevent unauthorized modification of the boot process and command line arguments.

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:< 35.6.4>= 36.0, < 36.5= 38.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/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. Determine Jetson Linux version
    Run 'cat /etc/nv_tegra_release' or check '/usr/src/linux-headers-*/include/generated/uapi/linux/version.h' for the kernel version. Also check 'dpkg -l | grep -i nvidia' for Jetson Linux package versions.
    Affected if The installed version is < 35.6.4, or >= 36.0 but < 36.5, or exactly 38.2
  2. Identify if initrd is in use
    Check boot configuration by examining '/boot/extlinux/extlinux.conf' or run 'ls -la /boot/initrd*' to see if an initrd image exists. Also check 'cat /proc/cmdline' to see if 'initrd=' parameter is present.
    Affected if An initrd image is present and loaded during boot (initrd= parameter visible in /proc/cmdline)
  3. Check secure boot status
    Run 'mokutil --sb-state' to check if secure boot is enabled. On Jetson devices, also check '/sys/firmware/efi/efivars/SecureBoot-*' or use 'tegrastats' to verify boot security status.
    Affected if Secure boot is disabled or not configured (the mitigation is not in place)
  4. Verify boot chain integrity mechanisms
    Examine '/boot' directory permissions with 'ls -la /boot' and check if boot files have not been tampered with. Verify the initrd image file integrity using 'sha256sum' against known-good values if available.
    Affected if Boot files have weak permissions or no integrity verification is in place

You are affected if your Jetson Linux version falls within the vulnerable ranges (< 35.6.4, 36.0-36.4, or 38.2) AND initrd is used during boot AND secure boot is not enabled as a mitigation.

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 35.6.4 / 36.5 or later
Fixed in 35.6.436.5
Interim mitigation

Implement boot integrity mechanisms such as secure boot with signed initrd images, TPM-based measurement, and hardware-rooted trust to prevent unauthorized modification of the boot process and command line arguments.

Recommended fix High confidence

Jetson Linux 35.6.4 for 35.x branches; Jetson Linux 36.5 for 36.x branches; latest 38.x release (e.g., 38.3 or later) for 38.x branches

  1. 1. Identify the Jetson Linux version currently installed by checking /etc/nv_tegra_release or using the command 'cat /etc/nv_tegra_release'
  2. 2. Determine the appropriate upgrade path based on current version: for 35.x branches upgrade to 35.6.4; for 36.x branches upgrade to 36.5; for 38.2 upgrade to the latest available 38.x release
  3. 3. Download the corresponding Jetson Linux release package from the official NVIDIA Jetson download center (https://developer.nvidia.com/embedded/jetson-linux)
  4. 4. Follow NVIDIA's official flashing instructions using JetPack and the SDK Manager to apply the new OS image
  5. 5. After upgrade, verify the initrd version and confirm the vulnerability is patched by checking the CVE is resolved in the release notes
  6. 6. Re-apply any custom configurations or data after confirming the system boots correctly
Caveat Upgrading Jetson Linux requires re-flashing the entire system which will erase all data; custom kernel configurations may need to be reapplied; ensure board-specific compatibility and backup all data before proceeding

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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