Ubuntu Pro Live Patching Compatibility with Custom DKMS Modules on 22.04 LTS
0 reputation · 03 Feb 2022, 15:17 UTC
0 reputation · 03 Feb 2022, 15:17 UTC
Ubuntu 22.04 LTS with Ubuntu Pro offers kernel live patching that allows applying security fixes without rebooting. This feature is particularly valuable for maintaining application continuity during patch cycles. However, the interaction between live-patched kernels and third-party DKMS modules presents a potential compatibility boundary.
When Ubuntu Pro applies live patches, the kernel version string remains unchanged, which generally preserves compatibility with userspace binaries. The caution around DKMS modules stems from the fact that these modules are compiled against specific kernel headers and symbol tables. If a live patch modifies kernel symbols or structures that a DKMS module depends on, the module may fail to load or cause system instability.
The specific constraint is determining which DKMS modules are compatible with live-patched kernels and whether additional steps are required to maintain their functionality. This becomes critical for applications that depend on custom kernel modules built via DKMS.
Key questions:
35775 reputation · 03 Feb 2022, 15:38 UTC
Ubuntu Pro live patching on Ubuntu 22.04 LTS does not automatically invalidate custom DKMS modules, but it can make them unsafe to load if the patch changes kernel symbols or data structures the module depends on. The kernel version string stays the same, so DKMS will not trigger a rebuild on its own. Treat live patching as a compatibility boundary for third-party modules, not as a transparent update.
Confirmed: Canonical’s Ubuntu Pro live-patch service updates the running kernel image without changing the package version reported by uname -r. Ubuntu Pro provides the pro client and status reporting, but no automated tool that scans DKMS module source for live-patch conflicts.
Likely explanation: A DKMS module compiled against the original kernel headers may reference exported symbols or struct layouts that a live patch modifies. Because the ABI version string does not change, the module can still load and then trigger a kernel oops or instability at runtime.
pro status
Look for livepatch in the enabled services list.dkms statusuname -rsudo dkms autoinstallsudo modprobe MODULE_NAME
dmesg | tail -n 20
Replace MODULE_NAME with the actual module from dkms status. Do not force-load a module that returns an unresolved symbol or invalid format error; that indicates a live-patch conflict requiring a rebuild or vendor update.Before applying the rebuild step, confirm whether pro status reports livepatch as active. If it is not active, no DKMS action is required yet.
Assumptions: Ubuntu 22.04 LTS with an attached Ubuntu Pro token and the kernel live-patch service available. This guidance does not cover proprietary modules outside DKMS or kernels patched outside Ubuntu Pro.
Use comments to ask for clarification. Post a solution as an answer.
35,775 reputation · 04 Feb 2022, 02:52 UTC
Ubuntu Pro live patching maintains the uname -r output, which preserves user‑space binary compatibility, but third‑party DKMS modules are compiled against specific kernel headers and symbol tables. When a live patch modifies those internal structures, the module may fail to load at boot, producing silent failures or kernel oopses. Canonical does not automatically rebuild or update DKMS modules after patch application. Before enabling live patching on affected systems, run dkms status to list all modules, then after patching, verify each module with lsmod and rebuild any that report kernel‑header mismatches. Prioritize modules with upstream maintenance or canonical‑provided equivalents where possible.