Skip to content

TSRM: roll back id_count when the resource type table cannot grow - #23595

Open
iliaal wants to merge 1 commit into
php:masterfrom
iliaal:promote/tsrm-id-count-rollback
Open

TSRM: roll back id_count when the resource type table cannot grow#23595
iliaal wants to merge 1 commit into
php:masterfrom
iliaal:promote/tsrm-id-count-rollback

Conversation

@iliaal

@iliaal iliaal commented Sep 6, 2026

Copy link
Copy Markdown
Member

ts_allocate_id(), ts_allocate_fast_id_at() and ts_allocate_tls_id() each do id_count++ before growing resource_types_table. If the realloc fails they return 0 with id_count still counting the new slot, so resource_types_table_size < id_count from then on and allocate_new_resource() walks j < id_count over an entry that was never initialized.

This targets master rather than a stable branch because it is unreachable without an allocation failure, and TSRM.c has diverged. The PHP-8.4 shape has only two increment sites and puts one of them in ts_allocate_fast_id(), which on master no longer increments at all, so the same diff would be wrong there. No test: the branch needs a failing realloc during ZTS startup, which has no userland surface. Verified against a --enable-zts build.

ts_allocate_id(), ts_allocate_fast_id_at() and ts_allocate_tls_id()
increment id_count before growing resource_types_table. When the
realloc fails they return 0 with id_count still counting the new slot,
so allocate_new_resource() later walks j < id_count and reads an entry
that was never initialized. Roll id_count back on those three paths.

Closes phpGH-23595
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant