On this page (7 sections)
Ubuntu published USN-9165-1 on 19 November 2026. It fixes several security issues in the Linux kernel on Ubuntu 26.10. Ubuntu says an attacker could possibly use these flaws to compromise the system, and that a reboot is required after the update.
If you run Ubuntu 26.10 on web servers, hosting nodes, build machines or container hosts, this update belongs in your next maintenance window. Three of the CVEs listed in the notice are described below. The notice lists many more, and the research available here does not describe those.
What Ubuntu fixed
The notice is a roll-up of kernel fixes. Ubuntu says the corrected flaws are in these subsystems: Cryptographic API, File systems infrastructure, Key management, io_uring, PID namespace and Tracing infrastructure. The notice references a long list of CVE identifiers, from CVE-2026-99218 up to CVE-2026-99245 in the ranges it shows.
The GitHub Advisory Database entries for the three CVEs below were published on 2 November 2026 and updated on 3 November. They are marked unreviewed and list no package, affected versions or patched versions, so the Ubuntu notice is the practical source for which package version contains the fix.
Technical details of three of the CVEs
CVE-2026-99218: coredump use after free
According to the GitHub advisory, the kernel function that finishes a coredump wakes parked threads without holding a reference on the task and without being inside an RCU read section. If the process doing this is preempted at the wrong moment, the thread can exit and be freed, and the wake-up code then takes a lock in freed memory. The fix holds RCU across the loop.
The advisory lists a CVSS v3 base score of 7.0 (High) with vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. In plain terms: the attacker needs local access and low privileges, and the timing makes it hard to hit. Its EPSS value is listed as 0.122%.
CVE-2026-99219: ftrace uninitialized variables
Per the advisory, a tracing function leaves two variables uninitialized. When a symbol lookup fails, for example while a kernel module is being loaded or unloaded, a garbage value can be dereferenced, producing a general protection fault. The advisory says this can be triggered by reading the available_filter_functions file during a module load or unload. The fix initializes both variables. No severity score is published in the source.
CVE-2026-99220: NULL pointer dereference in key handling
The advisory describes a NULL pointer dereference in the asymmetric keys code. It says an unprivileged caller can trigger it through the keyring restriction call followed by add_key() when a PKCS#8 key is supplied, ending in a kernel panic. The fix rejects restriction keys that have no key IDs. No severity score is published in the source.
Who is realistically exposed
- Servers running Ubuntu 26.10. The notice lists no other Ubuntu release.
- Shared hosting, CI runners, container hosts and any system where untrusted or low-privilege users can run code. Local flaws matter most there.
- Web servers where a separate bug (for example a vulnerable plugin or app) could give an attacker a low-privilege shell. A kernel flaw can then be a second step. This is general risk reasoning, not something the sources report for these CVEs.
- Machines with third-party kernel modules, because of the ABI change described below.
How to check your system
This read-only command prints the running kernel version. On a fixed system it should show 7.3.0-11 in the release string after you reboot.
uname -rThis read-only command shows the installed and candidate version of the kernel metapackage. If the installed version is older than 7.3.0-11.12, the update has not been applied.
apt policy linux-image-genericWhat to do now
- Confirm which hosts run Ubuntu 26.10 and which kernel flavor they use (generic, generic-64k, virtual, ibm).
- Schedule a maintenance window, because the fix only takes effect after a reboot.
- Run the standard package update (commands below) and install the 7.3.0-11.12 kernel packages.
- Reboot, then confirm with uname -r that the new kernel is running.
- If you installed third-party kernel modules, make sure they were rebuilt for the new version (see the warning).
- Review who has local shell access on each server and remove accounts that are no longer needed.
This updates the package index and installs available upgrades, including the kernel metapackages. Run it as root or with sudo.
sudo apt update
sudo apt upgradeAfter the update completes, this command reboots the server so the new kernel is loaded. Run it during your maintenance window.
sudo rebootMonitoring after the update
Kernel crashes caused by flaws like these show up as oops messages, general protection faults or unexpected reboots. Watch kernel logs and uptime for unexplained restarts, and keep an eye on unusual local logins on shared hosts. Uptime monitoring helps you notice a host that panics and reboots; see uptime monitoring explained and Webforta Monitor.
This read-only command searches the kernel log for oops and general protection fault messages. Matches do not prove an attack, but they are worth investigating.
sudo journalctl -k | grep -iE 'oops|general protection fault'For broader context on keeping servers current, see the small business website security guide.
What we do not know
- Ubuntu does not say in the notice which CVE is fixed in which individual package beyond the version table.
- Only CVE-2026-99218 has a published severity score in the sources. The scores for the others, and the details of the remaining CVEs in the notice, are not available in the research.
- The sources do not report any exploitation in the wild.
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.
