Filtered by CWE-416
Total 6420 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2024-42326 1 Zabbix 1 Zabbix 2025-10-08 4.4 Medium
There was discovered a use after free bug in browser.c in the es_browser_get_variant function
CVE-2024-42331 1 Zabbix 1 Zabbix 2025-10-08 3.3 Low
In the src/libs/zbxembed/browser.c file, the es_browser_ctor method retrieves a heap pointer from the Duktape JavaScript engine. This heap pointer is subsequently utilized by the browser_push_error method in the src/libs/zbxembed/browser_error.c file. A use-after-free bug can occur at this stage if the wd->browser heap pointer is freed by garbage collection.
CVE-2025-7425 1 Redhat 12 Discovery, Enterprise Linux, Insights Proxy and 9 more 2025-10-08 7.8 High
A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.
CVE-2025-49844 1 Redis 1 Redis 2025-10-08 10 Critical
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
CVE-2025-59734 1 Ffmpeg 1 Ffmpeg 2025-10-08 N/A
It is possible to cause an use-after-free write in SANM decoding with a carefully crafted animation using subversion <2. When a STOR chunk is present, a subsequent FOBJ chunk will be saved in ctx->stored_frame. Stored frames can later be referenced by FTCH chunks. For files using subversion < 2, the undecoded frame is stored, and decoded again when the FTCH chunks are parsed. However, in process_frame_obj if the frame has an invalid size, there’s an early return, with a value of 0.  This causes the code in decode_frame to still store the raw frame buffer into ctx->stored_frame. Leaving ctx->has_dimensions set to false. A subsequent chunk with type FTCH would call process_ftch and decode that frame obj again, adding to the top/left values and calling process_frame_obj again. Given that we never set ctx->have_dimensions before, this time we set the dimensions, calling init_buffers, which can reallocate the buffer in ctx->stored_frame, freeing the previous one. However, the GetByteContext object gb still holds a reference to the old buffer. Finally, when the code tries to decode the frame, codecs that accept a GetByteContext as a parameter will trigger a use-after-free read when using gb. GetByteContext is only used for reading bytes, so at most one could read invalid data. There are no heap allocations between the free and when the object is accessed. However, upon returning to process_ftch, the code restores the original values for top/left in stored_frame, writing 4 bytes to the freed data at offset 6, potentially corrupting the allocator’s metadata. This issue can be triggered just by probing whether a file has the sanm format. We recommend upgrading to version 8.0 or beyond.
CVE-2024-46716 1 Linux 1 Linux Kernel 2025-10-07 5.5 Medium
In the Linux kernel, the following vulnerability has been resolved: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor Remove list_del call in msgdma_chan_desc_cleanup, this should be the role of msgdma_free_descriptor. In consequence replace list_add_tail with list_move_tail in msgdma_free_descriptor. This fixes the path: msgdma_free_chan_resources -> msgdma_free_descriptors -> msgdma_free_desc_list -> msgdma_free_descriptor which does not correctly free the descriptors as first nodes were not removed from the list.
CVE-2024-42112 1 Linux 1 Linux Kernel 2025-10-07 7.8 High
In the Linux kernel, the following vulnerability has been resolved: net: txgbe: free isb resources at the right time When using MSI/INTx interrupt, the shared interrupts are still being handled in the device remove routine, before free IRQs. So isb memory is still read after it is freed. Thus move wx_free_isb_resources() from txgbe_close() to txgbe_remove(). And fix the improper isb free action in txgbe_open() error handling path.
CVE-2022-49043 2 Redhat, Xmlsoft 6 Discovery, Enterprise Linux, Openshift and 3 more 2025-10-07 8.1 High
xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
CVE-2025-61692 1 Keyence 1 Vt Studio 2025-10-07 7.8 High
VT STUDIO versions 8.53 and prior contain a use after free vulnerability. If the product uses a specially crafted file, arbitrary code may be executed on the affected product.
CVE-2010-3962 1 Microsoft 6 Internet Explorer, Windows 7, Windows Server 2003 and 3 more 2025-10-07 8.1 High
Use-after-free vulnerability in Microsoft Internet Explorer 6, 7, and 8 allows remote attackers to execute arbitrary code via vectors related to Cascading Style Sheets (CSS) token sequences and the clip attribute, aka an "invalid flag reference" issue or "Uninitialized Memory Corruption Vulnerability," as exploited in the wild in November 2010.
CVE-2024-45544 1 Qualcomm 88 C-v2x 9150, C-v2x 9150 Firmware, Fastconnect 6800 and 85 more 2025-10-06 6.6 Medium
Memory corruption while processing IOCTL calls to add route entry in the HW.
CVE-2024-45540 1 Qualcomm 136 C-v2x 9150, C-v2x 9150 Firmware, Fastconnect 6200 and 133 more 2025-10-06 6.6 Medium
Memory corruption while invoking IOCTL map buffer request from userspace.
CVE-2024-43066 1 Qualcomm 196 Csrb31024, Csrb31024 Firmware, Fastconnect 6200 and 193 more 2025-10-06 7.8 High
Memory corruption while handling file descriptor during listener registration/de-registration.
CVE-2024-49848 1 Qualcomm 294 Ar8035, Ar8035 Firmware, Fastconnect 6200 and 291 more 2025-10-06 6.7 Medium
Memory corruption while processing multiple IOCTL calls from HLOS to DSP.
CVE-2025-9385 2 Appneta, Broadcom 2 Tcpreplay, Tcpreplay 2025-10-06 5.3 Medium
A flaw has been found in appneta tcpreplay up to 4.5.1. The affected element is the function fix_ipv6_checksums of the file edit_packet.c of the component tcprewrite. This manipulation causes use after free. The attack is restricted to local execution. The exploit has been published and may be used. Upgrading to version 4.5.2-beta3 is sufficient to fix this issue. It is advisable to upgrade the affected component.
CVE-2025-9386 2 Appneta, Broadcom 2 Tcpreplay, Tcpreplay 2025-10-06 5.3 Medium
A vulnerability has been found in appneta tcpreplay up to 4.5.1. The impacted element is the function get_l2len_protocol of the file get.c of the component tcprewrite. Such manipulation leads to use after free. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. Upgrading to version 4.5.2-beta3 is sufficient to resolve this issue. You should upgrade the affected component.
CVE-2024-40989 2 Linux, Redhat 3 Linux Kernel, Enterprise Linux, Rhel Eus 2025-10-06 7.8 High
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Disassociate vcpus from redistributor region on teardown When tearing down a redistributor region, make sure we don't have any dangling pointer to that region stored in a vcpu.
CVE-2025-10729 1 Qt 1 Qt 2025-10-06 8.6 High
The module will parse a <pattern> node which is not a child of a structural node. The node will be deleted after creation but might be accessed later leading to a use after free.
CVE-2024-23365 1 Qualcomm 96 Fastconnect 7800, Fastconnect 7800 Firmware, Qam8255p and 93 more 2025-10-03 8.4 High
Memory corruption while releasing shared resources in MinkSocket listener thread.
CVE-2024-38629 2 Linux, Redhat 2 Linux Kernel, Enterprise Linux 2025-10-03 7.8 High
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Avoid unnecessary destruction of file_ida file_ida is allocated during cdev open and is freed accordingly during cdev release. This sequence is guaranteed by driver file operations. Therefore, there is no need to destroy an already empty file_ida when the WQ cdev is removed. Worse, ida_free() in cdev release may happen after destruction of file_ida per WQ cdev. This can lead to accessing an id in file_ida after it has been destroyed, resulting in a kernel panic. Remove ida_destroy(&file_ida) to address these issues.