On this page (7 sections)
Ubuntu published USN-9175-1 on 19 November 2026. It is a Linux kernel security update for the linux-oracle package, the kernel built for Oracle Cloud systems, and it lists Ubuntu 24.04 LTS as the affected release. Ubuntu says several security issues were fixed and that an attacker could possibly use them to compromise the system.
If you run Ubuntu 24.04 LTS servers with the Oracle kernel, this is worth scheduling soon. The update needs a reboot, and Ubuntu says an ABI change means third-party kernel modules must be recompiled and reinstalled.
What the notice says
The notice is short on individual details. It describes the update as correcting "several security issues" in the Linux kernel and lists the subsystems where flaws were found. The list is very long and covers drivers, architecture code, file systems, the BPF subsystem, memory management and networking. Among the networking entries are IPv4 networking, IPv6 networking, the SCTP protocol, the TCP network protocol, Netfilter and the networking core.
The text available to us does not list CVE identifiers, fixed package versions or any exploitation status, so we cannot say which specific bugs each fix addresses. Read the full notice on the Ubuntu page for the complete CVE list before you decide how urgent it is for your environment.
Why the ABI change matters
Ubuntu adds a specific warning: due to an unavoidable ABI change, the kernel updates have been given a new version number. That requires you to recompile and reinstall all third-party kernel modules you might have installed. Out-of-tree drivers, such as some storage, networking or monitoring modules, may not load on the new kernel until they are rebuilt.
Related kernel flaws published in the same period
The notice does not tell us whether the following issues are part of this update, so treat this section as background only. Three critical Linux kernel CVEs were published in subsystems that the notice lists (SCTP, TCP and IPv4). Check the Ubuntu notice and the Ubuntu CVE tracker to see whether your kernel covers them.
| CVE | CVSS | Weakness | Area |
|---|---|---|---|
| CVE-2026-64564 | 9.8 (critical) | CWE-416 use after free | SCTP: freeing the ASCONF's own transport during DEL-IP processing |
| CVE-2026-98432 | 9.8 (critical) | CWE-416 use after free | IPv4/TCP: inet_opt and ireq_opt freed without an RCU grace period |
| CVE-2026-99999 | 9.3 (critical) | CWE-20 improper input validation | IPv4: checksum_start not validated before completing a checksum |
The GitHub advisory for CVE-2026-64564 and the advisory for CVE-2026-98432 both give a CVSS 3.1 vector of network attack, low complexity, no privileges and no user interaction. Both list affected and patched versions as unknown. A use after free means code keeps using memory after it was released, which can lead to crashes or memory corruption. The records describe the flaws in kernel code, and the research we reviewed shows no confirmation of exploitation in the wild for any of them.
Who is exposed
- Ubuntu 24.04 LTS systems running the linux-oracle kernel.
- Servers that accept network traffic directly, since several of the listed subsystems handle network input.
- Hosts with third-party kernel modules, which need rebuilding after the update.
- Systems that have not rebooted since the update was installed, because a patched kernel only protects you once it is running.
This notice lists only the linux-oracle package for 24.04 LTS. If you run a different kernel package or a different Ubuntu release, check Ubuntu's security notices for the notice that applies to your system.
How to check your system
This read-only command prints the kernel release you are running now. Run it on the server and compare it with the package versions listed in the Ubuntu notice. If your system uses the Oracle kernel, the release string normally contains "oracle".
uname -rThis read-only command lists the installed linux-oracle packages and their versions, so you can see whether the update has been installed but not yet booted into.
dpkg -l | grep linux-oracleWhat to do now
- Read USN-9175-1 on the Ubuntu site and note the fixed package versions for 24.04 LTS.
- Take a snapshot or backup of the instance, and make sure you have console access.
- Check which third-party kernel modules you use and confirm they can be rebuilt for the new kernel.
- Refresh package lists and install the update with your normal package manager.
- Reboot into the new kernel in a maintenance window.
- Run uname -r again and confirm the new release is running.
- Check that networking, storage and any rebuilt modules work, then review service health.
This command refreshes the package index and applies pending updates on Ubuntu. Run it as root or with sudo. After it finishes, the new kernel is installed but not active until you reboot.
sudo apt update && sudo apt upgradeThis command reboots the server so it starts on the newly installed kernel. Afterward, run uname -r and look for the new release.
sudo rebootMonitoring after the update
Kernel flaws are a host-level problem, so an outside scan cannot confirm that your kernel is patched. Track it on the server: record the running kernel version across your fleet and alert on machines that fall behind. After the reboot, watch uptime and service availability for a day or two, since a failed module or driver often shows up as a service that did not come back. Uptime and certificate monitoring can help you notice a server that did not return after a reboot.
For a broader routine, see our small business website security guide and the uptime monitoring explainer.
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.
