CloudLinux users should review CVE-2026-31431, known as "Copy Fail." This Linux kernel privilege-escalation vulnerability affects CloudLinux 9 and CloudLinux 10 systems. CloudLinux 7 is not affected, while CloudLinux 8 requires a patched kernel when one becomes available.
CloudLinux systems running an affected kernel should be updated as soon as a suitable security patch is available. A kernel-level privilege-escalation vulnerability can allow a local attacker or compromised account to gain elevated privileges on the server.
For the latest vendor information, review the CloudLinux security advisory.
What Is CVE-2026-31431 "Copy Fail"?
CVE-2026-31431 is a Linux kernel privilege-escalation vulnerability. An attacker who already has local access to an affected system may be able to exploit the kernel flaw to obtain higher privileges.
On a shared hosting or cPanel server, this is particularly important because a compromised low-privilege hosting account could potentially become a much more serious server-level security problem if the underlying kernel is vulnerable.
The safest approach is to install the appropriate patched kernel and reboot the server when required.
Check Whether Your CloudLinux Server Is Affected
First, identify your operating system version:
cat /etc/os-release | grep -E '^(ID|VERSION_ID)='
Use the output to determine your CloudLinux version:
| CloudLinux Version | Status |
|---|---|
VERSION_ID="9..." |
Affected — apply the available security patch |
VERSION_ID="10..." |
Affected — apply the available security patch |
VERSION_ID="8..." |
Check the CloudLinux advisory for patch availability |
VERSION_ID="7..." |
Not affected by this vulnerability |
Check the Current Kernel
You should also check which kernel your server is currently running:
uname -r
For CloudLinux 10, the source guidance identifies 6.12.0-124.52.2.el10_1 or later as the patched kernel level. Always compare your installed kernel with the current CloudLinux advisory before deciding whether additional updates are required.
CloudLinux 10: Apply the Kernel Update
The source guidance uses the AlmaLinux testing repository to obtain the patched kernel. Because enabling a testing repository can expose a system to packages that are not part of the normal production repositories, take a backup and schedule a maintenance window before proceeding.
Enable the AlmaLinux 10 testing repository:
dnf install -y https://repo.almalinux.org/almalinux/10/extras/x86_64/os/Packages/almalinux-release-testing-10-1.el10.x86_64.rpm
Update the kernel:
dnf update kernel
Reboot the server so that it starts with the updated kernel:
reboot
After the server comes back online, verify the active kernel:
uname -r
The source guidance expects 6.12.0-124.52.2.el10_1 or later for CloudLinux 10.
Once the required package has been installed, disable the testing repository so routine updates do not unintentionally install other testing packages:
dnf config-manager --disable almalinux-testing
CloudLinux 9: Apply the Kernel Update
The same general process can be used for CloudLinux 9, but the repository package is different.
Install the AlmaLinux 9 testing repository package:
dnf install -y https://repo.almalinux.org/almalinux/9/extras/x86_64/os/Packages/almalinux-release-testing-9-1.el9.noarch.rpm
Update the kernel:
dnf update kernel
Reboot the server:
reboot
After rebooting, verify the running kernel:
uname -r
After confirming that the required kernel is active, disable the testing repository:
dnf config-manager --disable almalinux-testing
CloudLinux 8: Check for the Official Patch
For CloudLinux 8, patch availability should be checked against the current CloudLinux advisory. Do not install an unrelated kernel package simply to work around the vulnerability.
If CloudLinux provides a mitigation or patched kernel for your system, follow the vendor's current instructions and verify the running kernel after the change.
After the Kernel Reboot
A kernel update requires a reboot before the new kernel becomes active. After the server is back online, verify the kernel again:
uname -r
If you also experience a CloudLinux licensing problem after the reboot, first verify the license status and review the relevant CloudLinux or license-provider documentation. Do not use unofficial license activation scripts or firewall rules to restore licensing.
If a cPanel license issue occurs after a firewall or server restart, see cPanel License Fails After CSF or Firewall Restart — Fix.
Important Maintenance Notes
- Take a current backup before changing the production kernel.
- Schedule the reboot during an appropriate maintenance window.
- Make sure you have console access or another recovery method before rebooting a remote server.
- Verify the running kernel with
uname -rafter the reboot. - Disable temporary testing repositories after completing the required update.
- Follow the latest CloudLinux advisory if package versions or mitigation instructions change.
When to Contact ServerLicenser Support
Contact ServerLicenser Support if you need assistance preparing a maintenance window, updating the kernel, verifying the server after reboot, or troubleshooting a related CloudLinux or cPanel issue.
If you do not want to perform the kernel update yourself, professional server management can help reduce the risk of applying the update incorrectly on a production server.
Quick Checklist
- Check whether the server is running CloudLinux 9 or 10.
- Run
uname -rto identify the active kernel. - Compare the kernel against the current CloudLinux security advisory.
- Install the appropriate patched kernel.
- Reboot the server when required.
- Run
uname -ragain after reboot. - Disable any temporary testing repository after the update.
- Monitor cPanel, CloudLinux, websites, and other services after the maintenance.
