Koffei

CVE-2026-46300

🔴 High In CISA KEV

Linux kernel — net/core/skbuff.c with the ESP input path. A local unprivileged user suffices: unshare -Urn for CAP_NET_ADMIN, an espintcp SA with a known AES-GCM key, no race needed. The public PoC rewrites /usr/bin/su in the page cache, so the on-disk file never changes and file-integrity monitoring will not see it · Introduced in 3.9 ; fixed in 5.10.257 / 5.15.208 / 6.1.174 / 6.6.141 / 6.12.91 / 6.18.33 / 7.0.10 and mainline 7.1 ; 36 Red Hat errata (RHSA-2026:19540 onward, RHBZ#2477015) ; Siemens affected: SSA-082556 and SSA-019113

CVSS (Koffei note)
7.8
CVSS (v3.1, CVE List)
7.8
EPSS (2026-11-18)
16.130%
96.99th percentile
CISA KEV
2026-10-28
due 2026-10-31

Exploitation

Yes — CISA KEV since 28/10/2026, federal remediation due 31/10/2026 (SSVC exploitation active, though its timestamp of 14/05/2026 looks like a vulnrichment backfill, since a vendor FAQ of that same date reported no exploitation). It is being used as the privilege-escalation half of a chain: the php2shell pair CVE-2026-109618 / CVE-2026-109619 for the web shell, then Fragnesia for root. One vendor reports that chain rooting 25 servers across the US, Japan, Taiwan and South Korea, three of them in a US government-affiliated environment, with rooting events timed 23/10 18:14 UTC and 24/10 10:09 and 11:35 UTC, observed 25/10/2026. Attribution is only "suspected China-nexus" with no group named, and it stays unnamed here. Public PoC since disclosure. Credit: William Bowling, V12 Security, 13/05/2026 Update 30/10/2026: the 25-server claim is now corroborated — Unit 42 states it independently verified the same attacker tooling and confirmed the reported results. The victim detail firms up too: credential extraction and Active Directory enumeration on the three servers in the US-government-affiliated environment. New target class: the chain is being run against internet-exposed PAN-OS management interfaces, and Palo Alto confirms active exploitation there, which the original report had not named. Two exposure figures circulate and should not be merged: Unit 42 puts the impacted share at about 0.02% of the installed base with internet-facing management interfaces, while Palo Alto is reported as saying under 0.01% of the installed base even has such an interface. Still no named actor and no named malware.

Timeline

  1. 23/05/2026CVE record published (CVE List)
  2. 28/10/2026Added to the CISA KEV catalogue
  3. 29/10/2026PHP2Shell exploitation expands — Fragnesia kernel flaw chained to root firewalls, PAN-OS also targeted
  4. 30/10/2026PAN-OS "PHP2Shell" chain exploited by China-nexus actor to root 25 servers
  5. 30/10/2026Suspected China-nexus actor roots 25 PAN-OS servers
  6. 31/10/2026CISA deadline for US federal agencies

Relationships

CVE-2026-109619CVE-2026-109619CVE-2026-109618CVE-2026-109618Linux (kernel)Linux (kernel)PHP2Shell firewall clusterPHP2Shell firewall clusterCVE-2026-46300CVE-2026-46300

exploits suspected named in the same story vendor · Select a box to open its page · All relationships

Risk

7.8 High (v3.1, Linux CNA and Red Hat, identical vectors) — AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, EPSS 15.719% (96.85th percentile) — Red Hat adds severity "Important". CWE disagreement, and only two suppliers assign one: the Linux CNA assigns none, CISA-ADP says CWE-456, Red Hat says CWE-123. Nicknamed "Fragnesia" (skb_try_coalesce() loses the SKBFL_SHARED_FRAG marker, so ESP input skips skb_cow_data() and decrypts in place over page-cache fragments, giving a 192-byte arbitrary write into the shared page cache)

Fix

Yes — the kernel versions above. Correction of an earlier entry in this report: the kernel update IS the remediation. An earlier version of this row implied that blacklisting modules was the fix, which was misleading. Ubuntu publishes fixed kernel packages for every affected release (26.04 LTS 7.0.0-22.22, 25.10 6.17.0-35.35, 24.04 LTS 6.8.0-124.124, 22.04 LTS 5.15.0-181.191, plus the HWE and cloud flavours) and advises against cherry-picking the patch. What does not cover this is the pre-existing Dirty Frag patch set, and the esp4 / esp6 / rxrpc module blacklist is a stopgap for hosts that cannot be updated, not the remediation. Red Hat has shipped 30+ errata through RHSA-2026:34098

Official description

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost. That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skb_has_shared_frag() before deciding whether an uncloned nonlinear skb can skip skb_cow_data(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skb_has_shared_frag() as false and decrypt in place over page-cache backed frags. Propagate SKBFL_SHARED_FRAG when skb_try_coalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to's linear data rather than transferring frag descriptors.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H