Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
Linux & Systems / Infrastructure & Data / Linux

Ubuntu Issues USN-9174-1 Kernel Security Update for GCP FIPS Systems on 24.04 LTS

Canonical released USN-9174-1 for Ubuntu 24.04 LTS, updating the linux-gcp-fips 6.8 kernel packages to version 6.8.0-1074.82+fips1 across networking, storage, virtualization, and security subsystems.

Listen to this articleBrowser Voice
Ready
Official company logo or product image for ubuntu-usn-9174-1-linux-kernel-gcp-fips-24-04-lts
Official image or organization logo from ubuntu.com; identification only, no endorsement.
Event / context: 2026-11-19. Source check: October 28, 2026.

Canonical has published security advisory USN-9174-1 on November 19, 2026, delivering a sweeping set of vulnerability remediations for the Linux kernel tailored to Google Cloud Platform instances operating under Federal Information Processing Standards (FIPS) requirements. Distributed for Ubuntu 24.04 LTS (Noble Numbat), the update targets the linux-gcp-fips kernel variant and addresses flaws spanning more than 140 referenced CVE identifiers, including CVE-2026-98162, CVE-2026-98156, and CVE-2026-89810. According to the notice, attackers could potentially leverage the underlying kernel defects to compromise affected systems.

Operational Scope and Affected Ubuntu 24.04 LTS Packages

The advisory applies specifically to Ubuntu 24.04 LTS deployments running Canonical's FIPS-140 certified kernel builds for Google Cloud Platform. Unlike general-purpose cloud kernels, these images are maintained within the Ubuntu Pro FIPS Updates stream and carry cryptographic validation constraints suited for regulated workloads. To remediate the vulnerabilities documented in USN-9174-1, administrators must upgrade systems to version 6.8.0-1074.82+fips1 across three designated packages: linux-image-6.8.0-1074-gcp-fips, linux-image-gcp-fips, and linux-image-gcp-fips-6.8.

Canonical notes that the advisory is not a livepatch-only mitigation; a full system reboot is mandatory after applying the standard package update so the running kernel image transitions to the patched release. Because Ubuntu 24.04 LTS serves as a long-term support foundation for production cloud infrastructure, the release consolidates a wide backlog of upstream Linux 6.8 fixes into a single validated build.

Kernel Subsystems, Drivers, and Security Architecture Addressed

The breadth of USN-9174-1 reflects a comprehensive kernel rebase across hardware, virtualization, networking, and filesystem layers rather than an isolated patch for a single driver. In core compute and hardware enablement, the update corrects flaws across the x86, ARM64, PowerPC, RISC-V, and S390 architectures, alongside ACPI drivers, the PCI subsystem, Compute Express Link (CXL) drivers, the IOMMU subsystem, and the Intel NPU Driver and Compute Acceleration Framework. Hardware cryptography and entropy paths are also covered through fixes in hardware crypto device drivers and the hardware random number generator core.

For cloud-native and virtualized workloads, the release patches the KVM subsystem, Virtio drivers, the Virtio Host (VHOST) subsystem, VFIO and vDPA drivers, as well as hypervisor integration layers for Microsoft Hyper-V, Xen, and the ACRN Hypervisor Service Module. Storage and filesystem updates touch the block layer, NVMe and SCSI drivers, the Ublk userspace block driver, and major filesystems including Ext4, XFS, BTRFS, F2FS, EROFS, Overlay, Ceph, NFS client and server daemons, and SMB.

Networking and kernel security enforcement receive similarly broad attention. Patches address eXpress Data Path (XDP), Netfilter, IPv4, IPv6, TCP, SCTP, TLS, XFRM, and high-speed interface drivers from Mellanox, MediaTek, STMicroelectronics, Texas Instruments, and the Microsoft Azure Network Adapter (MANA). On the mandatory access control and instrumentation side, the update modifies both the AppArmor and SELinux security modules, BPF, control groups (cgroup), memory management, userfaultfd(), and KASAN debugging infrastructure.

ABI Changes, Third-Party Kernel Modules, and Deployment Workflows

From an operational engineering standpoint, the most consequential detail in USN-9174-1 is Canonical's explicit warning regarding an unavoidable Application Binary Interface (ABI) change. Because the kernel ABI shifted, the updated packages carry a bumped version number, which requires operators to recompile and reinstall all out-of-tree or third-party kernel modules present on GCP instances. Environments relying on custom security agents, specialized observability hooks, or proprietary storage modules built via DKMS should verify module compilation immediately during staging before rolling the update into production pools.

Canonical states that unless an administrator manually removed standard kernel metapackages—such as linux-generic, linux-generic-lts-RELEASE, linux-virtual, or linux-powerpc—a standard system upgrade handles the kernel package transition automatically. Still, cloud infrastructure teams managing immutable VM images or golden AMI-style snapshots on Google Cloud will need to rebuild base images, validate module compatibility under the new 6.8.0-1074-gcp-fips ABI, and schedule rolling instance replacements or controlled reboots.

FIPS 140 Compliance Boundaries and Ubuntu Pro Licensing Caveats

USN-9174-1 also highlights important entitlement and compliance boundaries for engineering teams. The patched linux-gcp-fips packages are delivered through the FIPS Updates channel under Ubuntu Pro, which Canonical provides with ten-year security coverage across more than 25,000 packages in the Main and Universe repositories and makes available free of charge for up to five machines. Organizations operating larger GCP fleets require active Ubuntu Pro subscriptions or GCP Pro-enabled instance images to pull the certified binaries.

Equally important, the primary advisory does not break down individual CVSS severity scores, active exploitation status, or per-CVE technical root causes within the notice body itself, listing only the aggregate subsystem scope and the associated CVE reference identifiers. Administrators seeking granular exposure assessments for specific compliance audits must cross-reference the individual CVE records alongside their specific enabled kernel modules and cloud instance configurations, and verify that any rebuilt third-party modules adhere to organizational FIPS boundary policies.

Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-19.

Follow your curiosity.

Pass the signal.