Ubuntu USN-8730-4 Fixes Linux kernel Vulnerability

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

Quick Answer

Ubuntu's USN-8730-4 addresses CVE-2026-53131 in five Ubuntu 22.04 kernel flavors: Azure FDE, Intel IoTG, KVM, Oracle, and Xilinx ZynqMP. Install the fixed build for the flavor actually in use. A reboot is required, and the ABI change requires rebuilding and reinstalling any third-party kernel modules; the full warning appears below.

Confirm Scope And Apply The Supported Fix

What to do now: Record the running kernel and installed kernel packages, match one of the five jammy builds below, prepare third-party modules and recovery access, then schedule the update and required reboot.

Open the authoritative advisory

Last verified: 2026-09-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeLinux kernel vulnerability on Ubuntu 22.04 LTS (jammy)
AdvisoryUSN-8730-4
CVECVE-2026-53131
Authoritative release date2026-09-21 13:04:26.776039 UTC
Authority revision date2026-09-21 13:04:26.776039 UTC
Affected versionsThe Ubuntu releases and packages enumerated in USN-8730-4: Ubuntu 22.04 LTS (jammy).
Fixed versionjammy: linux-azure-fde 5.15.0-1120.129 / jammy: linux-intel-iotg 5.15.0-1110.116 / jammy: linux-kvm 5.15.0-1107.112 / jammy: linux-oracle 5.15.0-1112.118 / jammy: linux-xilinx-zynqmp 5.15.0-1078.82
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

Ubuntu identifies fixes in IPv6 networking and Netfilter for CVE-2026-53131. After a standard system update you need to reboot your computer to make all the necessary changes. ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual, linux-powerpc), a standard system upgrade will automatically perform this as well.

What To Validate Now

  1. Inventory. Identify jammy hosts using linux-azure-fde, linux-intel-iotg, linux-kvm, linux-oracle, or linux-xilinx-zynqmp. Record active and installed kernel versions, third-party modules, and the host owner.
  2. Establish applicability. Match the precise kernel flavor to its table entry; these five 5.15 builds are not interchangeable merely because every host runs Ubuntu 22.04.
  3. Remediate. Apply jammy: linux-azure-fde 5.15.0-1120.129 / jammy: linux-intel-iotg 5.15.0-1110.116 / jammy: linux-kvm 5.15.0-1107.112 / jammy: linux-oracle 5.15.0-1112.118 / jammy: linux-xilinx-zynqmp 5.15.0-1078.82 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. After reboot, confirm the intended fixed kernel is running and required third-party modules load. Check the host's storage, network, and application functions, retaining module-build and boot results.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Keep working recovery access and an approved boot recovery plan before changing the kernel. A package installation alone does not prove the fixed kernel is running. The advisory identifies IPv6 and Netfilter fixes but does not establish that every host exposes the same attack path.

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.