Vulnerabilities > Use After Free
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-01-30 | CVE-2023-0240 | Use After Free vulnerability in Linux Kernel There is a logic error in io_uring's implementation which can be used to trigger a use-after-free vulnerability leading to privilege escalation. | 7.8 |
2023-01-30 | CVE-2023-0266 | Use After Free vulnerability in Linux Kernel A use after free vulnerability exists in the ALSA PCM package in the Linux Kernel. | 7.8 |
2023-01-30 | CVE-2023-0471 | Use after free in WebTransport in Google Chrome prior to 109.0.5414.119 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | 8.8 |
2023-01-30 | CVE-2023-0472 | Use after free in WebRTC in Google Chrome prior to 109.0.5414.119 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | 8.8 |
2023-01-30 | CVE-2023-0474 | Use after free in GuestView in Google Chrome prior to 109.0.5414.119 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a Chrome web app. | 8.8 |
2023-01-26 | CVE-2023-0468 | Use After Free vulnerability in Linux Kernel A use-after-free flaw was found in io_uring/poll.c in io_poll_check_events in the io_uring subcomponent in the Linux Kernel due to a race condition of poll_refs. | 4.7 |
2023-01-26 | CVE-2023-0469 | Use After Free vulnerability in Linux Kernel A use-after-free flaw was found in io_uring/filetable.c in io_install_fixed_file in the io_uring subcomponent in the Linux Kernel during call cleanup. | 5.5 |
2023-01-26 | CVE-2023-20920 | Use After Free vulnerability in Google Android In queue of UsbRequest.java, there is a possible way to corrupt memory due to a use after free. | 7.8 |
2023-01-26 | CVE-2023-20925 | Use After Free vulnerability in Google Android In setUclampMinLocked of PowerSessionManager.cpp, there is a possible way to corrupt memory due to a use after free. | 7.8 |
2023-01-26 | CVE-2022-3094 | Use After Free vulnerability in ISC Bind Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. | 7.5 |