PHP patches seven critical flaws that can lead to code execution
Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; several bugs need specific application conditions.
PHP-FPM epoll use-after-free local privilege escalation
A use-after-free in PHP-FPM occurs when catch_workers_output is enabled and the epoll backend is in use. The master can close a worker output pipe without dropping the event, then free the worker record while the registration is still live; a later event uses that freed pointer. A local attacker who can run PHP in an FPM worker can crash the master or run code with its privileges, often root. The option is off by default but on in official PHP-FPM Docker images. PHP 8.2.7 through builds before 8.2.36, and 8.3, 8.4, and 8.5 before the listed fixes, are affected.
What to do: Upgrade PHP to 8.2.36, 8.3.37, 8.4.28, or 8.5.13 as applicable.
| Product | Affected | Fixed in |
|---|---|---|
| PHP | 8.2.7 before 8.2.36; 8.3.* before 8.3.37; 8.4.* before 8.4.28; 8.5.* before 8.5.13 | 8.2.36, 8.3.37, 8.4.28, 8.5.13 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
PHP-FPM epoll use-after-free can lead to local privilege escalation. When catch_workers_output is enabled and the epoll event backend is used, the PHP-FPM master can close a worker's output pipe in fpm_child_close() without removing the associated event, and the delayed cleanup can free the worker record while its epoll registration is still active. A later event is then dispatched through a pointer into freed memory. A local attacker who can execute PHP code in an FPM worker can crash the master or execute code with its privileges, commonly root. catch_workers_output is disabled by default but enabled in the official PHP-FPM Docker images. This issue affects PHP versions from 8.1.20 through 8.1.34, from 8.2.7 before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; several bugs need specific application conditions.
The November 19 releases fix flaws that PHP says need non-default or uncommon setups, including session-handling remote code execution.
Fixed releases are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36; two issues can reach ordinary WordPress hosts.
The top issue is a PHP-FPM request-smuggling flaw scored 9.2 that needs reused backend connections.
Today 915 readers · 1K views · 86 reads · all time 211K views