ClickCease What Is Live Patching? | Learn More About Linux Live Patching

Learn More About Linux Live Patching

If you're looking to see how Linux live patching can automate security patching without
rebooting your service, please check out our resources below.

Ultimate Guide to Live Patching for Linux Kernels

Learn More About Linux Live Patching

Live Patching In the DevOps Workflow

Learn about Linux Live Patching with Continuous Integration tools.

Does Live Patching Slow Systems Down?

Looking at performance implications with different Live Patching solutions.

IT Automation With Live Patching

Where does KernelCare Enterprise fit in your existing IT infrastructure?

Linux Live Patching vs. Server Reboot Cycles: Pros and Cons

What's the big deal with having to reboot with manual patching?

How Live Patching Works with KernelCare Enterprise

TuxCare’s KernelCare Enterprise delivers fast, automated patching without downtime or disruptions – so how do we do it?

Are you currently using a Linux Live Patching service such as KSplice or Kpatch? Check out our competitor reviews here.

Oracle KSplice vs. KernelCare Red Hat KPatch vs. KernelCare


When there is an issue or security risk that affects Linux systems, an update that fixes the issue is made available. Patching is when that update is applied to the core of the Linux operating system, also known as the kernel.

When applying an update or patch, a Linux system will usually require a reboot for it to be applied. With Live Patching, the patch is applied without needing to reboot the system, keeping it online, or live.

Check your system’s log files in the /var/log directory to see when the most recent patch was applied, or run the command: rpm -qa –last.

Applying a patch to a kernel requires you to acquire the patch file by downloading or using the git command. Then you apply the patch with the patch command to the specific file or directory and compile the kernel. Once compiled, reboot your system and the updated kernel should be in effect.

Manual Linux patching requires a reboot to apply the patch to the system. Until the system is rebooted, the patch will not be applied.

Live Linux patching does not require a reboot because it applies a patch to an instance of the kernel that is running in live memory and makes the updates in real-time.

Linux servers need to be patched to fix security vulnerabilities, errors in the code, and to maintain compliance with rules and regulations – depending on the industry or use. Not patching a Linux server can have severe consequences.

Linux patches can be automated with a Live Patching service like TuxCare’s KernalCare that downloads and applies patches without having to reboot or take down a machine. The entire process takes a single command to set up, and after that, runs entirely in the background.

You can see if a security patch is installed on Linux by checking your log files in the /var/log directory or by using the command rpm -qa –last to see the latest update that was installed.

Didn't Find The Answers You Were Looking For?


Talk to a TuxCare Expert

Tell us your challenges and our experts will help you find the best approach to address them with the TuxCare product line.




Linux & Open Source

Subscribe to
our newsletter