Whether it's exactly the same issue or not, the point remains: a double-free in and of itself doesn't establish a critical CVE (or even a high one). There's a known double-free in that GitHub issue, if there's a second independent one, it shouldn't necessarily cause any more concern than the first one.

▲

athrowaway3z 3 hours ago | parent [-]

Its nothing

https://www.reddit.com/r/PHP/comments/1xbyxd2/new_php_cve_di...

	▲	akersten 3 hours ago \| parent [-]
		Color me unconvinced that the dev team that sat on the 2024 security audit leading to today's CVE successfully explored the ramifications of a new memory bug in an hour