The fixed build, kmod-lve 2.1-80, is now in the stable repository. A regular update installs it:
dnf update kmod-lve reboot
After the reboot, cat /sys/module/kmodlve/version should report 2.1-80.el8.
Posted Oct 13, 2026 - 23:55 UTC
Update
The fixed build, kmod-lve 2.1-80, is now listed on the changelog (CLKRN-2367: stop creating LVE groups in the blkio hierarchy), and its staged rollout to the stable channel has started. Servers will receive it progressively through the regular update path as the rollout reaches them.
To install it now on an affected CloudLinux 8 server with cgroup v1, run as root and then reboot: dnf update kmod-lve --enablerepo=cloudlinux-rollout-18-bypass reboot
Posted Oct 10, 2026 - 02:22 UTC
Update
Update, October 7, 2026
The fixed build, kmod-lve 2.1-80, is in the beta channel since October 7. The package changelog lists CLKRN-2367 (changelog.cloudlinux.com does not show 2.1-80 yet). To install it on an affected CloudLinux 8 server with cgroup v1, run as root and then reboot:
If you added kmod-lve to the exclude= line in /etc/dnf/dnf.conf earlier, remove it first, otherwise dnf will skip the package
A staged rollout of 2.1-80 to the stable channel has been requested, and this incident will be updated when it lands
Please note that kmod-lve 2.1-78 reached the stable channel on October 6, so a regular dnf update now installs it. If your CloudLinux 8 server runs cgroup v1 and has not been updated yet, add kmod-lve to (or keep it on) the exclude= line in /etc/dnf/dnf.conf until the fixed build is in the stable channel, or install 2.1-80 from the beta channel as shown above. Servers on cgroup v2 are not affected
On some CloudLinux 8 servers using cgroup v1, after updating to kmod-lve 2.1-78 or 2.1-79 and rebooting, LVEs cannot be created. Websites return 508 Resource Limit Is Reached, and the kernel log repeats lines like these (the numbers differ per server and account): LVE: [NNNN] init_lve: subsys 2 lveNNNN err -2 LVE: [NNNN] _lve_enter: Can't alloc ve #NNNN lvp #0, rc -22 CloudLinux 8 servers on cgroup v2 are not affected.
Workaround: Go back to kmod-lve 2.1-76 and keep it until the fixed build is released. Run as root (use 2.1-79 in the remove command if that is the installed build):