On this page (7 sections)
Ubuntu published security notice USN-9022-1 on 2026-11-10. It says several security issues were discovered in the Linux kernel and that an attacker could possibly use them to compromise the system. A second notice, USN-9023-1, was published the same day with the same introductory text and subsystem list.
If you run Ubuntu servers, VPS instances or container hosts that carry websites, this is a kernel update to plan for. The research available for this article is limited, so the sections below separate what Ubuntu states from what you need to confirm on your own systems.
At a glance
What Ubuntu has said
The notice is short in the portion available to us. Ubuntu describes it as a set of security issues in the Linux kernel and lists the subsystems where flaws were corrected. In the excerpt we have, it does not name individual CVEs, give severity ratings, list the affected Ubuntu releases or state fixed package versions. The page text we received is also cut off partway through the subsystem list.
Only one independent publisher, Ubuntu itself, covers this story so far, and the second notice repeats the same introduction. Treat the two notices as one vendor's statement, not as separate confirmations. The research does not explain why Ubuntu published two notices, so open both pages directly and check which one applies to your release and kernel.
Which parts of the kernel are involved
The notice lists a very wide range of subsystems. Grouped loosely, they include:
- Core kernel areas: memory management, networking core, stream parser, block layer, drivers core
- CPU architecture code: ARM32, ARM64, M68K, MIPS, OpenRISC, PowerPC, RISC-V, S390, User-Mode Linux and x86
- Storage and block drivers: Serial ATA and Parallel ATA, null block, ublk, compressed RAM block device, Micron PCIe SSD
- Hardware and platform drivers: Bluetooth, TPM, ACPI, Intel NPU, AMD CDX bus, clock and CPU frequency frameworks, hardware crypto devices
- Other areas: USB Gadget drivers, network file systems library, Android drivers, hardware random number generator core
The list continues beyond what we can see. Most of these areas matter only if the code is built in and reachable on your machine, so real exposure varies a lot between a cloud VM and a physical server with specialized hardware. We cannot say from the research which flaws are remotely reachable, so do not assume either way.
Who is realistically exposed
Any Ubuntu host running a kernel that the notices list as affected should be treated as in scope until you confirm otherwise. Kernel flaws are typically most serious on multi-user systems, shared hosting, build servers and container hosts, because a local attacker or a compromised application may be able to escalate privileges. That is general background on this weakness class, not a claim about specific bugs in this notice.
How to check your systems
First, see which kernel is running. This command is read-only. Run it on each Ubuntu host and note the version string.
uname -rNext, list the installed kernel image packages to see whether a newer one is already present but not yet booted. The output shows package names and versions for installed kernels.
dpkg --list | grep linux-imageThen compare against the notices. Open USN-9022-1 and USN-9023-1, look for your Ubuntu release and the kernel package you actually run, and note the fixed package version given there. If your installed version is older than the fixed one, you need the update.
What to do now
- Open USN-9022-1 and USN-9023-1 and identify which one applies to your Ubuntu release and kernel package.
- Run uname -r on each host and record the current kernel version.
- Refresh package lists and install available updates with apt.
- Schedule a reboot, because a new kernel only takes effect after restart (unless you use a live patching service).
- After rebooting, run uname -r again and confirm the new version matches or exceeds the fixed version in the notice.
- Prioritize multi-user hosts, container hosts and anything internet-facing, then the rest of the fleet.
- Keep a record of patched hosts and dates so you can show what was done.
This command refreshes package lists and upgrades installed packages, including kernel packages made available through Ubuntu's security updates. Run it with sudo on the host.
sudo apt update && sudo apt upgradeAfter the reboot, confirm the running kernel again.
uname -rMonitoring afterwards
Kernel updates fix the host, but sites on it still need watching. Keep an eye on uptime after the reboot, on unexpected new processes or user accounts, and on certificate and DNS changes that could hint at a wider problem. Webforta Monitor covers uptime, certificate, DNS and header changes from the outside, which helps you notice a site that did not come back cleanly after a restart.
For broader habits, see our WordPress security checklist if your server hosts WordPress sites, and browse more security news and analysis. If you suspect a server was already compromised, follow website hacked: what to do.
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.
