Kernel update leaves system booting old kernel

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Security patching appears complete but uname -r shows older vulnerable kernel after reboot.

Environment & Reproduction

RHEL 7 with multiple installed kernels and custom grub2 settings.

Root Cause Analysis

GRUB default index points to old entry or kernel package install was partial.

Quick Triage

Run grub2-editenv list, grubby –default-kernel, and rpm -qa kernel to compare versions.

Step-by-Step Diagnosis

Inspect /etc/default/grub and generated grub.cfg; check journalctl -b -1 for previous boot context.

Solution – Primary Fix

Set default with grub2-set-default/grubby, regenerate grub config if required, then reboot.

Solution – Alternative Approaches

Pin known-stable kernel for specific hardware until driver compatibility is validated.

Verification & Acceptance Criteria

Post-reboot uname -r matches intended kernel and required modules load correctly.

Rollback Plan

Select previous kernel from GRUB menu and reset default back to last stable version.

Prevention & Hardening

Automate post-patch reboot verification that checks running kernel against target baseline.

Related Errors & Cross-Refs

Kernel mismatch alert, failed compliance scan, kABI module load warnings.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

grubby man page, RHEL 7 kernel management docs, grub2 administration guide.