Vulnerabilidades explotables hoy
349,970en 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,647
Nuevos KEV · 24H0
Exploit Today ≥ 701,583
Distribución · última ventana
- Crítico1,333
- Alto4,375
- Medio3,748
- Bajo298
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2023-20817—0.5%
——0——CVE-2026-20772—0.5%
——0——CVE-2026-140947.8 ALT0.5%
——0Use after free in Installer in Google Chrome on Windows prior to 150.0.7871.47 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: Low)18dCVE-2023-32818—0.5%
——0——CVE-2023-32817—0.5%
——0——CVE-2025-47322—0.5%
——0——CVE-2023-32816—0.5%
——0——CVE-2025-20665—0.5%
——0——CVE-2023-32815—0.5%
——0——CVE-2026-50255—0.5%
——0——CVE-2026-23469—0.5%
——0——CVE-2024-20037—0.5%
——0——CVE-2022-47474—0.5%
——0——CVE-2025-35969—0.5%
——0——CVE-2024-42183—0.5%
——0——CVE-2023-20805—0.5%
——0——CVE-2022-47473—0.5%
——0——CVE-2023-21305—0.5%
——0——CVE-2026-585504.0 MED0.5%
——0Out-of-bounds read vulnerability in the image codec module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.4dCVE-2025-21475—0.5%
——0——CVE-2025-20723—0.5%
——0——CVE-2023-20800—0.5%
——0——CVE-2026-10814—0.5%
——0——CVE-2023-21377—0.5%
——0——CVE-2026-151734.7 MED0.5%
——0pcapng file parser crash in Wireshark 4.6.0 to 4.6.6 allows denial of service10dCVE-2022-20443—0.5%
——0——CVE-2023-32807—0.5%
——0——CVE-2023-21175—0.5%
——0——CVE-2021-39679—0.5%
——0——CVE-2026-43415—0.5%
——0——CVE-2023-20815—0.5%
——0——CVE-2025-710795.5 MED0.5%
——0In the Linux kernel, the following vulnerability has been resolved:
net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write
A deadlock can occur between nfc_unregister_device() and rfkill_fop_write()
due to lock ordering inversion between device_lock and rfkill_global_mutex.
The problematic lock order is:
Thread A (rfkill_fop_write):
rfkill_fop_write()
mutex_lock(&rfkill_global_mutex)
rfkill_set_block()
nfc_rfkill_set_block()
nfc_dev_down()
device_lock(&dev->dev) <- waits for device_lock
Thread B (nfc_unregister_device):
nfc_unregister_device()
device_lock(&dev->dev)
rfkill_unregister()
mutex_lock(&rfkill_global_mutex) <- waits for rfkill_global_mutex
This creates a classic ABBA deadlock scenario.
Fix this by moving rfkill_unregister() and rfkill_destroy() outside the
device_lock critical section. Store the rfkill pointer in a local variable
before releasing the lock, then call rfkill_unregister() after releasing
device_lock.
This change is safe because rfkill_fop_write() holds rfkill_global_mutex
while calling the rfkill callbacks, and rfkill_unregister() also acquires
rfkill_global_mutex before cleanup. Therefore, rfkill_unregister() will
wait for any ongoing callback to complete before proceeding, and
device_del() is only called after rfkill_unregister() returns, preventing
any use-after-free.
The similar lock ordering in nfc_register_device() (device_lock ->
rfkill_global_mutex via rfkill_register) is safe because during
registration the device is not yet in rfkill_list, so no concurrent
rfkill operations can occur on this device.5dCVE-2022-44448—0.5%
——0——CVE-2022-44447—0.5%
——0——CVE-2022-48242—0.5%
——0——CVE-2025-64457—0.5%
——0——CVE-2023-32813—0.5%
——0——CVE-2022-47476—0.5%
——0——CVE-2025-26454—0.5%
——0——CVE-2026-26100—0.5%
——0——