Ubuntu Pro Livepatch for Kernel Updates Without Rebooting

Canonical’s Livepatch service applies selected Linux kernel security fixes to a running system by loading replacement code into memory. A vulnerable kernel function is redirected without restarting the machine, so applications, open terminals and active work continue. This is valuable where a restart would interrupt trading, operations or remote access.

Live kernel patching is not a replacement for apt upgrade. It covers security issues Canonical has judged suitable for live delivery, while ordinary package updates, firmware, user-space software and full kernel upgrades follow their normal path. A sound setup combines Livepatch with routine patching and planned reboots.

The steps below suit supported Ubuntu LTS installations, including eligible desktop and server systems. They cover entitlement, verification and practical limits that matter in Australia, from hybrid offices and NBN links to regulated environments. Keep recovery access and a current backup before changing a production host.

What Livepatch changes

Live patching works within the Linux kernel’s livepatch mechanism. Canonical’s service downloads a patch module, changes selected kernel functions in memory and switches execution to the corrected versions. The running kernel version reported by uname -r does not change.

Coverage is deliberate rather than universal. Canonical supports live delivery for many kernel CVEs, especially important kernel vulnerabilities, but some fixes cannot be expressed safely as a function replacement. Changes to kernel data structures, drivers or other incompatible code may need a conventional kernel package and restart.

Livepatch also does not update the rest of Ubuntu. OpenSSH client libraries, browser packages, container images, bootloaders and firmware remain the job of normal package management or vendor updates. Use sudo apt upgrade as the baseline, then use Livepatch to remove the immediate need to restart for supported kernel security fixes.

Access and entitlement

Ubuntu Pro is the entitlement and management layer for Livepatch. Create or sign in to an Ubuntu Pro account, obtain its token from the Ubuntu Pro dashboard and attach it to each authorised machine. The client uses that entitlement to determine which services and Ubuntu releases the host may use.

Canonical offers personal-use Ubuntu Pro access for a small number of machines, commonly five under the current personal-use terms. Those terms are not a commercial fleet licence. Australian businesses, schools and community organisations should use an appropriate paid or sponsored entitlement for production systems and confirm machine counts in the dashboard rather than assuming a personal token is sufficient.

Supported Ubuntu LTS releases can use the service directly, while older supported releases may require an Expanded Security Maintenance entitlement. The precise release, architecture and entitlement combination must be visible in sudo pro status --all; another Linux kernel, such as one supplied by a non-Ubuntu distribution, cannot be patched by Ubuntu Livepatch.

Preparing the Ubuntu host

Start with a healthy host. Run the normal update path, confirm that the installed kernel is supported and reboot beforehand if an update has replaced the kernel still in use. Livepatch can bridge the interval between installing a security update and restarting, but it should not be used to conceal an already overdue reboot.

Check the release and running kernel before making changes:

lsb_release -ds
uname -r
pro version

The pro command may be unavailable until the Ubuntu Pro client is installed. Ensure the machine has reliable storage, administrator access and enough free space for the client and temporary package work. A snapshot or tested backup remains important because a kernel change can affect low-level hardware access.

Network access must reach Canonical’s package and entitlement infrastructure. Ubuntu servers commonly operate behind authenticated proxies or restricted firewalls; allow the required HTTPS traffic or configure the client according to your organisation’s proxy rules. Australian branch sites using NBN or fixed wireless can lose connectivity during an outage, so patching should resume safely once the link returns rather than leaving the host permanently unprotected.

Enabling the service

On a supported Ubuntu release, install the Ubuntu Pro client from the standard repositories:

sudo apt update
sudo apt install ubuntu-pro-client

If that package is unavailable on the release, ensure snapd is installed and use sudo snap install ubuntu-pro-client. If Ubuntu Pro is already present, identify what is installed with pro version and keep that packaging route updated.

Attach the organisation’s or authorised user’s token, then enable kernel live patching:

sudo pro attach YOUR_TOKEN
sudo pro enable livepatch
sudo pro status --all

Attaching may enable some entitled services automatically, so inspect the status output before repeating configuration. Keep the token out of shared scripts, tickets and shell history where practical, and protect the Ubuntu Pro account with strong authentication.

The command should report that Livepatch is enabled and its daemon is active. If the current kernel does not support live patching, the client may ask for a normal restart into a compatible kernel. Enabling the service itself does not require a restart on every healthy system, but the first activation must be tested before the host is relied upon for unattended patch coverage.

Checking patches and daemon health

Livepatch normally applies eligible fixes automatically while the machine is online. Daily monitoring does not mean checking each CVE by hand; instead, confirm that the daemon remains active, that the client can contact Canonical and that no newer client release is required. These checks are useful after a broadband outage, firewall change or snap refresh.

Use the Pro tools to inspect both service and vulnerability status:

sudo pro status --all
sudo pro security-status
snap services ubuntu-pro-client

The security report shows known Ubuntu vulnerabilities and their remediation state, although wording varies between releases. Journal entries for the client’s unattended service help explain delayed downloads or failed patch application. Refresh the client with sudo snap refresh ubuntu-pro-client when it is snap-installed, or through apt when it came from the distribution repository.

For managed fleets, collect the same status fields centrally and alert on a stopped daemon, repeated download failures or an unsupported kernel. Record kernel security coverage separately from ordinary package patch levels. That makes it possible to demonstrate that a critical vulnerability has been mitigated by live patching without claiming that the whole machine is fully up to date.

Australian deployment considerations

Australia’s geography creates useful maintenance windows outside the traditional 9-to-5 schedule. Brisbane keeps UTC+10 throughout the year, Sydney and Melbourne shift with daylight saving, and Perth remains two hours behind Brisbane. An automatic patch arriving at 02:00 can therefore avoid peak activity in several states without relying on one national working-hour window.

Hybrid work and remote administration are now ordinary. Staff in Brisbane, Melbourne, Adelaide and Perth may connect to company systems from home over NBN or fixed wireless, while a small office or warehouse may have no engineer on site. Livepatch reduces the need for a physical console or coordinated workstation restart, though a plan is still needed for power loss, kernel faults and outages.

Australian compliance language also shapes the business case. The Privacy Act 1988 applies to many organisations handling personal information, state and territory health-records laws may also apply, and APRA-regulated entities must follow CPS 234. The Australian Signals Directorate’s Essential Eight provides a risk-based security framework. None of these instruments mandates Livepatch, but faster kernel vulnerability remediation can support patch-management controls and recorded evidence without creating a false compliance claim.

Small and medium businesses often depend on managed service providers to operate Ubuntu servers, retail point-of-sale systems, warehouse tools and logistics platforms. A repeatable Pro rollout should fit the provider’s monitoring and change process, with a clear route for major upgrades. Machines also need outbound access to Canonical; security and privacy policies should account for that connection and any associated metadata, rather than assuming all operational traffic remains in Australia.

Limits and reboot planning

The in-memory patch disappears after a reboot. Normal kernel packages, out-of-tree modules such as some proprietary graphics drivers, firmware and user-space applications still need their own updates and, where required, restarts. A new major kernel or LTS release is also outside the normal live-patching path.

Livepatch is not the host kernel for containers, and it generally does not patch a Linux kernel running under Windows Subsystem for Linux. Check support for virtual machines, embedded appliances and specialist hardware before deployment. Unsupported combinations can connect to the Pro service yet leave kernel vulnerabilities uncovered, so verification must be based on the running kernel and applicable release.

Plan reboots for patched package sets that need one, kernel upgrades and maintenance that touches drivers. Keep the previous kernel available as a recovery option, then confirm the running version with uname -r after maintenance. If the daemon reports a problem, continue with standard Ubuntu security updates and arrange the required restart rather than disabling security tooling and waiting indefinitely.

Livepatch is a targeted layer for reducing kernel vulnerability exposure and service interruption. It works best when the Ubuntu Pro entitlement is correct, the supported kernel and client are healthy, connectivity is dependable and administrators can distinguish live kernel fixes from ordinary package updates.

The essential rule is simple: use Livepatch to shorten exposure for supported kernel flaws, keep the rest of Ubuntu patched, and reboot deliberately whenever a full kernel change or broader maintenance requires it.