Ubuntu USN-8816-2 Updates GCP and OEM Kernels for 101 Vulnerabilities

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

USN-8816-2 covers GCP kernel packages on Ubuntu 24.04 and 26.04, plus the OEM 7.0 kernel on Ubuntu 26.04. These are different release/flavor combinations, not interchangeable install targets. Apply the matching binary update and reboot before recording the running system as updated.

Confirm Scope And Apply The Supported Fix

What to do now: identify whether the machine uses the GCP, GCP 64k or OEM flavor and which Ubuntu release it runs. Keep that supported combination, verify third-party module readiness and schedule a reboot with cloud-console or physical recovery access appropriate to the machine.

Open the authoritative advisory

Last verified: October 2, 2026 UTC against Canonical's notice and JSON. No cloud or OEM system was tested.

Scope And Authority

Product scopeLinux kernel vulnerabilities on Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble)
AdvisoryUSN-8816-2
CVEsCVE-2026-64530, CVE-2026-64534, CVE-2026-64535, CVE-2026-64541, CVE-2026-64551, CVE-2026-68083, CVE-2026-68457, CVE-2026-68476, CVE-2026-68477, CVE-2026-72014, CVE-2026-72020, CVE-2026-72033, CVE-2026-72041, CVE-2026-72046, CVE-2026-72064, CVE-2026-72065, CVE-2026-72069, CVE-2026-72083, CVE-2026-72084, CVE-2026-72085, CVE-2026-72098, CVE-2026-72129, CVE-2026-72130, CVE-2026-72137, CVE-2026-72139, CVE-2026-72191, CVE-2026-72192, CVE-2026-72194, CVE-2026-72217, CVE-2026-72220, CVE-2026-72221, CVE-2026-72222, CVE-2026-72226, CVE-2026-72234, CVE-2026-72248, CVE-2026-72249, CVE-2026-72251, CVE-2026-72277, CVE-2026-72278, CVE-2026-72279, CVE-2026-72287, CVE-2026-72288, CVE-2026-72289, CVE-2026-72296, CVE-2026-72299, CVE-2026-72317, CVE-2026-72318, CVE-2026-72319, CVE-2026-72320, CVE-2026-72322, CVE-2026-72323, CVE-2026-72329, CVE-2026-72339, CVE-2026-72348, CVE-2026-72351, CVE-2026-72355, CVE-2026-72366, CVE-2026-72381, CVE-2026-72393, CVE-2026-72398, CVE-2026-72399, CVE-2026-72412, CVE-2026-72417, CVE-2026-72422, CVE-2026-72429, CVE-2026-72436, CVE-2026-72442, CVE-2026-72451, CVE-2026-72463, CVE-2026-72466, CVE-2026-72472, CVE-2026-72473, CVE-2026-72477, CVE-2026-72491, CVE-2026-72493, CVE-2026-72494, CVE-2026-72495, CVE-2026-72496, CVE-2026-72501, CVE-2026-74255, CVE-2026-74267, CVE-2026-74268, CVE-2026-74269, CVE-2026-74287, CVE-2026-74310, CVE-2026-74345, CVE-2026-74350, CVE-2026-74361, CVE-2026-74376, CVE-2026-74384, CVE-2026-74394, CVE-2026-74398, CVE-2026-74401, CVE-2026-74406, CVE-2026-74427, CVE-2026-74428, CVE-2026-74433, CVE-2026-74434, CVE-2026-74436, CVE-2026-74439, CVE-2026-80665
Authoritative release date2026-09-29 07:52:53.963417 UTC
Authority revision dateNo separate material revision date is stated by Ubuntu; verified against the first-party notice API.
Affected versionsThe Ubuntu releases and source packages enumerated in USN-8816-2: Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble).
Fixed versionBinary packages listed by Canonical; select the matching installed flavor, not every row:
noble: linux-image-7.0.0-1013-gcp 7.0.0-1013.13~24.04.1
noble: linux-image-7.0.0-1013-gcp-64k 7.0.0-1013.13~24.04.1
noble: linux-image-gcp 7.0.0-1013.13~24.04.1
noble: linux-image-gcp-64k 7.0.0-1013.13~24.04.1
noble: linux-image-gcp-64k-7.0 7.0.0-1013.13~24.04.1
noble: linux-image-gcp-7.0 7.0.0-1013.13~24.04.1
resolute: linux-image-7.0.0-1013-gcp 7.0.0-1013.13
resolute: linux-image-7.0.0-1013-gcp-64k 7.0.0-1013.13
resolute: linux-image-7.0.0-1014-oem 7.0.0-1014.14
resolute: linux-image-gcp 7.0.0-1013.13
resolute: linux-image-gcp-64k 7.0.0-1013.13
resolute: linux-image-gcp-64k-7.0 7.0.0-1013.13
resolute: linux-image-gcp-7.0 7.0.0-1013.13
resolute: linux-image-oem-26.04 7.0.0-1014.14
resolute: linux-image-oem-26.04a 7.0.0-1014.14
resolute: linux-image-oem-7.0 7.0.0-1014.14
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Canonical identifies fixes across storage, filesystems and networking, among other kernel subsystems. Its update instructions require a reboot and warn of an ABI change requiring external modules to be rebuilt/reinstalled. Retained standard kernel metapackages normally bring in matching updates; confirm that transaction and module-build results are successful rather than assuming a downloaded image is ready to boot.

What To Validate Now

  1. Choose the correct row. Match Ubuntu release and GCP/OEM flavor to the listed binary package. Do not install the resolute OEM build on a noble GCP guest or switch page-size variants solely for this notice.
  2. Stage the update. Preserve recovery access and the prior supported boot option. Review package/module-build failures before permitting the reboot.
  3. Reboot and read back. Confirm the actual running kernel and installed image version. An updated metapackage or a service restart alone does not establish that the fixed kernel is active.
  4. Check the relevant hardware path. On GCP, test required guest networking, attached storage and workload health. On OEM systems, test the devices and power/resume behavior the deployment depends on.
  5. Record remaining machines. Retain release/flavor, package versions, boot and device results, and nodes deferred for compatibility or recovery issues.

Operational Cautions

These builds are listed in the security pocket, not as an ESM-only update. The broad CVE list is not evidence that every listed subsystem is active on every machine. Preserve the deployment's kernel flavor and required drivers; switching flavors to evade a compatibility failure is a separate change requiring its own validation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.