CVE-2025-47343
Published Jan 7, 2026Memory corruption while processing a video session to set video parameters.
- 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
17 results · Sorted by Highest Buzz score first
Memory corruption while processing a video session to set video parameters.
Memory corruption while handling concurrent memory mapping and unmapping requests from a user-space application.
Memory Corruption when multiple threads concurrently access and modify shared resources.
Memory corruption when processing camera sensor input/output control codes with invalid output buffers.
Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
Memory corruption in diagnostic services due to absence of input validation
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 accessing an output buffer without validating its size during IOCTL processing.
Memory Corruption when allocating memory with sizes that exceed the maximum allowed value.
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 when processing registry values with incorrect types using a direct query method.
Memory corruption while processing IOCTL calls for escape operations.
Memory corruption while processing multiple IOCTL command for escape operations.
Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between check and use.
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.