CVE-2025-47322
Published Dec 18, 2025Memory corruption while handling IOCTL calls to set mode.
- 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
161 results · Sorted by Highest Buzz score first
Memory corruption while handling IOCTL calls to set mode.
Memory corruption while routing GPR packets between user and root when handling large data packet.
Memory corruption while handling invalid inputs in application info setup.
Memory corruption while processing control commands in the virtual memory management interface.
Memory corruption while processing request sent from GVM.
Information Disclosure when a user-level driver performs QFPROM read or write operations on Fuse regions.
Memory corruption while processing client message during device management.
Memory corruption when triggering a subsystem crash with an out-of-range identifier.
Information disclosure while processing message from client with invalid payload.
Memory corruption when calculating oversized partition sizes without proper checks.
Memory corruption while calculating offset from partition start point.
Memory corruption while processing large input data from a remote source via a communication interface.
Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls.
Cryptographic Issue when a shared VM reference allows HLOS to boot loader and access cert chain.
Memory Corruption while processing IOCTL calls when concurrent access to shared buffer occurs.
Memory corruption while loading an invalid firmware in boot loader.
Memory corruption when accessing resources in kernel driver.
Memory corruption while processing a packet with a size close to the maximum allowed value.
Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits.
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.
Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to a user throttling by…
Cryptographic issues while generating an asymmetric key pair for RKP use cases.
Memory corruption while assigning memory from the source DDR memory(HLOS) to ADSP.
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.