CVE-2025-47355
Published Oct 9, 2025Memory corruption while invoking remote procedure IOCTL calls.
- evidence mentions
- 1
- Buzz score
- 11.9
Loading current evidence
Historical archive search
Search decades of CVEs by regex, severity, date, CWE, vendor/product tags, KEV, PoC, and other evidence.
Results
67 results · Sorted by Highest Buzz score first
Memory corruption while invoking remote procedure IOCTL calls.
Memory Corruption when multiple threads concurrently access and modify shared resources.
Memory Corruption when user space address is modified and passed to mem_free API, causing kernel memory to be freed inadvertently.
Memory Corruption when multiple threads simultaneously access a memory free API.
Memory corruption while accessing a buffer during IOCTL processing.
Memory corruption when dereferencing an invalid userspace address in a user buffer during MCDM IOCTL processing.
Memory corruption while preprocessing IOCTL request in JPEG driver.
Memory corruption when processing camera sensor input/output control codes with invalid output buffers.
Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level.
Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
Memory corruption in windows drivers while sending incorrect trusted application request
Memory Corruption when output buffer size is smaller than input buffer size during data copying operation.
Memory Corruption when sending random number generator command with insufficient output buffer size.
Memory Corruption when using deprecated DMABUF IOCTL calls to manage video memory.
Memory Corruption when handling power management requests with improperly sized input/output buffers.
Memory corruption while processing IOCTL calls for escape operations.
Memory corruption while processing multiple IOCTL command for escape operations.
Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.
Memory corruption while processing IOCTL command when device is in power-save state.
Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between check and use.
Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input.
Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input due to accessing already freed memory.
Memory corruption may occur while attaching VM when the HLOS retains access to VM.
Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.
Memory corruption while doing Escape call when user provides valid kernel address in the place of valid user buffer address.
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.