Daily · Article 01 · 4 min read · Series 5 episode
- Security
CISA flags Linux flaw that can compound PHP attacks into root access
October 28 CISA catalog update · vendor guidance checked October 29 JST
Summary
CISA added Linux kernel flaw CVE-2026-46300 to its exploited-vulnerability catalog on October 28, describing a possible chain with existing PHP flaws. Operators need separate evidence for web PHP and the running server kernel.
A fixed PHP version does not tell you the state of the server’s operating system. On October 28, U.S. cybersecurity agency CISA added a Linux kernel flaw to its exploited-vulnerability catalog and described how it can compound existing PHP attacks. This is a change in the threat picture, rather than a newly released PHP fix.
Key facts
CISA added CVE-2026-46300 to its Known Exploited Vulnerabilities catalog, KEV, on October 28. The entry says it can be chained with PHP flaws CVE-2026-109618 and CVE-2026-109619 to implant webshells and execute commands as root. A webshell gives an attacker a command channel on a server; root is Linux’s administrator identity. The catalog was released at 04:00:04 JST on October 29, not the time of an individual attack. CISA source catalog
Hosting customers can ask for both web PHP remediation and an assessment of this kernel flaw, with evidence about the running kernel. This article has not inspected an individual customer’s server for compromise or kernel remediation.

1. What changes when an attack has two stages?
PHP handles requests for sites such as WordPress. Beneath it, the kernel is the operating system’s core, managing memory, files and permissions. Normal website work runs with the permissions assigned to its account. An attack that reaches the existing PHP flaws’ vulnerable conditions can first execute code with the PHP process’s permissions. CISA continues to urge immediate remediation of web-serving PHP. Earlier PHP alert
If an affected kernel and the necessary attack conditions remain, a second attack can gain higher privileges inside the server. Ubuntu’s security team describes this Linux flaw as local privilege escalation. Local means an attacker can already execute code on that server, rather than necessarily sitting at a home PC. Ubuntu impact and fixes
The figure separates the boundaries in CISA’s possible chain. It does not establish that every PHP site supports the chain or that a particular server was compromised.
%% Boundaries in the possible chain · CISA KEV and Ubuntu guidance
flowchart TD
A["External web request"] --> B["Vulnerable PHP conditions met"]
B --> C["Code executes as PHP account"]
C --> D["If affected kernel and<br/>additional attack conditions remain"]
D --> E["Root access becomes possible<br/>Broader file and settings damage"]The cat asks Q&A
- The researcher
Wouldn’t someone need a login password to start inside the server?
Pocket NotebookThe PHP route CISA warns about can begin with an unauthenticated external request. Code execution gained there can provide the starting point for a second attack. The kernel flaw alone does not give every internet visitor immediate root access.
2. Which protection was lost inside the kernel?
The official fix describes a shared-data marker getting lost when network-data fragments are combined. Later processing can miss that marker and change shared memory in place when it should first make a copy. That can unintentionally alter memory holding file contents. The fix carries the protection marker along when fragments move. Linux maintainer’s fix
Imagine shared originals with a note saying “copy before editing,” where the note disappears as papers are bundled. This explains the memory-handling principle, not an attack recipe. Gaining administrator privileges can extend damage to server files and settings that the website account was never allowed to change, widening the investigation beyond one website process.
| Layer to protect | Its job | Evidence needed |
|---|---|---|
| Web PHP | Handle external requests as website code | Fixes for the two PHP CVEs and active web workers |
| Linux kernel | Manage server-wide files, memory and permissions | CVE-2026-46300 impact and remediation in the running kernel |
| Earlier intrusion activity | Establish what happened before remediation | Security review of logs, files and alerts |
- Layer to protect
Web PHP
- Its job
- Handle external requests as website code
- Evidence needed
- Fixes for the two PHP CVEs and active web workers
- Layer to protect
Linux kernel
- Its job
- Manage server-wide files, memory and permissions
- Evidence needed
- CVE-2026-46300 impact and remediation in the running kernel
- Layer to protect
Earlier intrusion activity
- Its job
- Establish what happened before remediation
- Evidence needed
- Security review of logs, files and alerts
The cat asks Q&A
- The researcher
Does fixing PHP also resolve the second stage?
Pocket NotebookIt blocks that entry route but does not repair the kernel itself. Another entry route, or code already present on the server, needs separate attention. That is why both layers’ remediation evidence and historical records matter.
3. Check the server’s package, not a universal version number
This Linux issue was publicly documented in May. The new October development is KEV inclusion and the PHP-chain description. Distributions differ in configuration and fixed packages, so the impact cannot be assigned to every Linux server.
For example, Ubuntu lists its base linux package for 24.04 LTS as fixed in 6.8.0-124.124. Its notice lists many other kernel packages too; that number is not a threshold for every server. AWS says Amazon Linux and Bottlerocket do not ship the relevant espintcp module and are not affected by this CVE. That statement does not cover every other vulnerability. AWS status
| Question for the provider | Evidence to request |
|---|---|
| Is our distribution and kernel package affected by this CVE? | Product/package identity and vendor impact assessment |
| Is the fix active in the running environment? | Package build, running kernel, activation time and method |
| How far did the pre-fix compromise review reach? | Investigation window, log scope, preserved evidence and unknowns |
- Question for the provider
Is our distribution and kernel package affected by this CVE?
- Evidence to request
- Product/package identity and vendor impact assessment
- Question for the provider
Is the fix active in the running environment?
- Evidence to request
- Package build, running kernel, activation time and method
- Question for the provider
How far did the pre-fix compromise review reach?
- Evidence to request
- Investigation window, log scope, preserved evidence and unknowns
Installing a new package on disk and running a fixed kernel are separate states. The operator should choose the appropriate restart or live-patching approach and establish which fix is active. Customers should not restart a production server arbitrarily because of this article.
The cat asks Q&A
- The researcher
What should I ask if the provider only says “up to date”?
Pocket NotebookAsk for the CVE impact assessment and evidence that the running kernel includes the fix. A PHP version screen or a downloaded kernel file cannot answer both questions. Also request the period and records examined alongside any “nothing found” conclusion.
To close
Add kernel evidence to the PHP record
The external entry route and the server’s internal privilege boundary now need to be considered together. Add the kernel impact assessment and active-fix evidence to the timing records in the earlier PHP exploitation story to make the provider’s next checks concrete.
Sources
- CISA source catalogcisa.gov
- Earlier PHP alertcisa.gov
- Ubuntu impact and fixesubuntu.com
- Linux maintainer’s fixgithub.com
- AWS statusaws.amazon.com