CVE-2024-45573
Published Feb 3, 2025Memory corruption may occour while generating test pattern due to negative indexing of display ID.
Loading current evidence
cvebuzz
CVE mentions, exploit signals, and PoC evidence in one fast public view.
CVE mentions, exploit signals, and PoC evidence in one fast public view.
Loading current evidence
Historical archive search
Search decades of CVEs by regex, severity, date, CWE, vendor/product tags, KEV, PoC, and other evidence.
Results
66 results · Sorted by Highest Buzz score first
Memory corruption may occour while generating test pattern due to negative indexing of display ID.
Memory corruption while handling IOCTL call from user-space to set latency level.
Memory corruption occurs when invoking any IOCTL-calling application that executes all MCDM driver IOCTL calls.
Memory corruption while processing FIPS encryption or decryption validation functionality IOCTL call.
Memory corruption while processing IOCTL call invoked from user-space to verify non extension FIPS encryption and decryption functionality.
Memory corruption while processing FIPS encryption or decryption IOCTL call invoked from user-space.
Memory corruption while invoking IOCTL calls from user space to read WLAN target diagnostic information.
Memory corruption while invoking IOCTL calls from user space to set generic private command inside WLAN driver.
Memory corruption when the captureRead QDCM command is invoked from user-space.
Memory corruption while creating a LPAC client as LPAC engine was allowed to access GPU registers.
Memory corruption while allocating memory for graphics.
Memory corruption while invoking the SubmitCommands call on Gfx engine during the graphics render.
Memory corruption while processing the IOCTL FM HCI WRITE request.
Information Disclosure while processing IOCTL request in FastRPC.
Memory corruption when negative display IDs are sent as input while processing DISPLAYESCAPE event trigger.
Memory corruption while reading ACPI config through the user mode app.
Every filter state lives in the URL so you can bookmark, share, and crawl exact historical slices instead of a client-only search session.
Buzz order uses the latest all-time evidence snapshot, refreshed every two hours. Evidence-bearing CVEs rank first; records without a snapshot continue newest-first.