Vulnerabilities exploitable today
349,507in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,647
New KEV · 24H0
Exploit Today ≥ 701,582
Distribution · last window
- Critical1,331
- High4,364
- Medium3,727
- Low291
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2023-20753—1.0%
——0——CVE-2023-21214—1.0%
——0——CVE-2022-21764—1.0%
——0——CVE-2023-20632—1.0%
——0——CVE-2024-58114—1.0%
——0——CVE-2026-21040—1.0%
——0——CVE-2024-45448—1.0%
——0——CVE-2022-33700—1.0%
——0——CVE-2022-32651—1.0%
——0——CVE-2022-25332—1.0%
——0——CVE-2023-21188—1.0%
——0——CVE-2022-33692—1.0%
——0——CVE-2023-21078—1.0%
——0——CVE-2025-32735—1.0%
——0——CVE-2023-21222—1.0%
——0——CVE-2023-31313—0.9%
——0——CVE-2025-20638—1.0%
——0——CVE-2026-43353—1.0%
——0——CVE-2023-21079—1.0%
——0——CVE-2023-33895—1.0%
——0——CVE-2023-33894—1.0%
——0——CVE-2025-29933—1.0%
——0——CVE-2025-48653—1.0%
——0——CVE-2024-43063—1.0%
——0——CVE-2025-0372—1.0%
——0——CVE-2023-33890—1.0%
——0——CVE-2023-21072—1.0%
——0——CVE-2023-21073—1.0%
——0——CVE-2023-21075—1.0%
——0——CVE-2026-39635—1.0%
——0——CVE-2023-21236—1.0%
——0——CVE-2026-42481—1.0%
——0——CVE-2025-52608—0.9%
——0——CVE-2026-532075.5 MED1.0%
——0In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison
Two concurrent madvise(MADV_HWPOISON) calls on the same hugetlb page can
trigger a recursive spinlock self-deadlock (AA deadlock) on hugetlb_lock
when racing with a concurrent unmap:
thread#0 thread#1
-------- --------
madvise(folio, MADV_HWPOISON)
-> poisons the folio successfully
madvise(folio, MADV_HWPOISON) unmap(folio)
try_memory_failure_hugetlb
get_huge_page_for_hwpoison
spin_lock_irq(&hugetlb_lock) <- held
__get_huge_page_for_hwpoison
hugetlb_update_hwpoison()
-> MF_HUGETLB_FOLIO_PRE_POISONED
goto out:
folio_put()
refcount: 1 -> 0
free_huge_folio()
spin_lock_irqsave(&hugetlb_lock)
-> AA DEADLOCK!
The out: path in __get_huge_page_for_hwpoison() calls folio_put() to drop
the GUP reference while the hugetlb_lock is still held by the hugetlb.c
wrapper get_huge_page_for_hwpoison(). If concurrent unmap has released
the page table mapping reference, folio_put() drops the folio refcount to
zero, triggering free_huge_folio() which attempts to re-acquire the
non-recursive hugetlb_lock.
Fix this by moving hugetlb_lock acquisition from the hugetlb.c wrapper
into get_huge_page_for_hwpoison(). Place spin_unlock_irq() before the
folio_put() at the out: label so the folio is always released outside the
lock.
[akpm@linux-foundation.org: fix race, rename label per Miaohe]16dCVE-2022-49884—1.0%
——0——CVE-2023-20849—1.0%
——0——CVE-2022-20143—1.0%
——0——CVE-2025-53919—1.0%
——0——CVE-2022-33697—1.0%
——0——CVE-2022-33695—1.0%
——0——