This type of flaw occurs when memory that has been freed is still used by the program
Am I understanding correctly that a memory leak has been fixed? Though it says that it relates specifically to “Animation timelines”, so does it mean that the fix only affects the (small?) portion of the memory that’s been used by that feature? Or any memory that should get freed but wasn’t previously?
Based on your quite, this is a use-after-free, meaning that despite Firefox marking the memory region as free to be reallocated, it continues to use the memory. This is dangerous as an attacker may be able to allocate in that region, leetting them change the old structure’s values.
Am I understanding correctly that a memory leak has been fixed? Though it says that it relates specifically to “Animation timelines”, so does it mean that the fix only affects the (small?) portion of the memory that’s been used by that feature? Or any memory that should get freed but wasn’t previously?
Based on your quite, this is a use-after-free, meaning that despite Firefox marking the memory region as free to be reallocated, it continues to use the memory. This is dangerous as an attacker may be able to allocate in that region, leetting them change the old structure’s values.