Staying Secure & Up to Date – Part 6: The Foundation – Host Patching, Kernel & Ubuntu Pro

Category: Projects / CVE Check | Reading time: ~7 minutes
Applications resting on a maintained kernel and hardware foundation
Series overview: In parts 3–5 we looked at the applications (containers). Now comes the foundation below them: operating system, kernel, and system packages – the house behind the wallpaper.

What is the core of your system? (the kernel, briefly)

The kernel is the boss inside your computer: it translates between hardware and programs and manages everything – including your virtual machines and containers. If there is a kernel vulnerability, it can potentially affect all services running on top. That’s why “keep the kernel current” deserves its own chapter.

With a hypervisor like Proxmox, there is more: All your LXCs (container systems) don’t have their own kernel — they use the host’s. A kernel update on the host therefore patches several “systems” at once. Conversely, if the host is outdated, all guests share the risk.

The quick update check per system (5 minutes)

Ubuntu/Debian:

sudo apt update
apt list --upgradable
uname -r

Proxmox:

pveversion
sudo apt update
apt list --upgradable
A snapshot and maintenance appointment prepare an orderly reboot

Most important rule after kernel updates: reboot once

A new kernel only takes effect after a reboot. The catch: on a hypervisor, reboot means all VMs/LXCs go down briefly. For a clean shutdown, install the qemu-guest-agent in VMs (a small helper that lets the host shut the VM down orderly instead of hard-stopping it):

# Inside the VM:
sudo apt install qemu-guest-agent
From practice: in one of my reboots, the host “hung” while shutting down a VM — because that exact helper was missing and the hypervisor waited for an answer. Since the agent is installed, reboots go through like butter, and a snapshot before the update (one click on Proxmox) gives you the safety to go back anytime.

Ubuntu Pro / ESM: the free “extension” for security updates

A common misunderstanding: on Ubuntu, many packages that deliver additional services belong to the “Universe” category — and for those, without Ubuntu Pro you get no more security updates once standard support ends. Typical examples from my practice: an image-processing library (ImageMagick), Python tools (pip), a graphics format (OpenEXR) — all with known flaws but, without the subscription, simply “no updates”.

The good news: Canonical offers Ubuntu Pro free for personal use on up to 5 machines. Setting it up takes 5 minutes:

1. Create a personal token at ubuntu.com/pro/subscribe (“Free for personal use”, no credit card).

2. Activate on the server:

sudo pro attach YOUR_TOKEN
sudo pro enable esm-infra esm-apps    # if not enabled automatically

3. Then update as usual:

sudo apt update && sudo apt upgrade

And under pro security-status you see how many vulnerabilities remain — after applying all ESM updates I had: 0 open.

Beginner tip: spend your 5 slots wisely — the two/three servers offering internet services first. Also: the subscription applies to official Ubuntu versions; a derived system like KDE neon is not supported (I managed that one without ESM).

Your monthly foundation rhythm

From now on, every system gets three regular questions (part 8 turns this into a ready-made checklist):

Any new updates?               → apt list --upgradable
Kernel switch/reboot due?      → uname -r + /var/run/reboot-required
ESM packages covered?         → pro security-status

Pro Corner

• Livepatch: with Ubuntu Pro, you can patch critical kernel flaws without a reboot (Kernel Livepatch is part of the subscription). Practical, but doesn’t permanently replace scheduled restarts.

• Unattended-upgrades: auto-apply small security updates (unattended-upgrades), keep kernel switches manual — a good compromise for a homelab.

• Reboot discipline: evaluate needs-restarting and /var/run/reboot-required; on Proxmox use reboot windows with snapshots plus qm guest cmd / pct shutdown. Enforce guest agents in all VMs.

• Major distro upgrades (e.g. Ubuntu 24.04 → 26.04) are projects of their own: backups + release notes first, not a “quick job”.


Why this matters: keeping applications current is half the job — without a patched foundation, the container concepts above stay shaky.

Next part: Part 7 – Watchtower: auto-updates and their three pitfalls.

AI Assisted AI Assisted