Vulnerabilities > Use After Free
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-06-11 | CVE-2024-5831 | Use After Free vulnerability in multiple products Use after free in Dawn in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | 8.8 |
2024-06-11 | CVE-2024-5832 | Use After Free vulnerability in multiple products Use after free in Dawn in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | 8.8 |
2024-06-11 | CVE-2024-5841 | Use After Free vulnerability in multiple products Use after free in V8 in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | 8.8 |
2024-06-11 | CVE-2024-5842 | Use After Free vulnerability in multiple products Use after free in Browser UI in Google Chrome prior to 126.0.6478.54 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform an out of bounds memory read via a crafted HTML page. | 8.8 |
2024-06-11 | CVE-2024-5845 | Use After Free vulnerability in multiple products Use after free in Audio in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. | 8.8 |
2024-06-11 | CVE-2024-5846 | Use After Free vulnerability in multiple products Use after free in PDFium in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. | 8.8 |
2024-06-11 | CVE-2024-5847 | Use After Free vulnerability in multiple products Use after free in PDFium in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. | 8.8 |
2024-06-11 | CVE-2024-5694 | Use After Free vulnerability in Mozilla Firefox An attacker could have caused a use-after-free in the JavaScript engine to read memory in the JavaScript string section of the heap. | 7.5 |
2024-06-10 | CVE-2024-36971 | Use After Free vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets. | 7.8 |
2024-06-07 | CVE-2024-32503 | Use After Free vulnerability in Samsung products An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 850, Exynos 1080, Exynos 2100, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, Exynos W930. | 7.8 |