Advisory · Linux kernel · local root

CloudLinux ZDI-CAN-33367 and Fragnesia: kernel local-root fixes

Two flaws in the Linux networking stack turn a shell as an ordinary hosting user into root. ZDI-CAN-33367 was published by CloudLinux on 23 October with a public exploit and no fixed kernel; fixed kernels and livepatches followed over the next two weeks. Fragnesia, CVE-2026-46300, was fixed upstream in May and entered CISA’s catalog on 28 October because it is being chained with the PHP2Shell flaws to go from one web request to root. On a shared server either one makes a single compromised site a server incident.

This page collects the coverage of both kernel flaws from the weekly briefings of 26 October, 2 November and 9 November 2026, oldest first. Each section is dated; the newest is the current status.

ZDI-CAN-33367
CloudLinux 7 Hybrid, 8, 9 and 10; no CVE assigned. Fixed kernels or KernelCare livepatches on every line by 5 November
Fragnesia
CVE-2026-46300, fixed upstream in May; in CISA’s KEV since 28 October, chained with PHP2Shell
What does not stop it
CageFS, per CloudLinux’s own test; an installed kernel that has not been booted
Check
The running kernel with uname -r against the vendor’s fixed build, and kcarectl --patch-info where KernelCare is used

26 October · CloudLinux · ZDI-CAN-33367

CloudLinux: a local root zero-day with a public exploit and no fixed kernel

CloudLinux published its advisory on 23 October for ZDI-CAN-33367, a Linux kernel flaw that has no CVE assigned yet. The bug is in skb_zerocopy(), the networking code that builds packets from existing memory pages rather than copies. A local user can use it to change the contents of a file they are only allowed to read, through the page cache, and from there the usual route to root is open. The attacker needs a shell on the machine, which on shared hosting every customer account provides. A public exploit exists. The fix for Dirty Frag, CVE-2026-43284, added a check for a shared-fragment marker; in this bug the marker is lost before the check runs, so a server with the Dirty Frag fix is still exposed.

CloudLinux measured CageFS against it and is direct about the result: inside the cage the exploit succeeded. What does close the local route is whether ordinary users can create user namespaces. CloudLinux 7 is not affected, because its kernel never decrypts in place. CloudLinux 7 Hybrid is exposed as shipped. CloudLinux 8 and 9, and their ELS variants, are conditional: installations since mid-2024 ship with the namespace path closed by default, older installations have it open. CloudLinux 10 and CloudLinux for Ubuntu 22.04 are closed by default. The check is one command, and 0 is the safe answer:

shell
sysctl user.max_user_namespaces

No fixed kernel has shipped for any line; the upstream fix was posted for review and is not merged. KernelCare is ahead of the kernels: the livepatch is in the production feed for CloudLinux 10 and AlmaLinux 10, in review for CloudLinux 9, in progress for CloudLinux 8, in preparation for CloudLinux 7 Hybrid and 9 ELS, and not started for Ubuntu 22.04, whose kernel fix will come from Canonical. CloudLinux 8 ELS has no livepatch stream at all, so there the only route is a kernel upgrade and a reboot when one exists. On CloudLinux 10:

shell
kcarectl --update
kcarectl --patch-info | grep -i 33367

CloudLinux notes that --patch-info is the command that shows it; --info does not.

Figure 1 · At a glance

Two kernel flaws, one result: a hosting user becomes root.

QuestionAnswer
ZDI-CAN-33367Public exploit on 23 October; CloudLinux 7 Hybrid, 8, 9 and 10
Its fixFixed kernels or KernelCare livepatches on every line by 5 November
Fragnesia · CVE-2026-46300In CISA’s KEV since 28 October, chained with PHP2Shell
Its fixUpstream since May: check the running kernel is from the last six months
Does not stop eitherCageFS; a fixed kernel that is installed and not booted
The points that decide what to do about the CloudLinux ZDI-CAN-33367 and Fragnesia CVE-2026-46300 kernel flaws, as stated in the sections below.
CloudLinux lineExposure as shippedFix status on 23 October
CloudLinux 7Not affectedNothing needed
CloudLinux 7 HybridExposedKernel waits on upstream; livepatch in preparation
CloudLinux 8, 8 ELSClosed on installs since mid-2024; exposed on older onesKernel waits on upstream; livepatch in progress for 8, none possible for 8 ELS
CloudLinux 9, 9 ELSClosed on installs since mid-2024; exposed on older onesNo fixed kernel; livepatch in review for 9, in preparation for 9 ELS
CloudLinux 10Closed by defaultNo fixed kernel; livepatch in the production feed
CloudLinux for Ubuntu 22.04Closed by defaultKernel via Canonical; livepatch not started

2 November · CloudLinux · ZDI-CAN-33367

CloudLinux: the fixed kernels are out for 7h, 8, 9 and 10, and they need a reboot

Last week’s briefing covered ZDI-CAN-33367 when it had a public exploit, no fixed kernel on any line, and a livepatch only for CloudLinux 10. CloudLinux’s advisory has been updated since. Fixed kernels moved to production on 28 October for CloudLinux 9 and 10, through the AlmaLinux kernel updates, and on 30 October for CloudLinux 7 Hybrid and CloudLinux 8. The ELS variants of 8 and 9 were still pending on their extended-support channel at the cut-off, with 8 ELS waiting on a kernel uplift to 5.14 and no livepatch possible; CloudLinux for Ubuntu 22.04 waits on Canonical. KernelCare has moved less: the livepatch is in production for CloudLinux 10 only, in review for 9, in progress for 8 and in preparation for 7 Hybrid and 9 ELS. Still no CVE.

Installing the package is not the fix; running it is. A kernel that is installed and not booted protects nothing, so the sequence is update, reboot, and compare the running version against the table:

shell
dnf update "kernel*"
reboot
uname -r

Use yum on CloudLinux 7 Hybrid. Where a reboot cannot happen today, keep the mitigation from last week in place, which newer CloudLinux 8 and 9 installs and every CloudLinux 10 already have by default, and schedule a short window:

shell
sysctl user.max_user_namespaces
echo "user.max_user_namespaces = 0" > /etc/sysctl.d/99-zdi-33367.conf && sysctl --system
CloudLinux lineFixed kernelStatus at 2 November
CloudLinux 7Not affectedNothing needed
CloudLinux 7 Hybrid4.18.0-553.177.1.lve.1.el7hProduction since 30 October; livepatch in preparation
CloudLinux 84.18.0-553.177.1.lve.1.el8Production since 30 October; livepatch in progress
CloudLinux 8 ELSPending (5.14 uplift)No fixed kernel; no livepatch possible; mitigation only
CloudLinux 95.14.0-687.60.1.el9_8 or laterProduction since 28 October; livepatch in review
CloudLinux 9 ELSPendingNo fixed kernel; livepatch in preparation; mitigation only
CloudLinux 106.12.0-211.69.1.el10_2 or laterProduction since 28 October; livepatch in the production feed
CloudLinux for Ubuntu 22.04Via CanonicalPending; livepatch not started

9 November · Linux kernel · CVE-2026-46300 and ZDI-CAN-33367

Fragnesia: the kernel half of the PHP2Shell chain, in CISA’s catalog since 28 October

CVE-2026-46300, named Fragnesia, is a local privilege escalation in the Linux networking stack from the same family as Dirty Frag. When TCP receive coalescing moves page-cache-backed fragments into another socket buffer, the marker that says “shared, do not write in place” is lost, and the ESP-in-TCP input path then decrypts over the page cache. In practice that lets an ordinary local user change files they can only read, and from there take root. The kernel fix, which propagates the marker, was published in May; secondary reports put the affected range at kernels released before 13 May 2026, with fixes in the 5.10, 5.15, 6.1, 6.6, 6.12 and later stable lines.

What changed is CISA’s 28 October catalog entry, which says the flaw “can be chained with CVE-2026-109618 and CVE-2026-109619 to implant PHP webshells and run commands as root”, with a three-day deadline. BleepingComputer reports that Dream Security published a campaign using exactly that chain, a customised PHP2Shell exploit followed by Fragnesia, with about 40 post-exploitation scripts and 25 servers rooted across the United States, Japan, Taiwan and South Korea. That is one vendor’s report via one outlet. It is also the scenario every shared-hosting operator plans for: a single web request to an unpatched PHP becomes a shell as the web user, and an unpatched kernel turns the shell into the whole server.

Distributions shipped the fix months ago, so for most servers the question is whether the running kernel is from the last six months. The package changelog answers whether an installed build carries it, and uname answers whether that build is the one running:

shell
uname -r
rpm -q --changelog kernel-core kernel 2>/dev/null | grep -m1 "CVE-2026-46300"
apt changelog "linux-image-$(uname -r)" 2>/dev/null | grep -m1 "CVE-2026-46300"

On Debian, the security tracker lists bookworm fixed from 6.1.176-1 and trixie from 6.12.107-1. An empty grep on an RPM system is not proof of exposure, because some vendors list kernel fixes by upstream commit rather than CVE; compare the running version against your distribution’s advisory for the CVE in that case.

The CloudLinux kernel bug covered in the last two issues, ZDI-CAN-33367, is a different flaw in the same area and still has no CVE. CloudLinux’s 5 November update closes the gaps from last week: fixed TuxCare kernels are now in production for 8 ELS and 9 ELS, and KernelCare livepatches are in production for 7 hybrid, 8, 9, 10 and CloudLinux for Ubuntu 22.04. Only the 9 ELS livepatch is still in preparation, and 8 ELS has no livepatch stream at all, so it needs the kernel and a reboot.

Common questions

Common questions about the kernel local-root flaws

Does CageFS protect my CloudLinux server from ZDI-CAN-33367?

No. CloudLinux ran the exploit inside the cage and it succeeded. What closes the local route is user.max_user_namespaces at 0, which newer CloudLinux 8 and 9 installs and all CloudLinux 10 installs have by default and older installs and CloudLinux 7 Hybrid do not. Check the value; set it to 0 unless customers run rootless containers; apply the KernelCare livepatch on CloudLinux 10.

The CloudLinux kernel package is installed. Am I done?

Not until it is running. Reboot and confirm that uname -r prints a version at or above the one in the table for your line. On CloudLinux 8 ELS, 9 ELS and Ubuntu there is no fixed kernel yet, and the only protection is user.max_user_namespaces set to 0, which CloudLinux 10 and newer 8 and 9 installs already have by default. CageFS does not stop this exploit.

What is Fragnesia, and is it the same as the CloudLinux bug?

Fragnesia is CVE-2026-46300, a Linux kernel flaw that lets a local user change files they can only read and so take root; the kernel fix is from May. CISA says it is being chained with PHP2Shell. The CloudLinux bug, ZDI-CAN-33367, is a different flaw in the same part of the kernel, still without a CVE, and has its own fixed kernels and livepatches. A server needs both fixes.

Choose the response path

A web-user shell is now a route to root: choose the response path.

The server under the sites

Get both halves of the PHP2Shell chain checked and proven on every host.

Best when several servers need PHP and the kernel verified from the running process rather than the repository, the Core update window and the published addresses searched in the logs, and the post-exploitation look-back done once, with a written result per host.

One site, one worrying result

Get the finding classified and the site restored to a trusted state.

Best when an exploited booking, membership or form plugin left an administrator or a PHP file behind, a plugin with no fix was installed, or a cleaned site has come back, and you want every layer removed in one pass rather than one at a time.