On this page (6 sections)
Canonical published USN-9169-2 on 20 November 2026. It is a Linux kernel update for Ubuntu 20.04 LTS that covers the linux-hwe-5.15, linux-lowlatency-hwe-5.15 and linux-nvidia-tegra-5.15 packages. Canonical says several security issues were found and that an attacker could possibly use them to compromise the system.
If you run Ubuntu 20.04 LTS servers or devices on one of those kernel flavors, this one is for you. The notice marks the fixed kernel packages with 'Fix available with Ubuntu Pro', and says the update needs a reboot to take effect.
What the notice says
Canonical describes this as a multi-issue kernel update. The notice text we reviewed does not break out individual flaws, and the research we had contained no CVE records, CVSS scores or reports of exploitation. We therefore cannot say how severe any single issue is, or whether any is being attacked. Treat it as a broad kernel security release and patch on your normal fast track.
Only one source, Canonical's own notice, covers this so far, and the text available to us was truncated. No independent analysis was available when we wrote this article.
Which parts of the kernel are involved
The notice lists a long set of subsystems with corrected flaws. Grouped loosely, they include:
- Networking: TCP, IPv4 and IPv6, Netfilter, Netlink, Open vSwitch, packet sockets, SCTP, TIPC, TLS, Bluetooth, wireless and MAC80211
- File systems: Ceph, F2FS, NFS server daemon, OCFS2, SMB network file system and file system notification
- Hardware drivers: GPU, USB (core, gadget, host, serial, Type-C), Thunderbolt and USB4, NVMe, SCSI, HID and several others
- Core kernel: BPF, perf events, memory management, futex primitives, audit, key management and the AppArmor security module
- Audio: ALSA and several codec and USB sound drivers
A kernel flaw is a bug in code that runs with full privilege. Depending on the subsystem, a bug there can let a local user gain higher privileges, crash the machine, or in some network-facing cases be reached remotely. The notice only says an attacker could possibly compromise the system, so we do not claim a specific attack path.
Who is realistically exposed
This notice lists only the Ubuntu 20.04 LTS packages named above. It does not discuss other kernels or other Ubuntu releases, so if you run those, check Ubuntu's other security notices for them. Hosts that expose many services, share user accounts, run containers, or allow untrusted code are the higher priority, since kernel bugs are most useful to someone who already has some foothold.
The package list in the notice marks each fixed kernel image with 'Fix available with Ubuntu Pro'. The text we reviewed does not explain further how that applies to systems without a Pro subscription, so check Canonical's notice and your subscription status to confirm how your hosts receive these fixes.
How to check your exposure
Run this on the server to print the running kernel release and the Ubuntu release. Compare the kernel against the fixed versions for your kernel flavor in the table below.
uname -r
lsb_release -aThis lists installed kernel image packages so you can see whether a fixed version is already installed but not yet booted.
dpkg -l 'linux-image*' | grep ^ii| Kernel flavor | Example package | Fixed version |
|---|---|---|
| Generic | linux-image-5.15.0-204-generic | 5.15.0-204.214~20.04.1 |
| Low latency | linux-image-5.15.0-199-lowlatency | 5.15.0-199.209~20.04.1 |
| NVIDIA Tegra | linux-image-5.15.0-1072-nvidia-tegra | 5.15.0-1072.74~20.04.1 |
The notice text we reviewed was truncated, so compare your installed packages against the full package list in the official notice rather than relying on this table alone.
What to do now
- Inventory your Ubuntu 20.04 LTS hosts and note which run linux-hwe-5.15, a lowlatency kernel or an NVIDIA Tegra kernel.
- Read the notice's package list and check your subscription status so you know how each host will receive the fixed packages.
- Run the package update commands below on a test host first.
- If you use third-party kernel modules, confirm they rebuilt against the new kernel version.
- Reboot into the new kernel in a planned window.
- Verify with uname -r that the running kernel matches a fixed version from the notice.
This refreshes package lists and installs available updates, including the new kernel. Run it with sudo on the affected host, then reboot.
sudo apt update
sudo apt upgradesudo reboot
# after the host is back:
uname -rMonitoring afterwards
After patching, keep an eye on the basics: unexpected reboots, new local accounts, unusual outbound connections and changes to scheduled tasks. Outside-in checks cannot see your kernel version, but they can confirm your public services stay healthy after the reboot. Uptime monitoring catches a host that does not come back, and Webforta Monitor can watch uptime and certificates on the sites running on it.
For wider hygiene on the systems that host your sites, see the small business website security guide, and browse more advisories on the Webforta blog.
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.
