Vulnerabilities > Use After Free
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-01-02 | CVE-2023-49135 | Use After Free vulnerability in Openatom Openharmony in OpenHarmony v3.2.2 and prior versions allow a local attacker cause multimedia player crash through modify a released pointer. | 5.5 |
| 2024-01-02 | CVE-2023-49142 | Use After Free vulnerability in Openatom Openharmony in OpenHarmony v3.2.2 and prior versions allow a local attacker cause multimedia audio crash through modify a released pointer. | 3.3 |
| 2024-01-02 | CVE-2023-33094 | Use After Free vulnerability in Qualcomm products Memory corruption while running VK synchronization with KASAN enabled. | 7.8 |
| 2024-01-02 | CVE-2023-33108 | Use After Free vulnerability in Qualcomm products Memory corruption in Graphics Driver when destroying a context with KGSL_GPU_AUX_COMMAND_TIMELINE objects queued. | 7.8 |
| 2024-01-02 | CVE-2023-33114 | Use After Free vulnerability in Qualcomm products Memory corruption while running NPU, when NETWORK_UNLOAD and (NETWORK_UNLOAD or NETWORK_EXECUTE_V2) commands are submitted at the same time. | 7.8 |
| 2024-01-02 | CVE-2023-43514 | Use After Free vulnerability in Qualcomm products Memory corruption while invoking IOCTLs calls from user space for internal mem MAP and internal mem UNMAP. | 7.8 |
| 2023-12-31 | CVE-2023-52266 | Use After Free vulnerability in Hongliuliao Ehttp 1.0.6 ehttp 1.0.6 before 17405b9 has an epoll_socket.cpp read_func use-after-free. | 7.5 |
| 2023-12-19 | CVE-2023-6859 | Use After Free vulnerability in multiple products A use-after-free condition affected TLS socket creation when under memory pressure. | 8.8 |
| 2023-12-19 | CVE-2023-6862 | Use After Free vulnerability in multiple products A use-after-free was identified in the `nsDNSService::Init`. | 8.8 |
| 2023-12-19 | CVE-2023-6932 | Use After Free vulnerability in Linux Kernel A use-after-free vulnerability in the Linux kernel's ipv4: igmp component can be exploited to achieve local privilege escalation. A race condition can be exploited to cause a timer be mistakenly registered on a RCU read locked object which is freed by another thread. We recommend upgrading past commit e2b706c691905fe78468c361aaabc719d0a496f1. | 7.0 |