Three Days to Patch "Fragnesia": CISA KEVs the Linux Kernel Flaw That Chains PHP2Shell Access Into Root

Three Days to Patch "Fragnesia": CISA KEVs the Linux Kernel Flaw That Chains PHP2Shell Access Into Root

Three Days to Patch "Fragnesia": CISA KEVs the Linux Kernel Flaw That Chains PHP2Shell Access Into Root

CISA added CVE-2026-46300 — nicknamed Fragnesia — to its Known Exploited Vulnerabilities catalog on October 28 with one of the shortest deadlines in the catalog: federal agencies must remediate by October 31. The flaw is a high-severity local privilege escalation (Red Hat rates it 7.8) in the kernel's network stack, specifically the skb_try_coalesce() function in net/skbuff. When paged fragments transfer between socket buffers during TCP receive coalescing, the SKBFL_SHARED_FRAG marker is lost, and the ESP (Encapsulating Security Payload) input handler then performs in-place decryption over page-cache-backed memory — corrupting shared kernel data. The practical result: an unprivileged local attacker can modify read-only file contents in the kernel page cache and take deterministic root, with no race conditions or timing games required.

The bug belongs to the same vulnerability class as Dirty Frag, alongside the earlier Copy Fail family. It was first disclosed on May 13, 2026 through Red Hat's CVE tracker and the oss-security mailing list, with NVD publication on May 23; William Bowling of the V12 security team is credited with the find and published a proof-of-concept, and Wiz's technical analysis maps the full mechanics across the XFRM ESP-in-TCP subsystem. Affected versions span kernel 3.9 through 7.1-rc4 — which is to say, essentially every Linux server not rebuilt on a post-May stable branch. CISA's KEV entry links the stable git.kernel.org fix commits directly.

Why the three-day fuse? Because Fragnesia is the second half of a live attack chain. CISA's alert notes that the flaw can be chained with the two PHP engine bugs behind PHP2Shell (CVE-2026-109618 and CVE-2026-109619) — pre-auth remote code execution on internet-facing PHP applications — to deploy webshells and then escalate. Dream Security analysts reported that exactly this pairing has already been used to breach more than two dozen servers, including three belonging to a U.S. government-affiliated organization, describing "a complete attack operation that included a custom weaponization of the PHP2Shell exploit chain paired with the Fragnesia kernel privilege escalation (CVE-2026-46300), target lists, exploitation logs, and approximately 40 custom post-exploitation scripts." CISA could not share more about ongoing chaining when asked; the KEV entry's exploitation date speaks for itself.

The composite picture is the story: a PHP bug lets the attacker in as an unprivileged web user, and the kernel bug quietly converts that foothold into root on the host. Neither CVE looks catastrophic alone — one is a web-tier RCE in a scripting language, the other a local privilege escalation — but chained they turn an exposed CMS or legacy PHP app into full server ownership, the same pairing logic we saw Plex2Shell exploit against media servers and PHP2Shell itself across the web at large.

What Should You Do?

  1. Patch to a fixed kernel now — any stable branch carrying the May 2026 fix commits satisfies the October 31 KEV deadline; verify hosts and containers actually run the patched kernel after reboot, not just have it staged.
  2. Treat every internet-facing PHP host as possibly exploited — if you run unpatched PHP (< 8.5.12-1, 8.4.27-1, 8.3.36-1, 8.2.35-1) on unpatched kernels, assume the chain was available to attackers and hunt for webshells and unexpected root processes.
  3. Contain the escalation path — block or restrict XFRM/ESP-in-TCP handling where it is not required on servers, and run application workers under non-root users so a page-cache corruption buys less by default.
  4. Check container and VM images — the affected range covers kernels released before May 13, 2026; anything built on older bases inherits the exposure the moment it runs privileged workloads.

The WAF Angle

Fragnesia is the clearest recent example of why "what does the WAF see" is the wrong boundary for scoping an incident. The web edge can block or flag the PHP2Shell request pattern — the pre-auth RCE half of the chain — and a WAF with strong request inspection is genuinely valuable there, as it was when Collabora's proxy.php RCE hit the KEV list earlier this month. But the escalation half happens entirely inside the kernel, below any HTTP-layer control, and Dream's roughly 40 post-exploitation scripts show what a rooted host is worth to an operator building reusable tooling. Defensively that means pairing layers: request-side blocking for the entry bug, kernel patching for the escalation bug, and host-level detections (unexpected root, page-cache anomalies, webshells in web roots) that assume the web tier can fail — the posture CISA implicitly mandated with a due date three days out.

Sources