CVE detail
CVE-2026-21373
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing.
Buzz score
Why this CVE is surfacing
This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.
Buzz score components · mention 6.9 · diversity 5.0 · KEV 0.0 · OTX 0.0 · PoC 0.0
Why it matters now
Mention timeline
- Total mentions
- 0
- within the 30d window
- Peak daily
- 0
- highest bucket
Evidence
Source links by recency
1 source links · newest first
- https://docs.qualcomm.com/product/publicresources/securitybulletin/april-2026-bulletin.htmldocs.qualcomm.com
No excerpt available.
Vendor Advisorydocs.qualcomm.comApr 6, 2026, 4:16 PM
Exploit code
Public exploit repository references
Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.
0 repository references · best confidence N/A · max 0 stars
Related records
Similar CVEs
6 related CVEs with shared weakness or product evidence
- CVE-2026-21379CVSS 7.8 · High
Memory Corruption when allocating memory with sizes that exceed the maximum allowed value.
- CVE-2025-59611CVSS 6.7 · Medium
Memory corruption in diagnostic services due to absence of input validation
- CVE-2025-27055CVSS 7.8 · High
Memory corruption during the image encoding process.
- CVE-2025-21475CVSS 7.8 · High
Memory corruption while processing escape code, when DisplayId is passed with large unsigned value.
- CVE-2025-21421CVSS 7.8 · High
Memory corruption while processing escape code in API.
- CVE-2024-45561CVSS 7.8 · High
Memory corruption while handling IOCTL call from user-space to set latency level.