On this page (6 sections)

On 13 November 2026 Ubuntu published USN-9027-2, a security notice for the Linux kernel FIPS package (linux-fips) on Ubuntu 22.04 LTS. It says several flaws were fixed across the x86 architecture, hardware monitoring drivers, the OCFS2 file system, IPv4 networking, the Ethernet bridge, Netfilter and the XFRM subsystem.

If you run Ubuntu 22.04 LTS with the FIPS kernel (available through Ubuntu Pro), you should schedule this update and a reboot. Servers that use the standard kernel are not the target of this particular notice.

What the notice says

Ubuntu describes the issues in general terms: an attacker could possibly use them to compromise the system. The notice lists the affected kernel areas but does not break down which CVE belongs to which subsystem, and it does not give per-CVE severity. Ubuntu also notes that after a standard system update you must reboot to apply the changes.

The update changes the kernel ABI, so Ubuntu gave the packages a new version number. Third-party kernel modules you installed must be recompiled and reinstalled. Ubuntu says a standard upgrade does this automatically unless you manually removed the standard kernel metapackages.

The CVEs in more detail

Detail is available for three of the five identifiers, from the GitHub Advisory Database. Note that those GitHub entries are marked unreviewed and list affected and patched versions as unknown, so the Ubuntu package versions above are the reliable fix reference for this notice.

CVEs with published detail (scores as listed by GitHub)
CVEAreaCVSSWhat the description says
CVE-2026-74350OCFS2 file system9.8 (network vector)A corrupt inode with a zero-cluster symlink could make the kernel read past the end of the inode block buffer. The fix validates fast symlink size and NUL termination when the inode block is read.
CVE-2026-63940KVM SEV9.3 (local vector)Port I/O requests of length 0 are now ignored so code setting up the scratch area does not underflow the length. Weaknesses listed: CWE-190 and CWE-191.
CVE-2025-21656hwmon drivetemp5.5 (local vector)SCSI error codes were passed incorrectly, so the driver could report uninitialized data to userspace, for example if a disk was disconnected.

CVE-2026-99999 and CVE-2026-98432 appear in the Ubuntu notice's reference list, but the research provides no description or score for them, so their impact is not covered here. Check the Ubuntu notice for updates.

The 9.8 score for CVE-2026-74350 uses a network attack vector in the GitHub record, while the description centers on reading a corrupt OCFS2 inode. Treat the score as listed, but judge your real exposure by whether you mount OCFS2 volumes.

Who is realistically exposed

  • Anyone running Ubuntu 22.04 LTS with the linux-fips kernel. This notice only lists that package.
  • Systems that mount OCFS2 (a clustered file system) are the ones relevant to CVE-2026-74350. If you never use OCFS2, that path is less likely to matter, though updating is still the right move.
  • Hosts that run KVM virtual machines with AMD SEV are relevant to CVE-2026-63940.
  • Hosts with drivetemp-based disk temperature monitoring are relevant to CVE-2025-21656.

How to check your system

Run this on each server to see the running kernel. A version ending in 5.15.0-203-fips means you are already on the fixed kernel.

Show the running kernel version (Ubuntu)Shell
uname -r

This read-only command lists the installed FIPS kernel packages and their versions. Compare them with 5.15.0-203.213+fips1 and 5.15.0.203.117.

List installed linux-fips packages and versions (Ubuntu 22.04)Shell
dpkg -l | grep -i fips

To see whether any OCFS2 volumes are mounted, which tells you whether CVE-2026-74350 is relevant on that host, check the mount table.

Look for mounted OCFS2 file systems (read-only check)Shell
mount | grep ocfs2

What to do now

  1. Inventory Ubuntu 22.04 LTS hosts that use the FIPS kernel with the commands above.
  2. Update the packages with your normal process, as shown below.
  3. Reboot each host into the new kernel, since the fixes do not apply until then.
  4. Confirm with uname -r that the running kernel is 5.15.0-203-fips.
  5. Rebuild third-party kernel modules if the automatic step did not run, for example because the standard metapackages were removed.
  6. Record which hosts mount OCFS2 or run KVM with SEV so you can prioritize them.

Refresh the package lists and upgrade. This installs the new kernel but does not switch to it yet.

Apply the update (Ubuntu 22.04 LTS)Shell
sudo apt update && sudo apt upgrade
Caution. Rebooting interrupts services on that host. Plan a maintenance window, drain load balancers or migrate VMs first, and test that custom kernel modules load after the restart.
Reboot into the updated kernel (Ubuntu)Shell
sudo reboot

Monitoring after the update

Patch status drifts, so keep a regular check that kernels across your fleet match the expected version, and watch the Ubuntu security notices page for follow-up notices for other kernel flavors. Related notices listed on the page suggest more kernel updates may exist for other Ubuntu kernels, though the research does not detail them.

Kernel patching protects the host, but exposed web services need their own attention. Webforta's security scanner can check the public side of sites you verify, and monitoring can watch certificates, DNS and uptime. Neither replaces applying this kernel update.

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. CVE-2025-21656 - GitHub Advisory Databasegithub.com
  2. CVE-2026-63940 - GitHub Advisory Databasegithub.com
  3. CVE-2026-74350 - GitHub Advisory Databasegithub.com
  4. USN-9027-2: Linux kernel (FIPS) vulnerabilities | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • Linux kernel
  • USN
  • FIPS
  • patch management