On this page (6 sections)

On 6 November 2026 Ubuntu published USN-9002-1, a security notice for the Linux kernel built for NVIDIA Tegra systems on Ubuntu 24.04 LTS. It fixes a long list of kernel subsystem flaws, and it names one specific issue, CVE-2026-81010, in the io_uring subsystem.

If you administer Ubuntu 24.04 LTS devices that run the linux-nvidia-tegra kernel, such as embedded or edge boards, this update is for you. Servers on the standard Ubuntu kernel are not covered by this particular notice.

What the notice says

Ubuntu describes CVE-2026-81010 as an io_uring flaw where canceled task work was not handled properly during certain wait operations, so the operation ran in the wrong task context. According to the notice, a local attacker could possibly use this to cause a denial of service (system crash).

The same notice says several other kernel security issues were fixed, and that an attacker could possibly use these to compromise the system. The list of affected areas is long: CPU architectures, many device drivers, file systems, networking, BPF, KVM and security modules among them. That breadth is the main reason to treat this as a routine but worthwhile kernel update rather than a single-bug patch.

Technical background on CVE-2026-81010

The GitHub advisory quotes the upstream kernel description. The waitid callback in io_uring (io_waitid_cb) can run through a fallback path when work can no longer be queued to the task that submitted it. In that case the work runs from a kernel worker and is marked as canceled. The callback ignored that cancel flag and went on to do child lookup relative to the current task, which in that situation is not the submitter.

In plain terms, this is a context mix-up: code that depends on which process it is running as was executed as a different one. The upstream fix honors the cancellation first, completes the request with -ECANCELED and skips copying data back to the submitter. The advisory links three kernel stable commits for the change.

Severity and an open question about the CVE record

The GitHub advisory lists a CVSS v3 score of 7.8 (High) with a local attack vector, low complexity, low privileges required and no user interaction. It also lists an EPSS score of 0.182%, and no CWE. Ubuntu's own wording is narrower than the score suggests: it mentions a possible denial of service.

There is a discrepancy to be aware of. The CVE record text we reviewed reads "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority", yet the GitHub advisory and the Ubuntu notice still describe the issue and its fix. We could not determine from the sources why the record shows as rejected, so treat the identifier's status as unclear. The kernel change itself is described consistently, and applying the Ubuntu update is the sensible course either way.

Who is exposed

  • Systems running Ubuntu 24.04 LTS with the linux-nvidia-tegra kernel, per the notice.
  • Environments where untrusted or low-privileged local users, containers or workloads can run code, since the attack vector is local and needs low privileges.
  • Shared or multi-tenant edge devices, where a local crash affects other users.

A remote attacker with no local access cannot reach this flaw directly. It becomes relevant if another weakness, such as a vulnerable web application, gives an attacker a local foothold. Patching the kernel limits what such a foothold can do.

How to check your system

These read-only commands show which kernel you are running and whether the Tegra kernel package is installed. Run them on the Ubuntu 24.04 device.

Show the running kernel and installed linux-nvidia-tegra packages (Ubuntu 24.04)Shell
uname -r
dpkg -l | grep linux-nvidia-tegra

If the second command returns no rows, this notice does not apply to that machine. If it lists packages, compare their versions with the fixed version shown in the USN-9002-1 notice, which carries the update instructions.

What to do now

Caution. Installing a new kernel needs a reboot to take effect, which interrupts services on that device. Schedule a maintenance window, and for remote boards make sure you have console or out-of-band access first.

This refreshes the package index and upgrades only the Tegra kernel packages on Ubuntu. Run it as root or with sudo, and look for the new package versions in the output.

Update the linux-nvidia-tegra kernel packages (Ubuntu 24.04)Shell
sudo apt update
sudo apt install --only-upgrade linux-nvidia-tegra

After rebooting, this confirms the device is running the new kernel.

Confirm the running kernel after reboot (Ubuntu 24.04)Shell
sudo reboot
# after the device comes back:
uname -r
  1. List every Ubuntu 24.04 LTS device that uses the linux-nvidia-tegra kernel.
  2. Read USN-9002-1 and note the fixed package version.
  3. Back up configuration and data before the maintenance window.
  4. Install the update and reboot each device.
  5. Verify the running kernel with uname -r.
  6. Restrict local and container access on edge devices to people and workloads that need it.

Monitoring afterwards

Unexpected kernel crashes or reboots are the observable symptom Ubuntu describes, so watch your device logs and uptime for them, before and after patching. A reboot you did not schedule is worth investigating. Our guide on uptime monitoring explains how to alert on that for the services these devices host.

Kernel updates are a recurring theme on Ubuntu. For a related notice, see USN-9003-1 for the NVIDIA kernel. If the devices serve a public website, a free security scan of your site can complement host patching, though it cannot see inside the kernel.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-81010 - GitHub Advisory Databasegithub.com
  2. USN-9002-1: Linux kernel (NVIDIA Tegra) vulnerabilities | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • Linux kernel
  • io_uring
  • NVIDIA Tegra
  • USN