I am using webmin (which uses yum) to install updates on my server, and it somestimes updates kernel as well including kernel-firmware and kernel-headers. Do I need to restart the server after a kernel update?


4 Answers 4


There are at least two reasons for rebooting:

  1. You probably want to use the advantages of the newer version (security fixes)
  2. Usually during a kernel update the module tree of the old kernel is removed. Thus if you (or some script) unload a module then the system cannot load it again because it finds only the newer one on disk (if at all) and this is compiled for a different kernel and thus cannot be loaded (at least usually).
  • 5
    On Red Hat/CentOS and Ubuntu (and all distros which are responsible about how they do kernel upgrades), #2 doesn't happen, because the old kernel package is left in place. I very much wish Debian would take the hint from them...
    – Paul Gear
    Commented May 1, 2013 at 10:51
  • @PaulGear , a couple times on Ubuntu, after a kernel update, I didn't reboot, but later that day, something broke. (Sorry, it was a long time ago, but it seemed due to not rebooting after the kernel update.) Any idea what it might be? I came here looking for more information on why I need to reboot after a kernel update, as I wish I didn't have to. (If I accept the security risk.) Commented Jun 19, 2021 at 14:28
  • I'm afraid "something broke" isn't specific enough to answer that question. For the record, since 2013, Debian has started releasing updates in the same way as Ubuntu, and the old kernel is not immediately removed.
    – Paul Gear
    Commented Jun 20, 2021 at 20:32
  • @Flurrywinde Have a look into the Ubuntu kernel livepatch facility - free for personal use (up to 3 machines): ubuntu.com/security/livepatch
    – Paul Gear
    Commented Jun 20, 2021 at 20:34
  • Re: "something broke." Yeah, I know. Sorry. I can't even remember for sure, but I think it involved having to uninstall and reinstall a package. I suspect it was after 2013 too, but can't even be sure of that anymore. Sheesh. But it happened more than once, so I suspect not rebooting after a kernel update can still break things despite the above. Thanks for the link to the livepatch facility. Looks good! Commented Jun 22, 2021 at 14:00

To actually use the new kernel you will have to reboot.
No way around that.

Do you have to reboot immediately after installing the update ?
In general NOT, you can schedule the reboot for a more convenient moment.

But it is NOT a good idea to install more updates before you reboot.
Some updates have different versions depending on which kernel you are running.

And anyway: After rebooting with a new kernel always check for updates. Some of your existing packages may need a new version after the kernel update.


It depends.

Ksplice takes care of all security updates but it depends on the updates and it's not free. You can check here for details for yum as well.

You also have the option of using kexec which will require a reboot but will skip the hardware part of the boot.


With Linux 4.0 and later, they say you don't have to reboot for the Kernel anymore.


  • This may not be enabled by default. For example, this url: wiki.archlinux.org/title/Kernel_live_patching implies additional steps must be taken. Thanks for the answer, though, as it does provide useful information. (I didn't know about this feature until I saw it.) However, as it's written, it's misleading, so that might explain the downvotes. I got excited, thinking I didn't have to reboot my system after kernel updates anymore, but it's not true. Commented Jun 19, 2021 at 14:23
  • I have a Fedora server that patches its Kernel without rebooting. I confirm this by seeing what version the running Kernel reports to be running. I recently upgraded the distro and even that process did not to want to reboot. This leads me to believe they have this working very well.
    – Andrew
    Commented Jun 20, 2021 at 19:39
  • I looked into this more, and Arch doesn't. (I did the test here: linux-audit.com/… ) I wondered why and found this: bugs.archlinux.org/task/61822 Thus, it looks like there's a security implication to live-patching the kernel, but I could see how on a server, the downtime of rebooting might outweigh this concern, which might be why your Fedora installation does it? Commented Jun 22, 2021 at 14:17
  • 1
    Looks like I have to take back what I said about the distro upgrade not needing a reboot. There is a separate command "dnf system-upgrade reboot" that needs to be run.
    – Andrew
    Commented Jun 23, 2021 at 3:03
  • 1
    @Andrew I've upvoted because it gives useful insight as what is possible but I would urge you to edit your answer with your comments combined and correct the misleading parts. Commented Oct 5, 2021 at 15:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .