CVE-2026-21368
Published Jul 6, 2026Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
- 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
11 results · Sorted by Highest Buzz score first
Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification.
Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
Memory Corruption when allocating memory with sizes that exceed the maximum allowed value.
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 when processing invalid HT40 channel layouts during dynamic channel switching operations.
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 when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization.
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.