On this page (7 sections)

Ubuntu has published security notice USN-9018-1 on 2026-11-10, describing several security issues in the Linux kernel. The notice says an attacker could possibly use these flaws to compromise the system, and that the update corrects problems across a very wide range of kernel subsystems.

If you run websites on Ubuntu servers, virtual machines or container hosts, this is a notice to put in your next patch window. The excerpt of the notice available to us is short on detail, so this article separates what is confirmed from what you will need to verify on the notice page itself.

What the notice says

Ubuntu's notice states that several security issues were discovered in the Linux kernel and that an attacker could possibly use them to compromise the system. In the portion we have, it does not rate the severity or say whether any flaw is being exploited. Treat exploitation status as unknown rather than as safe.

Only one publisher, Ubuntu itself, covers this story so far. There is no independent analysis yet, so details such as individual CVEs, scores and affected releases should be taken from the full notice and not from third-party summaries.

Which parts of the kernel are involved

The notice lists flaws in many areas rather than a single bug. The subsystems named in the available text include:

  • Network file systems library and stream parser
  • CPU architecture code: ARM64, PowerPC, RISC-V, S390, User-Mode Linux and x86
  • Block layer, NVMe, SCSI, MMC, MTD and MemoryStick storage code
  • Network drivers, including Ethernet bonding and team drivers, Mellanox, STMicroelectronics and MediaTek
  • Bluetooth, USB4 and Thunderbolt, TTY, HID, GPU and TPM drivers
  • Android drivers, InfiniBand, GPIO, EDAC, IIO and other hardware support code

The list in the text we have is cut off partway through, so more subsystems are likely named in the full notice. Many of these are hardware drivers, so whether a given server is exposed may depend on which drivers it actually loads, but the notice text we have does not say.

Who is realistically exposed

Kernel flaws matter because the kernel runs with full privileges. Bugs in drivers and subsystems often need local access or a specific device or feature to be reachable, but the notice does not say which of these apply here. Until you read the details, assume the following groups should patch first:

  • Shared hosting and multi-tenant servers, where untrusted users run code on the same kernel
  • Servers that run web applications which could be compromised, since a kernel flaw can turn a web shell into full system control
  • Container hosts and CI runners, because containers share the host kernel
  • Systems using the drivers named above, such as Bluetooth, NVMe, bonded or Mellanox networking
Cloud and VPS customers should check whether their provider ships its own kernel flavor. The fixed package names and versions in the full notice show which kernel packages are covered.

How to check your exposure

First find out which Ubuntu release and kernel you are running. These read-only commands print the running kernel version and the Ubuntu release; compare them with the fixed versions listed in the notice for your release.

Show the running kernel and Ubuntu release (Debian/Ubuntu)Shell
uname -r
lsb_release -a

Next, list the kernel packages installed. This command only reads package information; look for the installed linux-image versions.

List installed kernel image packages (Debian/Ubuntu)Shell
dpkg -l 'linux-image*' | grep ^ii

Then refresh the package index and list upgradable Linux packages. This does not install anything; a newer linux package in the output means an update is available.

Show pending upgrades for kernel packages (Debian/Ubuntu)Shell
sudo apt update
apt list --upgradable 2>/dev/null | grep -i linux

If upgradable linux packages appear, compare their versions with the notice. If you use Ubuntu Pro Livepatch, you can also view its status on each host. The notice text we have does not say whether Livepatch covers these fixes, so confirm that in the full notice and in Ubuntu's Livepatch documentation instead of assuming.

Check Livepatch status if you use it (Ubuntu)Shell
canonical-livepatch status

What to do now

  1. Open the full notice at ubuntu.com/security/notices/USN-9018-1 and note the affected releases, CVE list and fixed package versions.
  2. Inventory your Ubuntu hosts and record each one's release and running kernel with uname -r.
  3. Prioritize internet-facing servers, shared hosts, container hosts and build runners.
  4. Apply the kernel update from the Ubuntu archive on a test or staging host first, then roll it out.
  5. Reboot into the new kernel, then confirm with uname -r that the fixed version is running.
  6. If you use Livepatch, confirm in the full notice and Ubuntu's documentation whether it covers these fixes; do not assume it does, and note any remaining exposure window until you reboot.
  7. Record the patch date and version per host so you can show the fix was applied.

The next command installs available updates, including the kernel package. It changes the system, so run it only after you have a backup and a maintenance window.

Caution. A kernel update takes effect only after a reboot, which interrupts running services. Schedule it, drain traffic from load-balanced nodes where you can, and make sure the server will boot cleanly before you reboot a remote machine.
Install pending updates (Debian/Ubuntu)Shell
sudo apt update
sudo apt upgrade

After the update, reboot to load the new kernel. Once the server is back, uname -r should show the fixed version listed in the notice.

Reboot to load the new kernel, then verify the version (Debian/Ubuntu)Shell
sudo reboot
# after the server is back:
uname -r
Tip. Many servers keep an old kernel installed alongside the new one. That is normal and useful as a fallback, but remember that only the kernel shown by uname -r is the one actually running.

Monitoring after patching

Kernel updates rarely show up from the outside, so rely on your own records. Watch for hosts that missed the reboot, and review authentication and system logs for anything unusual around the time before you patched. If a host looks compromised, follow a structured response such as website hacked: what to do.

Outside-in checks can help catch the consequences of a server compromise, such as injected scripts or changed content. A website malware scan and change monitoring can flag symptoms, but they cannot confirm that a kernel is patched. See what outside-in malware detection can and cannot see.

What we do not know yet

  • Which CVEs are covered and how severe each one is
  • Whether any of the flaws is exploited in the wild
  • Which flaws are remotely reachable and which need local access
  • Whether Livepatch covers these fixes
  • The exact fixed package versions per Ubuntu release, which are in the full notice

We will not guess at these. If you manage many hosts, read the full notice and its linked CVE pages before deciding how fast to move. For broader habits that keep servers patched and monitored, see small business website security.

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. USN-9018-1: Linux kernel vulnerabilitiesubuntu.com ·
  • Ubuntu
  • Linux kernel
  • USN
  • patching
  • servers