Vulnerabilities exploitable today
352,317in 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,653
New KEV · 24H0
Exploit Today ≥ 701,590
Distribution · last window
- Critical2,150
- High7,306
- Medium6,373
- Low617
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-40354—2.8%
——1——CVE-2022-50326—2.8%
——1——CVE-2026-20623—2.8%
——1——CVE-2023-53319—2.8%
——1——CVE-2025-38504—2.8%
——1——CVE-2026-46126—2.8%
——1——CVE-2023-20755—2.8%
——1——CVE-2022-20011—2.8%
——1——CVE-2023-53236—2.8%
——1——CVE-2026-43137—2.8%
——1——CVE-2022-50506—2.8%
——1——CVE-2026-57305—2.8%
——1——CVE-2026-46207—2.8%
——1——CVE-2022-50688—2.8%
——1——CVE-2026-43167—2.8%
——1——CVE-2026-40001—2.8%
——1——CVE-2025-58150—2.8%
——1——CVE-2025-25273—2.8%
——1——CVE-2026-432165.5 MED2.8%
——1In the Linux kernel, the following vulnerability has been resolved:
net: Drop the lock in skb_may_tx_timestamp()
skb_may_tx_timestamp() may acquire sock::sk_callback_lock. The lock must
not be taken in IRQ context, only softirq is okay. A few drivers receive
the timestamp via a dedicated interrupt and complete the TX timestamp
from that handler. This will lead to a deadlock if the lock is already
write-locked on the same CPU.
Taking the lock can be avoided. The socket (pointed by the skb) will
remain valid until the skb is released. The ->sk_socket and ->file
member will be set to NULL once the user closes the socket which may
happen before the timestamp arrives.
If we happen to observe the pointer while the socket is closing but
before the pointer is set to NULL then we may use it because both
pointer (and the file's cred member) are RCU freed.
Drop the lock. Use READ_ONCE() to obtain the individual pointer. Add a
matching WRITE_ONCE() where the pointer are cleared.7hCVE-2023-53496—2.8%
——1——CVE-2026-46142—2.8%
——1——CVE-2023-53231—2.8%
——1——CVE-2026-45928—2.8%
——1——CVE-2023-53170—2.8%
——1——CVE-2026-33536—2.8%
——1——CVE-2023-53306—2.8%
——1——CVE-2025-712895.5 MED2.8%
——1In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: handle attr_set_size() errors when truncating files
If attr_set_size() fails while truncating down, the error is silently
ignored and the inode may be left in an inconsistent state.7hCVE-2021-0704—2.8%
——1——CVE-2023-53460—2.8%
——1——CVE-2025-39690—2.8%
——1——CVE-2026-43177—2.8%
——1——CVE-2026-20648—2.8%
——1——CVE-2022-50292—2.8%
——1——CVE-2025-38296—2.8%
——1——CVE-2025-22893—2.8%
——1——CVE-2023-53172—2.8%
——1——CVE-2025-39699—2.8%
——1——CVE-2025-33000—2.8%
——1——CVE-2024-33035—2.8%
——1——CVE-2019-25305—2.8%
——1——