← Back to all posts

Verify an Ubuntu Kernel Security Update After Reboot

Match the Ubuntu security notice to your kernel flavor, then verify the installed image and the kernel actually running after reboot.

A rounded dark system monitor with a colored gauge and status lights

A patch ticket says the kernel update was installed. The host has two kernel images on disk, and a reboot is planned for tonight. Which version should the next operator expect to see, and what should they record if the machine comes back on the old one?

Use three pieces of evidence: the vendor’s fixed package, the version installed on the host, and the release of the kernel that actually booted. Collect the first two before the maintenance window so the person checking the reboot has a specific target.

Match the notice to the host

Run these checks on the Ubuntu host or inside the guest VM that owns the kernel. An ordinary container reports the host kernel through uname while reading its own filesystem and package database. Those observations describe different systems.

. /etc/os-release
printf '%s %s\n' "$ID" "$VERSION_ID"
dpkg --print-architecture
uname -r
dpkg-query -W -f='${db:Status-Abbrev}\t${Package}\t${Version}\n' 'linux-image-*'

The last command may show old package records as well as installed images and metapackages. Read entries with status ii as installed. An image metapackage tracks a kernel series through dependencies. The versioned image package is the evidence to match to the running release.

Look up the notice for the Ubuntu release and kernel flavor you found. For example, USN-9027-2, published November 13, 2026, lists linux-image-5.15.0-203-fips at package version 5.15.0-203.213+fips1 for its Ubuntu 22.04 FIPS Updates case. That row is one example of a versioned image and its package revision. Use the corresponding row in Canonical’s CVE package status for your own flavor, including generic, HWE, or cloud-specific series as applicable.

Record the version that booted

Once the approved update is installed, record the fixed image package and its full version. Save the running release and the current boot ID before rebooting. After the maintenance reboot, rerun the same commands on the same host.

running=$(uname -r)
printf 'boot_id=%s\nrunning=%s\n' "$(cat /proc/sys/kernel/random/boot_id)" "$running"
dpkg-query -W -f='${db:Status-Abbrev}\t${Package}\t${Version}\n' \
  "linux-image-$running" "linux-image-unsigned-$running" 2>/dev/null |
  awk '$1 == "ii"'

Signed and unsigned kernel images can have different package names. An empty package result needs investigation. Check whether the host uses a separately managed or custom kernel before relying on Ubuntu package status. When comparing complete Debian package versions for the same package and series, use dpkg --compare-versions. Text sorting can put a package ending in .10 before .9.

Observation after maintenance What to check next
Boot ID changed and the running image matches the fixed package Save the observed image version and check the service that required the maintenance window.
Boot ID changed and the old release is still running Check the bootloader’s selected entry and whether the new image can boot. Keep the ticket open while investigating.
Boot ID stayed the same Confirm that the reboot completed and that both captures came from the same host.
The running package has no matching row Check the flavor and package provenance before recording a fix decision.

Systems using Canonical Livepatch have a separate source of runtime evidence. Inspect the applied CVE list with canonical-livepatch status --verbose when that client is configured, and record whether the running kernel is covered for the specific CVE. Canonical distinguishes applied live patches from fixes available in the kernel selected for the next boot. Livepatch client status

For a short handoff, record host label / Ubuntu release and flavor / notice / installed image version / running release / reboot time / service check. Someone reading it later should be able to repeat the check without guessing which kernel family the ticket referred to. For practice reading the running release, use the LabEx kernel version exercise.

References