CVE-2026-24153
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 · uneditedNVIDIA Jetson Linux has a vulnerability in initrd, where the nvluks trusted application is not disabled. A successful exploit of this vulnerability might lead to 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 confidenceNVIDIA Jetson Linux contains a vulnerability in the initial ramdisk (initrd) where the nvluks trusted application remains enabled when it should be disabled. This configuration issue in the initrd could allow unauthorized access to sensitive cryptographic material, leading to information disclosure.
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< 35.6.4>= 36.0, < 36.5= 38.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Jetson Linux versionCheck the Jetson Linux version by running 'cat /etc/nv_tegra_release' or using the JetPack version command. This file contains the L4T (Linux for Tegra) version information.Affected if The version falls within < 35.6.4, >= 36.0 and < 36.5, or = 38.2
-
Identify the initrd configuration sourceLocate the initrd or initramfs image used during boot. This is typically found in /boot/ directory with names like initrd.img, initrd, or uInitrd. Also check for any custom early-boot configuration files that control initrd contents.Affected if The initrd image exists and is in use for the system's boot process
-
Inspect initrd contents for nvluks presenceExtract and examine the initrd image contents. Use 'cpio' or 'gunzip' to unpack the initrd and search for nvluks-related files, binaries, or configuration. Look for files named nvluks, libnvluks, or nvluks.conf within the extracted initrd structure.Affected if The nvluks trusted application or its configuration files are present inside the initrd image
-
Check initrd configuration for nvluks enablementExamine any configuration files that control which trusted applications are included in initrd. Look for settings that explicitly enable or disable nvluks in the early boot environment. Check bootloader configuration or LUKS encryption setup files that specify initrd contents.Affected if nvluks is explicitly enabled or allowed to persist in initrd when it should be disabled
-
Verify the initrd build configurationReview the system build or deployment configuration that generates the initrd. Check if there's a configuration flag or file that controls whether nvluks trusted application is included in the initrd image.Affected if The build configuration permits nvluks to be bundled into initrd
A user is affected if their Jetson Linux version matches the vulnerable ranges AND the nvluks trusted application is present and enabled within their initrd configuration.
Generated from the published advisory. Verify against your own configuration.
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 · scoped35.6.436.5
Disable or remove the nvluks trusted application from the initrd configuration on affected Jetson Linux deployments. Verify that LUKS decryption keys and sensitive data are not exposed in the initrd environment.
Jetson Linux 35.6.4 (for 35.x line) or 36.5+ (for 36.x line); 38.x fix pending
- Identify current Jetson Linux version using 'cat /etc/nv_tegra_release' or 'dpkg -l | grep linux-image'
- Backup all critical data and configurations before upgrading
- For versions < 35.6.4: Upgrade to Jetson Linux 35.6.4 or later (35.x series)
- For versions >= 36.0 and < 36.5: Upgrade to Jetson Linux 36.5 or later (36.x series)
- For version 38.2: Wait for NVIDIA to release a fix for the 38.x series or check if 38.3+ addresses this vulnerability
- After upgrade, verify nvluks trusted application is properly disabled in initrd by reviewing /boot/extlinux/extlinux.conf and initrd contents
- Flash the new JetPack/Linux for Tegra (L4T) release following NVIDIA's official flashing documentation for your specific Jetson module
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24153 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24153 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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