CVE mentions, exploit signals, and PoC evidence in one fast public view.
Loading current evidence
Historical archive search
Search decades of CVEs by regex, severity, date, CWE, vendor/product tags, KEV, PoC, and other evidence.
Results
635 results · Sorted by Highest Buzz score first
In audio driver, there is a use after free due to a race condition. This could lead to local denial of service in kernel.
In wlan driver, there is a possible missing bounds check, This could lead to local denial of service in wlan services.
In camera driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In camera driver, there is a possible memory corruption due to improper locking. This could lead to local denial of service in kernel.
In face detect driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In face detect driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In power management service, there is a missing permission check. This could lead to set up power management service with no additional execution privileges needed.
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
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.