Vulnerabilities exploitable today
354,953in 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,656
New KEV · 24H0
Exploit Today ≥ 701,601
Distribution · last window
- Critical2,556
- High9,179
- Medium7,436
- Low693
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-30418—6.4%
——2——CVE-2022-33898—6.4%
——2——CVE-2026-32511—6.4%
——2——CVE-2022-50938—6.4%
——2——CVE-2025-11989—6.4%
——2——CVE-2022-38786—6.4%
——2——CVE-2026-43883—6.4%
——2——CVE-2022-32483—6.4%
——2——CVE-2026-56665—6.4%
——2——CVE-2026-48940—6.4%
——2——CVE-2026-23976—6.4%
——2——CVE-2023-40154—6.4%
——2——CVE-2026-32506—6.4%
——2——CVE-2023-32471—6.4%
——2——CVE-2023-25174—6.4%
——2——CVE-2026-32507—6.4%
——2——CVE-2025-58412—6.4%
——2——CVE-2024-32504—6.4%
——2——CVE-2026-28463—6.4%
——2——CVE-2023-28739—6.4%
——2——CVE-2026-28723—6.4%
——2——CVE-2025-381017.8 HIG6.4%
——2In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set()
Enlarge the critical section in ring_buffer_subbuf_order_set() to
ensure that error handling takes place with per-buffer mutex held,
thus preventing list corruption and other concurrency-related issues.4dCVE-2023-41784—6.4%
——2——CVE-2025-38027—6.4%
——2——CVE-2021-40037—6.4%
——2——CVE-2025-217017.8 HIG6.4%
——2In the Linux kernel, the following vulnerability has been resolved:
net: avoid race between device unregistration and ethnl ops
The following trace can be seen if a device is being unregistered while
its number of channels are being modified.
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 3 PID: 3754 at kernel/locking/mutex.c:564 __mutex_lock+0xc8a/0x1120
CPU: 3 UID: 0 PID: 3754 Comm: ethtool Not tainted 6.13.0-rc6+ #771
RIP: 0010:__mutex_lock+0xc8a/0x1120
Call Trace:
<TASK>
ethtool_check_max_channel+0x1ea/0x880
ethnl_set_channels+0x3c3/0xb10
ethnl_default_set_doit+0x306/0x650
genl_family_rcv_msg_doit+0x1e3/0x2c0
genl_rcv_msg+0x432/0x6f0
netlink_rcv_skb+0x13d/0x3b0
genl_rcv+0x28/0x40
netlink_unicast+0x42e/0x720
netlink_sendmsg+0x765/0xc20
__sys_sendto+0x3ac/0x420
__x64_sys_sendto+0xe0/0x1c0
do_syscall_64+0x95/0x180
entry_SYSCALL_64_after_hwframe+0x76/0x7e
This is because unregister_netdevice_many_notify might run before the
rtnl lock section of ethnl operations, eg. set_channels in the above
example. In this example the rss lock would be destroyed by the device
unregistration path before being used again, but in general running
ethnl operations while dismantle has started is not a good idea.
Fix this by denying any operation on devices being unregistered. A check
was already there in ethnl_ops_begin, but not wide enough.
Note that the same issue cannot be seen on the ioctl version
(__dev_ethtool) because the device reference is retrieved from within
the rtnl lock section there. Once dismantle started, the net device is
unlisted and no reference will be found.4dCVE-2026-41038—6.4%
——2——CVE-2023-21451—6.4%
——2——CVE-2025-68327—6.4%
——2——CVE-2022-36438—6.4%
——2——CVE-2025-10216—6.4%
——2——CVE-2026-32510—6.4%
——2——CVE-2025-30420—6.4%
——2——CVE-2024-31956—6.4%
——2——CVE-2026-461528.8 HIG6.4%
——2In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: drop stray 'static' from fast-RX rx_result
ieee80211_invoke_fast_rx() is documented as safe for parallel RX, but
its per-invocation rx_result is declared static. Concurrent callers then
share one instance and can overwrite each other's result between
ieee80211_rx_mesh_data() and the switch on res.
That can make a packet that was queued or consumed by
ieee80211_rx_mesh_data() fall through into ieee80211_rx_8023(), or make
a packet that should continue return as queued.
Make res an automatic variable so each invocation keeps its own result.5dCVE-2026-27769—6.4%
——2——CVE-2025-380987.8 HIG6.4%
——2In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Don't treat wb connector as physical in create_validate_stream_for_sink
Don't try to operate on a drm_wb_connector as an amdgpu_dm_connector.
While dereferencing aconnector->base will "work" it's wrong and
might lead to unknown bad things. Just... don't.4dCVE-2025-9098—6.4%
——2——CVE-2026-27898—6.4%
——2——CVE-2026-20010—6.4%
——2——