VYPR

CWE-416

Use After Free

VariantStableLikelihood: High

Description

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Hierarchy (View 1000)

Parents

Children

none

CVEs mapped to this weakness (8,218)

page 179 of 411
  • CVE-2025-27476HigApr 8, 2025
    risk 0.51cvss 7.8epss 0.01

    Use after free in Windows Digital Media allows an authorized attacker to elevate privileges locally.

  • CVE-2025-27467HigApr 8, 2025
    risk 0.51cvss 7.8epss 0.01

    Use after free in Windows Digital Media allows an authorized attacker to elevate privileges locally.

  • CVE-2025-27200HigApr 8, 2025
    risk 0.51cvss 7.8epss 0.00

    Animate versions 24.0.7, 23.0.10 and earlier are affected by a Use After Free vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

  • CVE-2025-26679HigApr 8, 2025
    risk 0.51cvss 7.8epss 0.01

    Use after free in RPC Endpoint Mapper Service allows an authorized attacker to elevate privileges locally.

  • CVE-2025-26648HigApr 8, 2025
    risk 0.51cvss 7.8epss 0.00

    Sensitive data storage in improperly locked memory in Windows Kernel allows an authorized attacker to elevate privileges locally.

  • CVE-2025-21437HigApr 7, 2025
    risk 0.51cvss 7.8epss 0.00

    Memory corruption while processing memory map or unmap IOCTL operations simultaneously.

  • CVE-2025-21436HigApr 7, 2025
    risk 0.51cvss 7.8epss 0.00

    Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads.

  • CVE-2024-43066HigApr 7, 2025
    risk 0.51cvss 7.8epss 0.00

    Memory corruption while handling file descriptor during listener registration/de-registration.

  • CVE-2025-21968HigApr 1, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix slab-use-after-free on hdcp_work [Why] A slab-use-after-free is reported when HDCP is destroyed but the property_validate_dwork queue is still running. [How] Cancel the delayed work when…

  • CVE-2025-21934HigApr 1, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: rapidio: fix an API misues when rio_add_net() fails rio_add_net() calls device_register() and fails when device_register() fails. Thus, put_device() should be used rather than kfree(). Add "mport->net =…

  • CVE-2025-21929HigApr 1, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: Fix use-after-free issue in hid_ishtp_cl_remove() During the `rmmod` operation for the `intel_ishtp_hid` driver, a use-after-free issue can occur in the hid_ishtp_cl_remove() function. The…

  • CVE-2025-21928HigApr 1, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() The system can experience a random crash a few minutes after the driver is removed. This issue occurs due to improper handling of memory…

  • CVE-2025-21923HigApr 1, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: HID: hid-steam: Fix use-after-free when detaching device When a hid-steam device is removed it must clean up the client_hdev used for intercepting hidraw access. This can lead to scheduling deferred work to…

  • CVE-2025-21896HigApr 1, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: fuse: revert back to __readahead_folio() for readahead In commit 3eab9d7bc2f4 ("fuse: convert readahead to use folios"), the logic was converted to using the new folio readahead code, which drops the reference…

  • CVE-2025-21893HigMar 31, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: keys: Fix UAF in key_put() Once a key's reference count has been reduced to 0, the garbage collector thread may destroy it at any time and so key_put() is not allowed to touch the key after that point. The…

  • CVE-2023-53023HigMar 27, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: net: nfc: Fix use-after-free in local_cleanup() Fix a use-after-free that occurs in kfree_skb() called from local_cleanup(). This could happen when killing nfc daemon (e.g. neard) after detaching an nfc…

  • CVE-2023-53021HigMar 27, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_taprio: fix possible use-after-free syzbot reported a nasty crash [1] in net_tx_action() which made little sense until we got a repro. This repro installs a taprio qdisc, but providing an…

  • CVE-2023-53003HigMar 27, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info The memory for llcc_driv_data is allocated by the LLCC driver. But when it is passed as the private driver info to the EDAC core, it…

  • CVE-2023-52999HigMar 27, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: net: fix UaF in netns ops registration error path If net_assign_generic() fails, the current error path in ops_init() tries to clear the gen pointer slot. Anyway, in such error path, the gen pointer itself has…

  • CVE-2023-52983HigMar 27, 2025
    risk 0.51cvss 7.8epss 0.00

    In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for bfqq in bic_set_bfqq() After commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'"), bic->bfqq will be accessed in bic_set_bfqq(), however, in some context bic->bfqq will…