Skip to main content

TECH VEDA

Corporate on-site training - Submit proposal Pick your modulesSharpen your kernel skills: deep dives, drivers, Yocto, CVEs, careers — updated daily. Read the blog →
Insights

Jetson Xavier Support After JetPack 5: Which Parts of the Stack Still Receive Fixes?

Jetson Xavier support after JetPack 5.1.8, the last JetPack 5 release: which layers still receive fixes, and how to check what your board runs.

Jetson Xavier Support After JetPack 5: Which Parts of the Stack Still Receive Fixes?

JetPack 5.1.8, released on 30 October 2026, is the last JetPack 5 release. No newer JetPack supports the Jetson AGX Xavier or Jetson Xavier NX. Jetson Xavier support now has a different answer for each layer of the product. The kernel can move to a CIP-based tree with maintenance projected to 2031. NVIDIA’s closed libraries have no path except NVIDIA. Orin products on JetPack 5 can move to JetPack 7.

Many edge AI products in robotics, video analytics and industrial inspection use a Jetson Xavier module with JetPack 5. NVIDIA has now made the last JetPack 5 release. This article explains what Jetson Xavier support means after that release, layer by layer. It names who still publishes fixes for each layer, and the parts that nobody covers. It also shows how to check which release a board runs.

What NVIDIA changed on 30 October 2026

On 30 October 2026, NVIDIA released JetPack 5.1.8 with Jetson Linux R35.7. NVIDIA’s announcement on its developer forum states that JetPack 5.1.8 is the final release of the JetPack 5 series. NVIDIA first gave notice on 15 January 2026. It then wrote that JetPack 5 would reach end of life in the third quarter of 2026.

JetPack 5.1.8 contains Linux kernel 5.10, a root file system based on Ubuntu 20.04, a UEFI-based bootloader and OP-TEE as the trusted execution environment. Its compute stack is CUDA 11.4.19, TensorRT 8.5.2, cuDNN 8.6.0 and DLA 3.12.1. NVIDIA describes it as a minor update to JetPack 5.1.7, with fixes for known issues and security vulnerabilities.

The announcement answers two practical questions. A team may continue to use JetPack 5, and existing applications continue to work as they do now. The team will no longer receive critical updates from NVIDIA. For maintenance after JetPack 5.1.8, NVIDIA refers customers to its partner RidgeRun.

Which Jetson products are affected

JetPack 5.1.8 supports the Jetson AGX Orin, Orin NX, Orin Nano, AGX Xavier and Xavier NX production modules. The end of JetPack 5 affects both module families, but in different ways.

The announcement gives a recommended release for each module. For the Jetson AGX Xavier and Jetson Xavier NX it is JetPack 5.1.8, marked as the end-of-life release. For the Orin modules it is JetPack 7.2.1. The JetPack 7.2.1 release page lists Thor and the Jetson Orin family as supported hardware. Xavier is not in that list. For Jetson Xavier support, there is no NVIDIA software release after JetPack 5.1.8.

The hardware dates are separate from the software dates. NVIDIA’s product lifecycle page lists the Jetson AGX Xavier 32GB, Xavier NX 16GB and 8GB, and AGX Xavier Industrial as available through July 2027. The AGX Xavier 64GB reached end of life in January 2025. The same page states that NVIDIA sends an official end-of-life notice at least eight months before the last shipment.

Key insight: NVIDIA lists Xavier modules as available until July 2027, but the last NVIDIA software release for them was made in October 2026. A Xavier product built in 2027 is built on software that NVIDIA no longer updates.

The layers of a JetPack 5 product, and who maintains each one

A JetPack 5 product has several layers, and each layer has its own maintainer. The table lists what was found for each layer.

LayerIn JetPack 5.1.8Maintenance found after JetPack 5.1.8
Linux kernel5.10, built by NVIDIA from its Jetson Linux sourceskernel.org projects December 2026 as the end of the upstream 5.10 longterm series. The Civil Infrastructure Platform (CIP) projects January 2031 for its 5.10 super-long-term kernel. NVIDIA makes no further JetPack 5 releases.
NVIDIA closed librariesCUDA 11.4.19, TensorRT 8.5.2, cuDNN 8.6.0, DLA 3.12.1, multimedia APINo source code is published. Only NVIDIA can change these libraries, and it makes no further JetPack 5 releases.
Bootloader and trusted execution environmentUEFI-based bootloader, OP-TEEPart of Jetson Linux R35.7. No further JetPack 5 releases.
Root file systemBased on Ubuntu 20.04Canonical lists May 2025 as the end of standard security maintenance for Ubuntu 20.04, and May 2030 as the end of Expanded Security Maintenance.
Yocto BSP layer (meta-tegra)Branches kirkstone and scarthgap-l4t-r35.x, at L4T R35.6.4 and JetPack 5.1.6Both branches are listed as “no longer actively maintained” on the meta-tegra branch page, last updated on 1 October 2026.

Two rows need a short explanation. The 5.10 kernel in Jetson Linux is NVIDIA’s own tree. An upstream 5.10 stable fix reaches a product only when someone merges it into that tree and builds a new kernel. The meta-tegra row matters to teams that build with Yocto. Its JetPack 5 branches stopped at JetPack 5.1.6, so they do not contain the fixes in 5.1.7 and 5.1.8.

The root file system row is a planning point, not a solution. This article did not confirm whether Canonical’s Expanded Security Maintenance can be used with the NVIDIA sample root file system. A team that depends on it should confirm that with Canonical in writing.

An earlier TECH VEDA article, SoC Kernel Support: How to Tell If Yours Has Already Lapsed, explains how these dates combine. It treats the upstream kernel date, the vendor branch date and the silicon availability date as separate measurements. Jetson Xavier support now depends on all three.

Extended Jetson Xavier support for the kernel: what it covers

RidgeRun, the partner that NVIDIA names, sells extended Jetson Xavier support for the kernel. It is based on the CIP 5.10 kernel. The CIP project lists its 5.10 super-long-term kernel with a projected end of life in January 2031 and a target of one release each month. RidgeRun’s release history lists three versions so far: 5.10.254-cip72, 5.10.256-cip73 and 5.10.258-cip74. RidgeRun stated on the NVIDIA forum that this offer is not open source.

RidgeRun documents what it has tested on the Jetson AGX Xavier developer kit. The list includes GPU operation, MIPI CSI camera capture, video encoding and decoding, networking, USB, storage, memory and display. Its “Known Gaps” page lists areas that it has not yet validated:

  • thermal zones, DevFreq, EMC scaling and the watchdog;
  • SD, NVMe, USB 3.0, Wi-Fi and Bluetooth;
  • suspend and resume, idle states, and audio;
  • the DLA and PVA accelerators, and the RCE and RTCPU firmware;
  • the secure boot chain, disk encryption, OTA updates, OP-TEE and bootloader capsule updates.

RidgeRun states that “not validated” does not mean “not working”. For a product team, the list is still a test plan. If the product uses any of these parts, the team must test them itself.

The scope page states further limits. Validation is done on the NVIDIA developer kits, and custom carrier boards need a separate evaluation. RidgeRun cannot modify or maintain NVIDIA’s proprietary software, firmware or drivers. It also states that future kernel updates may cause incompatibilities with that software. The customer must check that its own applications work with each kernel release.

Orin products that still run JetPack 5

An Orin product on JetPack 5 is in a different position. NVIDIA recommends JetPack 7.2.1 for the Orin modules and links to its flashing instructions for the upgrade. NVIDIA lists the Orin modules as available through January 2032.

The move is large. JetPack 7.2.1 uses Jetson Linux 39.2.1 with kernel 6.8 and Ubuntu 24.04. Its compute stack is CUDA 13.2.2, cuDNN 9.20.0 and TensorRT 10.16.2, with DeepStream 9.1. The kernel, Ubuntu, CUDA and TensorRT versions all change. Out-of-tree drivers and the device tree for a custom carrier board must be ported. Applications built against the NVIDIA libraries must be rebuilt and tested again.

The kernel.org longterm table lists 6.18, 6.12, 6.6, 6.1, 5.15 and 5.10. It does not list 6.8. Kernel fixes for a JetPack 7 product therefore come from NVIDIA releases, not from an upstream longterm series.

Yocto users have two maintained choices for Orin. The meta-tegra wrynose branch, a Yocto LTS branch, follows L4T R39.2.1 and JetPack 7.2.1. The scarthgap branch, also LTS, follows L4T R36.5.2 and JetPack 6.2.3, and the branch page states that it will stay on JetPack 6. This article did not confirm how long NVIDIA itself will publish JetPack 6 releases.

Three wrong conclusions about the end of JetPack 5

“JetPack 5 can still be downloaded, so it is still supported.” This conclusion is easy to reach, because NVIDIA states that JetPack 5 can still be used. The same announcement states that no critical updates will follow. A product that passes its tests today keeps every vulnerability found after 30 October 2026.

“A maintained kernel solves the problem.” This conclusion is also understandable. The kernel has a public stream of fixes and CVE records, so it looks like the whole risk. On a Jetson product, the GPU, camera, video and DLA functions depend on NVIDIA libraries that only NVIDIA can change. A new kernel does not change those libraries, and RidgeRun states that kernel updates may cause incompatibilities with them.

“The modules are available until July 2027, so the software is maintained until then.” The lifecycle page and the JetPack announcement are separate documents with separate dates. The hardware date says how long a team can buy the module. It says nothing about software releases.

Key insight: On a Xavier product, extended kernel maintenance covers the kernel only. The GPU, camera, video and DLA paths depend on NVIDIA libraries that will not change again. Test every new kernel against them before it is installed on field units.

How to check what your product runs

Any review of Jetson Xavier support starts with the release on the target board. NVIDIA’s Jetson Linux developer guide names the file /etc/nv_tegra_release as the place that records the installed software version. The apt source file shows which NVIDIA package repository the board uses for updates.

root@jetson-xavier-nx-devkit:~# cat /etc/nv_tegra_release
root@jetson-xavier-nx-devkit:~# cat /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
root@jetson-xavier-nx-devkit:~# grep VERSION_ID /etc/os-release

Jetson Linux R35 is the base of JetPack 5, and R35.7 is the base of JetPack 5.1.8. If the release file reports R35, the board runs JetPack 5. If the apt source file names an r35 release, updates come from the JetPack 5 repository. That repository will receive no further releases. An Ubuntu VERSION_ID of 20.04 confirms the JetPack 5 root file system.

Then record the following for each product line:

  • the module: Xavier or Orin;
  • the JetPack and Jetson Linux release on the field units;
  • whether the image is NVIDIA’s Ubuntu image or a Yocto build, and which meta-tegra branch it uses;
  • which NVIDIA libraries the application uses: CUDA, TensorRT, cuDNN, the multimedia API or the DLA;
  • the date until which the product has promised security updates to customers.

The last item is the most important one for the plan. Suppose the promised date is later than the end of maintenance for one of the layers. Then the team must cover the difference with its own work, a support contract or a hardware change.

Key insight: Compare the support date you have promised to customers with the end date of each layer’s maintenance. The earliest layer date, not the module availability date, sets how long the product can receive fixes without new work.

Before closing the review, confirm these points:

  1. /etc/nv_tegra_release and the apt source file were read on a field unit, not only on a development board.
  2. For an Orin product, a JetPack 7.2.1 build of the full application has been tested on the custom carrier board.
  3. For Jetson Xavier support through a CIP-based kernel, each item on RidgeRun’s “Known Gaps” list that the product uses has been tested.
  4. The owner of the Ubuntu 20.04 packages in the image is named in writing.
  5. The promised customer support date and the earliest layer end date are recorded in the product plan.

What this change does not fix

The end of JetPack 5 is a clear date, but it does not settle Jetson Xavier support on its own. Extended kernel maintenance does not change NVIDIA’s closed libraries, and it does not cover a custom carrier board without separate work. A move to JetPack 7 on Orin does not give the product an upstream longterm kernel, because 6.8 is not a longterm series. Nothing in these announcements changes the Ubuntu 20.04 root file system, whose standard security maintenance ended in May 2025. And no software path changes the date on which NVIDIA stops selling Xavier modules.

What was checked and what could not be verified

Every source in Further reading was read on 21 November 2026. The NVIDIA statements come from NVIDIA’s own forum announcements and release pages. The maintenance dates come from kernel.org, the CIP wiki and Canonical.

Some points were not verified. These are whether Canonical’s Expanded Security Maintenance applies to the NVIDIA root file system, and how long NVIDIA will publish JetPack 6 releases. The terms of RidgeRun’s offer, and whether a Xavier module end-of-life notice has been issued, were not checked either. No measurement was made on hardware, so no command output is shown.

Key takeaways

  • JetPack 5.1.8, released on 30 October 2026, is the last JetPack 5 release. No later JetPack supports Xavier.
  • Jetson Xavier support must be checked per layer: kernel, NVIDIA libraries, bootloader, root file system and Yocto layer.
  • Extended Jetson Xavier support based on the CIP 5.10 kernel runs to a projected January 2031, but it covers the kernel only.
  • NVIDIA lists Xavier modules as available through July 2027, after the last software release.
  • Orin products can move to JetPack 7.2.1, with kernel 6.8 and Ubuntu 24.04, but the move needs a full rebuild and retest.
Was this worth your time?

Frequently asked questions

Is JetPack 5.1.8 the last JetPack 5 release?
Yes. NVIDIA’s announcement of 30 October 2026 states that JetPack 5.1.8 marks the final release of the JetPack 5 series.

Does Jetson Xavier support continue in JetPack 6 or JetPack 7?
No. NVIDIA recommends JetPack 5.1.8 for Xavier, and the JetPack 7.2.1 hardware list does not include Xavier. The meta-tegra branch page lists its JetPack 6 branches for Orin modules only.

How long are Jetson Xavier modules available?
NVIDIA’s lifecycle page lists the AGX Xavier 32GB, Xavier NX 16GB and 8GB, and AGX Xavier Industrial as available through July 2027.

Does a CIP-based kernel give full Jetson Xavier support?
No. It maintains the kernel. NVIDIA’s closed libraries are not changed, and RidgeRun lists several subsystems, including the DLA, secure boot and OTA updates, as not yet validated.

How do I check which JetPack a board runs?
Read /etc/nv_tegra_release and the apt source file on the board. Jetson Linux R35 is the base of JetPack 5.

Further reading

RB
Raghu Bharadwaj

Founder, TECH VEDA — 20+ years teaching the Linux kernel, device drivers and embedded systems.

Follow on LinkedIn

Get new posts by email

Kernel, embedded Linux and AI-era engineering — a few sharp reads a month. No spam.

We email occasionally and never share your address.