Vulnerabilidades explotables hoy
350,369en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,651
Nuevos KEV · 24H4
Exploit Today ≥ 701,587
Distribución · última ventana
- Crítico1,484
- Alto4,943
- Medio4,052
- Bajo320
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-44348—0.9%
——0——CVE-2026-7539—0.9%
——0——CVE-2026-20409—0.9%
——0——CVE-2023-21652—0.9%
——0——CVE-2022-47470—0.9%
——0——CVE-2023-21081—0.9%
——0——CVE-2023-21203—0.9%
——0——CVE-2026-232717.8 ALT0.9%
——0In the Linux kernel, the following vulnerability has been resolved:
perf: Fix __perf_event_overflow() vs perf_remove_from_context() race
Make sure that __perf_event_overflow() runs with IRQs disabled for all
possible callchains. Specifically the software events can end up running
it with only preemption disabled.
This opens up a race vs perf_event_exit_event() and friends that will go
and free various things the overflow path expects to be present, like
the BPF program.7dCVE-2026-618722.5 BAJ0.9%
——0ImageMagick before 7.1.2-26 and 6.9.13-51 contains a memory leak in the TIFF encoder when an invalid tiff:tile-geometry is specified. Supplying malformed tile geometry parameters causes allocated memory not to be released, which can lead to increased memory consumption.6dCVE-2018-21080—0.9%
——0——CVE-2024-20088—0.9%
——0——CVE-2023-21158—0.9%
——0——CVE-2025-21061—0.9%
——0——CVE-2025-21062—0.9%
——0——CVE-2026-31667—0.9%
——0——CVE-2024-38302—0.9%
——0——CVE-2023-42746—0.9%
——0——CVE-2023-42748—0.9%
——0——CVE-2023-42745—0.9%
——0——CVE-2026-6499—0.9%
——0——CVE-2022-47491—0.9%
——0——CVE-2026-43864—0.9%
——0——CVE-2026-156837.5 ALT0.9%
——0Lorex 2K Indoor Wi-Fi Security Camera Device Management Server Improper Certificate Validation Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Lorex 2K Indoor Wi-Fi Security Cameras. User interaction is not required to exploit this vulnerability.
The specific flaw exists within the device management functionality. The issue results from the lack of proper validation of the certificate presented by the server. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-26851.7dCVE-2025-15320—0.9%
——0——CVE-2022-20464—0.8%
——0——CVE-2022-48235—0.8%
——0——CVE-2023-20982—0.8%
——0——CVE-2026-0541—0.8%
——0——CVE-2023-21103—0.8%
——0——CVE-2022-47498—0.8%
——0——CVE-2022-20350—0.8%
——0——CVE-2025-54612—0.8%
——0——CVE-2023-20985—0.8%
——0——CVE-2022-48238—0.8%
——0——CVE-2023-21099—0.8%
——0——CVE-2022-48237—0.8%
——0——CVE-2022-20293—0.8%
——0——CVE-2023-32812—0.8%
——0——CVE-2025-712217.0 ALT0.8%
——0In the Linux kernel, the following vulnerability has been resolved:
dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue()
Add proper locking in mmp_pdma_residue() to prevent use-after-free when
accessing descriptor list and descriptor contents.
The race occurs when multiple threads call tx_status() while the tasklet
on another CPU is freeing completed descriptors:
CPU 0 CPU 1
----- -----
mmp_pdma_tx_status()
mmp_pdma_residue()
-> NO LOCK held
list_for_each_entry(sw, ..)
DMA interrupt
dma_do_tasklet()
-> spin_lock(&desc_lock)
list_move(sw->node, ...)
spin_unlock(&desc_lock)
| dma_pool_free(sw) <- FREED!
-> access sw->desc <- UAF!
This issue can be reproduced when running dmatest on the same channel with
multiple threads (threads_per_chan > 1).
Fix by protecting the chain_running list iteration and descriptor access
with the chan->desc_lock spinlock.7dCVE-2022-48374—0.8%
——0——