CVE-2024-45540
Published Apr 7, 2025Memory corruption while invoking IOCTL map buffer request from userspace.
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
150 results · Sorted by Highest Buzz score first
Memory corruption while invoking IOCTL map buffer request from userspace.
Memory corruption while reading a value from a buffer controlled by the Guest Virtual Machine.
Memory corruption may occur while processing message from frontend during allocation.
Memory corruption may occur during communication between primary and guest VM.
Memory corruption may occur due to improper input validation in clock device.
Memory corruption while reading CPU state data during guest VM suspend.
Memory corruption can occur in the camera when an invalid CID is used.
Memory corruption while parsing the memory map info in IOCTL calls.
Transient DOS can occur when GVM sends a specific message type to the Vdev-FastRPC backend.
Uncontrolled resource consumption when a driver, an application or a SMMU client tries to access the global registers through SMMU.
information disclosure while invoking the mailbox read API.
Information Disclosure while invoking the mailbox write API when message received from user is larger than mailbox size.
Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer acce…
Memory corruption while processing concurrent IOCTL calls.
Memory corruption while calculating total metadata size when a very high reserved size is requested by gralloc clients.
Memory corruption while releasing shared resources in MinkSocket listener thread.
Memory corruption when more scan frequency list or channels are sent from the user space.
Memory corruption in Kernel while handling GPU operations.
Memory corruption in Graphics Driver when destroying a context with KGSL_GPU_AUX_COMMAND_TIMELINE objects queued.
Information disclosure in Core services while processing a Diag command.
Memory corruption in Automotive OS whenever untrusted apps try to access HAb for graphics functionalities.
Memory corruption in WLAN Host while setting the PMK length in PMK length in internal cache.
Memory Corruption in WLAN Host while deserializing the input PMK bytes without checking the input PMK length.
Memory Corruption in Radio Interface Layer while sending an SMS or writing an SMS to SIM.
Memory corruption in Automotive Display while destroying the image handle created using connected display driver.
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.