On this page (7 sections)
Ubuntu has published security notice USN-9045-1 for the Linux kernel. The notice says a security issue was discovered in the Linux kernel and that an attacker could possibly use it to compromise the system. The corrected flaws are in the IPv4 networking subsystem.
If you run Ubuntu servers, VMs or cloud instances, this notice is worth a few minutes of your time. The public information we have is very short, so this article separates what is confirmed from what is not, and focuses on how to check your systems and apply the update.
What has been published
The Ubuntu notice is brief. It states that a security issue was discovered in the Linux kernel, that an attacker could possibly use it to compromise the system, and that the update corrects flaws in the IPv4 networking subsystem. It is the only source available for this story so far, and no other publisher has independently covered it.
The material we have does not include CVE identifiers, CVSS scores, affected or fixed package versions, Ubuntu release numbers, kernel flavor names, or any statement about exploitation. We will not guess at those. Open the full notice on Ubuntu's site for the exact kernel packages, flavors and releases that apply to you.
Why kernel networking flaws matter
The kernel's IPv4 code handles every IPv4 packet the machine receives, so a bug there can sit on a path that remote traffic reaches. Depending on the specific flaw, the outcome can range from a crash (denial of service) to memory corruption or privilege problems. The notice's wording, that an attacker could possibly compromise the system, does not by itself tell you how easy exploitation is or whether it can be done remotely.
Because the notice text we reviewed does not name the individual flaws, treat the impact as unconfirmed. The safe assumption for a network-facing kernel component is to patch promptly rather than wait for more detail.
Who is realistically exposed
- Ubuntu servers, VMs and cloud instances running a Linux kernel package listed in the notice.
- Systems directly reachable over IPv4, such as web, API or application servers, where the networking stack processes untrusted traffic.
- Hosting providers and agencies that manage fleets of Ubuntu machines and may not track which kernel flavor or release each one runs.
Ubuntu ships several kernel flavors, and the notice may cover only some of them, with others handled in separate notices. Do not assume you are safe or affected based on the Ubuntu release alone. Check the running kernel on every Ubuntu host against the package list in the full notice.
How to check your systems
This read-only command prints the running kernel release. Run it on each Ubuntu host and note the version and flavor in the name, then compare against the packages and versions listed in the full notice.
uname -rThis read-only command lists installed kernel image packages, so you can see which kernel packages are present and at which version. Compare them with the fixed versions in the notice.
dpkg -l | grep linux-imageWhat to do now
- Open the full notice at ubuntu.com/security/notices/USN-9045-1 and note the affected releases, kernel packages and fixed versions.
- Run uname -r on each host to identify which kernel and flavor it is running.
- Refresh package lists and install updates with your normal process, starting with internet-facing hosts.
- Reboot into the new kernel in a planned maintenance window, since a kernel update does not take effect until the machine restarts.
- Run uname -r again after the reboot and confirm it matches the fixed version.
- Keep a note of any hosts you could not reboot yet and track them until they are patched.
This command refreshes the package index and installs available updates on Ubuntu. Run it as root or with sudo, and review what it will upgrade before confirming.
sudo apt update && sudo apt upgradeMonitoring afterwards
Kernel patching is easy to leave half done: the package is installed but the old kernel is still running. After your maintenance window, verify the running version on every host rather than trusting the package manager output alone.
From the outside, you can also watch for unexpected changes on public-facing systems. Webforta Monitor tracks uptime, certificate, DNS and header changes, which helps you notice an unplanned outage after a reboot. It does not detect or fix this kernel issue; patching the host is the fix. For general guidance on keeping servers and sites in good shape, see small business website security.
Watch the Ubuntu notice page for updates. If Ubuntu later adds CVE identifiers, severity or exploitation details, revisit your priority accordingly.
What we do not know yet
- Which specific CVEs are fixed in this update.
- Which kernel packages, flavors and Ubuntu releases are covered, beyond what the full notice lists.
- Whether the flaws can be triggered remotely or require local access.
- Whether any of them are being exploited.
- The CVSS severity, which is not given in the text we reviewed.
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.
