Export limit exceeded: 403962 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (36345 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-52977 | 1 Linux | 1 Linux Kernel | 2026-08-19 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup During wait-requeue-pi (task A) and requeue-PI (task B) the following race can happen: Task A Task B futex_wait_requeue_pi() futex_setup_timer() futex_do_wait() futex_requeue() CLASS(hb, hb1)(&key1); CLASS(hb, hb2)(&key2); *timeout* futex_requeue_pi_wakeup_sync() requeue_state = Q_REQUEUE_PI_IGNORE *blocks on hb->lock* futex_proxy_trylock_atomic() futex_requeue_pi_prepare() Q_REQUEUE_PI_IGNORE => -EAGAIN double_unlock_hb(hb1, hb2) *retry* Task B acquires both hb locks and attempts to acquire the PI-lock of the top most waiter (task B). Task A is leaving early due to a signal/ timeout and started removing itself from the queue. It updates its requeue_state but can not remove it from the list because this requires the hb lock which is owned by task B. Usually task A is able to swoop the lock after task B unlocked it. However if task B is of higher priority then task A may not be able to wake up in time and acquire the lock before task B gets it again. Especially on a UP system where A is never scheduled. As a result task A blocks on the lock and task B busy loops, trying to make progress but live locks the system instead. Tragic. This can be fixed by removing the top most waiter from the list in this case. This allows task B to grab the next top waiter (if any) in the next iteration and make progress. Remove the top most waiter if futex_requeue_pi_prepare() fails. Let the waiter conditionally remove itself from the list in handle_early_requeue_pi_wakeup(). | ||||
| CVE-2026-43491 | 1 Linux | 1 Linux Kernel | 2026-08-19 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: net: qrtr: ns: Limit the maximum server registration per node Current code does no bound checking on the number of servers added per node. A malicious client can flood NEW_SERVER messages and exhaust memory. Fix this issue by limiting the maximum number of server registrations to 256 per node. If the NEW_SERVER message is received for an old port, then don't restrict it as it will get replaced. While at it, also rate limit the error messages in the failure path of qrtr_ns_worker(). Note that the limit of 256 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased. | ||||
| CVE-2021-26444 | 1 Microsoft | 1 Azure Real Time Operating System | 2026-08-19 | 3.3 Low |
| Azure RTOS Information Disclosure Vulnerability | ||||
| CVE-2021-42323 | 1 Microsoft | 1 Azure Real Time Operating System | 2026-08-19 | 3.3 Low |
| Azure RTOS Information Disclosure Vulnerability | ||||
| CVE-2021-42278 | 1 Microsoft | 11 Windows Server 2004, Windows Server 2008, Windows Server 2008 R2 and 8 more | 2026-08-19 | 7.5 High |
| Active Directory Domain Services Elevation of Privilege Vulnerability | ||||
| CVE-2021-41356 | 1 Microsoft | 14 Windows 10, Windows 10 1507, Windows 10 1607 and 11 more | 2026-08-19 | 7.5 High |
| Windows Denial of Service Vulnerability | ||||
| CVE-2021-42305 | 1 Microsoft | 1 Exchange Server | 2026-08-19 | 6.5 Medium |
| Microsoft Exchange Server Spoofing Vulnerability | ||||
| CVE-2021-42288 | 1 Microsoft | 9 Windows 10, Windows 10 1809, Windows 10 1909 and 6 more | 2026-08-19 | 5.7 Medium |
| Windows Hello Security Feature Bypass Vulnerability | ||||
| CVE-2021-42284 | 1 Microsoft | 17 Windows 10, Windows 10 1507, Windows 10 1607 and 14 more | 2026-08-19 | 6.8 Medium |
| Windows Hyper-V Denial of Service Vulnerability | ||||
| CVE-2021-41376 | 1 Microsoft | 1 Azure Sphere | 2026-08-19 | 2.3 Low |
| Azure Sphere Information Disclosure Vulnerability | ||||
| CVE-2021-41375 | 1 Microsoft | 1 Azure Sphere | 2026-08-19 | 4.4 Medium |
| Azure Sphere Information Disclosure Vulnerability | ||||
| CVE-2021-41374 | 1 Microsoft | 1 Azure Sphere | 2026-08-19 | 6.7 Medium |
| Azure Sphere Information Disclosure Vulnerability | ||||
| CVE-2021-41373 | 1 Microsoft | 1 Fslogix | 2026-08-19 | 5.5 Medium |
| FSLogix Information Disclosure Vulnerability | ||||
| CVE-2021-41349 | 1 Microsoft | 1 Exchange Server | 2026-08-19 | 6.5 Medium |
| Microsoft Exchange Server Spoofing Vulnerability | ||||
| CVE-2023-21717 | 1 Microsoft | 3 Sharepoint Enterprise Server, Sharepoint Foundation, Sharepoint Server | 2026-08-19 | 8.8 High |
| Microsoft SharePoint Server Elevation of Privilege Vulnerability | ||||
| CVE-2021-41351 | 1 Microsoft | 4 Edge, Windows 10, Windows 11 and 1 more | 2026-08-19 | 4.3 Medium |
| Microsoft Edge (Chrome based) Spoofing on IE Mode | ||||
| CVE-2023-21716 | 1 Microsoft | 10 365 Apps, Office, Office Long Term Servicing Channel and 7 more | 2026-08-19 | 9.8 Critical |
| Microsoft Word Remote Code Execution Vulnerability | ||||
| CVE-2021-38631 | 1 Microsoft | 22 Windows 10, Windows 10 1507, Windows 10 1607 and 19 more | 2026-08-19 | 4.4 Medium |
| Windows Remote Desktop Protocol (RDP) Information Disclosure Vulnerability | ||||
| CVE-2021-40442 | 1 Microsoft | 14 365 Apps, Excel, Excel 2013 and 11 more | 2026-08-19 | 7.8 High |
| Microsoft Excel Remote Code Execution Vulnerability | ||||
| CVE-2021-38666 | 1 Microsoft | 23 Remote Desktop, Windows 10, Windows 10 1507 and 20 more | 2026-08-19 | 8.8 High |
| Remote Desktop Client Remote Code Execution Vulnerability | ||||