Vulnerabilities exploitable today
349,195in 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,644
New KEV · 24H0
Exploit Today ≥ 701,579
Distribution · last window
- Critical1,298
- High4,252
- Medium3,575
- Low277
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-20427—0.2%
——0——CVE-2026-4430—0.2%
——0——CVE-2023-38466—0.2%
——0——CVE-2023-40648—0.2%
——0——CVE-2023-40647—0.2%
——0——CVE-2026-21373—0.2%
——0——CVE-2023-40633—0.2%
——0——CVE-2025-22417—0.2%
——0——CVE-2024-47018—0.2%
——0——CVE-2026-41961—0.2%
——0——CVE-2023-40637—0.2%
——0——CVE-2025-36887—0.2%
——0——CVE-2025-66330—0.2%
——0——CVE-2025-66324—0.2%
——0——CVE-2026-530084.7 MED0.2%
——0In the Linux kernel, the following vulnerability has been resolved:
ice: fix race condition in TX timestamp ring cleanup
Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map()
that can cause a NULL pointer dereference.
ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag
after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map
call on another CPU to dereference the tstamp_ring, which could lead to
a NULL pointer dereference.
CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map()
--------------------------------|---------------------------------
tx_ring->tstamp_ring = NULL |
| ice_is_txtime_cfg() -> true
| tstamp_ring = tx_ring->tstamp_ring
| tstamp_ring->count // NULL deref!
flags &= ~ICE_TX_FLAGS_TXTIME |
Fix by:
1. Reordering ice_free_tx_tstamp_ring() to clear the flag before
NULLing the pointer, with smp_wmb() to ensure proper ordering.
2. Adding smp_rmb() in ice_tx_map() after the flag check to order the
flag read before the pointer read, using READ_ONCE() for the
pointer, and adding a NULL check as a safety net.
3. Converting tx_ring->flags from u8 to DECLARE_BITMAP() and using
atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag
operations throughout the driver:
- ICE_TX_RING_FLAGS_XDP
- ICE_TX_RING_FLAGS_VLAN_L2TAG1
- ICE_TX_RING_FLAGS_VLAN_L2TAG2
- ICE_TX_RING_FLAGS_TXTIME3dCVE-2024-14024—0.2%
——0——CVE-2023-40646—0.2%
——0——CVE-2026-34863—0.2%
——0——CVE-2026-34866—0.2%
——0——CVE-2025-20743—0.2%
——0——CVE-2026-28545—0.2%
——0——CVE-2026-34859—0.2%
——0——CVE-2023-40649—0.2%
——0——CVE-2026-41962—0.1%
——0——CVE-2026-41973—0.2%
——0——CVE-2025-20636—0.2%
——0——CVE-2026-41984—0.2%
——0——CVE-2023-38442—0.2%
——0——CVE-2026-46693—0.2%
——0——CVE-2023-21000—0.2%
——0——CVE-2025-20648—0.1%
——0——CVE-2025-47362—0.2%
——0——CVE-2023-38441—0.2%
——0——CVE-2023-38440—0.2%
——0——CVE-2025-22439—0.2%
——0——CVE-2025-58315—0.2%
——0——CVE-2025-32346—0.1%
——0——CVE-2024-25990—0.2%
——0——CVE-2024-44099—0.2%
——0——CVE-2023-42631—0.2%
——0——