Start with the running kernel

A distribution name alone does not tell you whether live patching covers a server. Record the running kernel and check current KernelCare support for that environment. A server that has installed a newer kernel may still be running the older one until it reboots.

Separate patch coverage from general updates

KernelCare applies supported live patches to the running kernel. That is a specific part of security maintenance. It does not remove the need to maintain PHP, the hosting panel, applications and other packages. Keep a record of which updates were applied and which still need a maintenance window.

Decide when to reboot

Plan a reboot when required changes fall outside live-patch coverage or the operating system needs it. Before a scheduled restart, confirm that backups are recoverable and that someone can access the server console if the machine does not return normally.

Check your LicenseCage package

KernelCare is included with our cPanel and CloudLinux packages. Review those services before buying a separate license. For a standalone order, check compatibility first, then follow the current LicenseCage installation instructions.

A practical example

Suppose a server has received live kernel patches but its package manager also shows a newly installed kernel. Those are separate observations. The running kernel can differ from the newest installed package, and successful live patching does not prove that every pending operating-system change is active. Keep the running version, installed version and patch status in the same maintenance record so the next administrator can understand what still needs attention.

Checks to make

  • Record the output of uname -r before reviewing the installed kernel packages.
  • Check coverage for that exact kernel, distribution and architecture in the provider documentation.
  • Separate a patching failure from an expired service or an unreachable update endpoint.
  • Keep a maintenance window and console access for changes that still require a restart.

Making the decision

A useful maintenance decision states which changes are already covered, which are pending and why a reboot is or is not scheduled. If coverage cannot be established, investigate it rather than equating the presence of a KernelCare license with a fully patched machine.