📖 ~1 min read
Table of contents
Symptom & Impact
`zypper patch` reports a kernel live patch installed, but `lscpu`-style verification still shows the unfixed CVE.
Environment & Reproduction
Occurs when the running kernel does not match the live patch package metadata.
Root Cause Analysis
Live patches target a specific kernel build; reboots into a different kernel orphan them.
Quick Triage
Compare `uname -r` to `rpm -qa kernel-livepatch-*`.
Step-by-Step Diagnosis
Inspect `/sys/kernel/livepatch/` to see which patches are enabled.

Solution – Primary Fix
Reboot to the kernel matching the live patch, then run `zypper patch –category=security`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Reinstall the matching `kernel-default` package to realign module versions.
Verification & Acceptance Criteria
`klp_state` for the patch shows `enabled` and CVE verification commands succeed.
Rollback Plan
Disable the live patch via `echo 0 > /sys/kernel/livepatch//enabled` if it misbehaves.
Prevention & Hardening
Keep livepatching policy aligned with kernel update cadence.
Related Errors & Cross-Refs
Related to `kdump` failing if kernel/initrd diverge.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE Live Patching documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.