CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-24148 remediation guide

NVIDIA Jetson Xavier Series and Jetson Orin Series, jetson linux, jetson agx orin 32gb

NVIDIA Jetson for JetPack contains a vulnerability in the system initialization logic, where an unprivileged attacker could cause the initialization of a resource with an insecure default. A successful exploit of this vulnerability might lead to information disclosure of encrypted data, data tampering, and partial denial of service across devices sharing the same machine ID.

Open CVE record
ProductNVIDIA Jetson Xavier Series and Jetson Orin Series, jetson linux, jetson agx orin 32gb
Affected versions>= All versions prior to 35.6.4, >= All versions prior to 36.5, < 35.6.4, >= 36.0 < 36.5
Fixed versions35.6.4, 36.5
Priority basisReview · CVSS 9.4 · EPSS 0.35%
01

Identify the affected asset

Confirm whether NVIDIA Jetson Xavier Series and Jetson Orin Series, jetson linux, jetson agx orin 32gb is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= All versions prior to 35.6.4, >= All versions prior to 36.5, < 35.6.4, >= 36.0 < 36.5. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 35.6.4, 36.5. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.