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 workers 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.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | php8.4-0:8.4.28-1.el10_3 | * |
| Red Hat Enterprise Linux 10.2 Extended Update Support | RedHat | php8.4-0:8.4.28-1.el10_2 | * |
| Red Hat Enterprise Linux 8 | RedHat | php:7.4-8100020261119125714.f7998665 | * |
| Red Hat Enterprise Linux 9.8 Extended Update Support | RedHat | php:8.3-9080020261120133305.9 | * |
| Red Hat Enterprise Linux 9.8 Extended Update Support | RedHat | php:8.2-9080020261120141350.9 | * |
| Php5 | Ubuntu | esm-infra-legacy/trusty | * |
| Php7.0 | Ubuntu | esm-infra-legacy/xenial | * |
| Php7.2 | Ubuntu | esm-infra/bionic | * |
| Php7.4 | Ubuntu | esm-infra/focal | * |
| Php8.1 | Ubuntu | jammy | * |
| Php8.3 | Ubuntu | noble | * |
| Php8.5 | Ubuntu | devel | * |
| Php8.5 | Ubuntu | resolute | * |
| Php8.5 | Ubuntu | stonking | * |