Use after free in task scheduling in Google Chrome prior to 81.0.4044.129 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
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.
| Link | Tags |
|---|---|
| https://security.gentoo.org/glsa/202005-13 | third party advisory vendor advisory |
| https://chromereleases.googleblog.com/2020/04/stable-channel-update-for-desktop_27.html | release notes vendor advisory |
| https://crbug.com/1064891 | vendor advisory permissions required |
| https://www.debian.org/security/2020/dsa-4714 | third party advisory vendor advisory |