CISA added CVE-2026-46300, the Linux kernel flaw known as Fragnesia, to its Known Exploited Vulnerabilities catalog on October 28. Its catalog entry says attackers can chain it with CVE-2026-109618 and CVE-2026-109619, the PHP2Shell vulnerabilities, to implant webshells and run commands as root.
Evidence status: CISA-listed known exploitation, plus a separate vendor-reported incident reconstruction added below. CISA’s catalog supplies no victim count or named campaign. Ransomware use is marked Unknown.
This is a fresh exploitation assessment of an older vulnerability. Greg Kroah-Hartman identified the CVE publicly on May 13; the Linux-maintained CVE record was published on May 23. October 28 is the catalog-addition date, not the disclosure date or the first day of attacks.
The kernel flaw needs local access
Fragnesia lets an attacker modify page-cache data, the in-memory copies of file contents, through a bug in network-buffer handling. The kernel loses a marker indicating that a buffer contains shared file-backed memory. Later processing can write into memory that should have remained protected.
Linux’s CVE assessment requires local access and low privileges. Its described path depends on relevant networking features and namespace permissions, which can let an unprivileged process configure a separate network environment. An ordinary incoming internet packet alone does not establish this attack path.
A remotely compromised PHP worker can supply the local foothold for a subsequent kernel attack. Those are separate security boundaries: the PHP runtime controls initial web execution; the host kernel controls escalation beyond the worker’s account.
The existing PHP2Shell incident page retains the runtime fixes and evolving attack evidence. This kernel check supplements that guidance. A container-image rebuild alone does not replace the host’s kernel.
Verify the distribution fix and the kernel actually running
The Linux-maintained record lists these first unaffected upstream stable versions for the respective branches:
| Upstream branch | First listed fixed version |
|---|---|
| 5.10 | 5.10.257 |
| 5.15 | 5.15.208 |
| 6.1 | 6.1.174 |
| 6.6 | 6.6.141 |
| 6.12 | 6.12.91 |
| 6.18 | 6.18.33 |
| 7.0 | 7.0.10 |
The record also identifies 7.1 as containing the original fix. These are branch-specific baselines, not instructions to downgrade a newer supported kernel.
Distribution package versions can differ because vendors backport fixes. The Debian Security Tracker, for example, lists 6.12.90-1 for trixie and 6.1.174-1 for bookworm as fixed source-package versions. Its trixie baseline differs from the upstream table. Match the distribution and package advisory rather than applying an upstream number comparison blindly.
For operators:
- Confirm coverage for this exact CVE in the host or appliance vendor’s supported update. Check managed-host responsibilities separately from application updates.
- Ensure the repaired kernel is active. Installing a package while continuing to run the old kernel leaves a different state from completing the required reboot or supported live-patch procedure.
- Patch exposed PHP runtimes too. A kernel repair does not close the remote PHP entry point; a PHP repair does not establish kernel coverage.
- Preserve evidence and investigate previous access. Review unexpected web-worker child processes, privilege changes and persistent access. Successful patch installation cannot establish that earlier activity was harmless.
CISA’s machine-readable catalog sets forensic triage to Yes and lists October 31 as the due date. It points operators to its risk-based directive and triage guidance. The directive’s compulsory scope is federal civilian executive-branch systems, not a universal private-sector deadline.
Update · October 29, 2026, 12:50 EDT
Dream reports a firewall-to-identity compromise
Dream Research’s October 26 report, reviewed here October 29, adds a claimed incident reconstruction beyond CISA’s brief catalog entry. Dream says recovered exploitation logs, target lists and scripts show 25 servers compromised through PHP2Shell and Fragnesia.
The report distinguishes 24 externally targeted firewalls from a subsequent internal management-server compromise. It associates three affected servers with a US government-affiliated environment. These are Dream’s artifact-based findings, not a global compromise estimate or a victim count independently confirmed by CISA.
Dream describes attackers obtaining a network tunnel, device keys and a service-account password for LDAP, a directory-access protocol, then enumerating users and groups. It explicitly cannot determine whether password spraying, backdoor-account creation or signing-key extraction for SAML, a federated sign-in standard, succeeded. Those unknown outcomes should not become confirmed domain takeover.
The vendor and affected firmware versions remain withheld. Operators need their appliance vendor’s supported repair guidance; an upstream PHP or kernel version alone cannot identify every affected appliance. Keep management interfaces restricted, investigate access beyond the appliance, and assess exposed device and directory credentials during recovery.
Dream infers possible AI assistance from installed tools and code characteristics. It acknowledges having no direct evidence that AI wrote the exploit or follow-on scripts. Its Chinese-nexus attribution is an assessment, not a demonstrated identity.
What the thread adds
In the ranked Hacker News discussion, codegeek asks, “Is this attack possible even after the PHP patches OR these servers just didn’t patch ?” jdiff replies that the firewall software runs an unpatched version.
That reply supplies no vendor release matrix. The report’s withheld firmware scope leaves the practical question with the appliance vendor: which supported update fixes both components? Installing a runtime patch elsewhere does not establish appliance coverage.
From a 66-comment thread, in HN’s own order.
Caveat: Dream sells cyberdefense and automated research products and used its own product for this investigation. Its incident count, attribution and continuing-access assessments remain source-reported.