Use After Free in DSP Service

Memory Corruption when executing system service routines due to improper handling of user input buffers.

Use After Free in DSP Service

Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations.

Use After Free in DSP Service

Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization.

Use After Free in Graphics

Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms.

Use After Free in Windows WLAN Host

Memory Corruption when processing concurrent DMA buffer allocation and deallocation commands without proper synchronization.

kernel: Possible use-after-free since the two fdget() during vhost_net_set_backend()

A use-after-free flaw was found in vhost_net_set_backend in drivers/vhost/net.c in virtio network subcomponent in the Linux kernel due to a double fget. This flaw could allow a local attacker to crash the system, and could even lead to a kernel information leak problem.

Use After Free in vim/vim

Use After Free in GitHub repository vim/vim prior to 8.2.

Use after free in append_command in vim/vim

Use after free in append_command in GitHub repository vim/vim prior to 8.2.4895. This vulnerability is capable of crashing software, Bypass Protection Mechanism, Modify Memory, and possible remote execution

kernel: use-after-free in hso_free_net_device() in drivers/net/usb/hso.c

hso_free_net_device in drivers/net/usb/hso.c in the Linux kernel through 5.13.4 calls unregister_netdev without checking for the NETREG_REGISTERED state, leading to a use-after-free and a double free.

nodejs: denial of service (DoS) by causing a node process which provides an http server supporting TLS server to crash

All versions of Node.js 9.x and 10.x are vulnerable and the severity is HIGH. An attacker can cause a denial of service (DoS) by causing a node process which provides an http server supporting TLS server to crash. This can be accomplished by sending duplicate/unexpected messages during the handshake. This vulnerability has been addressed by updating the TLS implementation.

Use After Free in vim/vim

Use After Free in GitHub repository vim/vim prior to 9.0.0046.

A maliciously crafted JT file in Autodesk AutoCAD 2022, 2021, 2020, 2019 can be used to trigger use-after-free vulnerability. Exploitation of this vulnerability may lead to code execution.

Use After Free in vim/vim

vim is vulnerable to Use After Free

kernel: slcan : race over tty->disc_data can lead use-after-free

In the Linux kernel before 5.4.16, a race condition in tty->disc_data handling in the slip and slcan line discipline could lead to a use-after-free, aka CID-0ace17d56824. This affects drivers/net/slip/slip.c and drivers/net/can/slcan.c.

kernel: use-after-free caused by a malicious USB device in the drivers/usb/class/cdc-acm.c driver

In the Linux kernel before 5.2.10, there is a use-after-free bug that can be caused by a malicious USB device in the drivers/usb/class/cdc-acm.c driver, aka CID-c52873e5a1ef.

python: Heap-Buffer-Overflow and Heap-Use-After-Free in Objects/fileobject.c

Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.

chromium-browser: Use after free in TabStrip

Use after free in TabStrip in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Foxit PDF Editor/Reader Annotation Use-After-Free Information Disclosure Vulnerability

A use-after-free vulnerability exists in Foxit PDF Editor/Reader’s handling of malformed PDF form fields. Improper validation during field-name traversal may cause the application to access a released object, resulting in an application crash.

Foxit PDF Editor/Reader AcroForm Use-After-Free Remote Code Execution Vulnerability

A use-after-free vulnerability exists in Foxit PDF Editor/Reader’s handling of PDF annotations. Reentrant annotation deletion triggered by embedded JavaScript can cause the application to access an annotation object after it has been released, resulting in a use-after-free condition and application crash.

Foxit PDF Editor/Reader Annotation Use-After-Free Remote Code Execution Vulnerability

A use-after-free vulnerability exists in Foxit PDF Editor/Reader’s JavaScript handling of PDF annotations. Reentrant page-event processing during annotation enumeration may release the associated page object, which is subsequently accessed, resulting in an application crash.