Vulnerabilities > Use After Free
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-06-12 | CVE-2023-34494 | Use After Free vulnerability in Emqx Nanomq 0.16.5 NanoMQ 0.16.5 is vulnerable to heap-use-after-free in the nano_ctx_send function of nmq_mqtt.c. | 7.5 |
2023-06-09 | CVE-2023-3141 | Use After Free vulnerability in multiple products A use-after-free flaw was found in r592_remove in drivers/memstick/host/r592.c in media access in the Linux Kernel. | 7.1 |
2023-06-08 | CVE-2023-33657 | Use After Free vulnerability in Emqx Nanomq 0.17.2 A use-after-free vulnerability exists in NanoMQ 0.17.2. | 7.5 |
2023-06-07 | CVE-2023-33595 | Use After Free vulnerability in Python 3.12.0 CPython v3.12.0 alpha 7 was discovered to contain a heap use-after-free via the function ascii_decode at /Objects/unicodeobject.c. | 5.5 |
2023-06-06 | CVE-2023-20744 | Use After Free vulnerability in multiple products In vcu, there is a possible use after free due to a logic error. | 6.7 |
2023-06-06 | CVE-2022-33263 | Use After Free vulnerability in Qualcomm products Memory corruption due to use after free in Core when multiple DCI clients register and deregister. | 7.8 |
2023-06-05 | CVE-2023-3111 | Use After Free vulnerability in multiple products A use after free vulnerability was found in prepare_to_relocate in fs/btrfs/relocation.c in btrfs in the Linux Kernel. | 7.8 |
2023-06-02 | CVE-2023-25735 | Use After Free vulnerability in Mozilla Firefox ESR Cross-compartment wrappers wrapping a scripted proxy could have caused objects from other compartments to be stored in the main compartment resulting in a use-after-free after unwrapping the proxy. | 8.8 |
2023-06-02 | CVE-2023-25739 | Use After Free vulnerability in Mozilla Firefox ESR Module load requests that failed were not being checked as to whether or not they were cancelled causing a use-after-free in <code>ScriptLoadContext</code>. | 8.8 |
2023-06-02 | CVE-2023-29536 | Use After Free vulnerability in Mozilla products An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruption, or a potentially exploitable crash. | 8.8 |