uri: Fix lexbor memory management in uri_parser_whatwg.c #19591
+36
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Calling
lexbor_mraw_clean()
after a specific number of parses will destroy the data for any liveUri\WhatWg\Url
objects, effectively resulting in a use-after-free.Fix the issue by removing the periodic
lexbor_mraw_clean()
call. Instead we implementphp_uri_parser_whatwg_free()
. This also requires to move the destruction of the lexbor structures from RSHUTDOWN to POST_ZEND_DEACTIVATE to prevent a use-after-free inphp_uri_parser_whatwg_free()
since otherwise the mraw would already have been destroyed.