Vulnerabilidades explotables hoy
367,284en 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,685
Nuevos KEV · 24H0
Exploit Today ≥ 701,629
Distribución · última ventana
- Crítico2,295
- Alto9,356
- Medio5,353
- Bajo528
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-23093—2.3%
——1——CVE-2026-46028—2.3%
——1——CVE-2026-46002—2.3%
——1——CVE-2026-45986—2.3%
——1——CVE-2026-23324—2.3%
——1——CVE-2026-45960—2.3%
——1——CVE-2026-31434—2.3%
——1——CVE-2026-23145—2.3%
——1——CVE-2026-46049—2.3%
——1——CVE-2025-71297—2.3%
——1——CVE-2026-530525.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
ASoC: qcom: qdsp6: topology: check widget type before accessing data
Check widget type before accessing the private data, as this could a
virtual widget which is no associated with a dsp graph, container and
module. Accessing witout check could lead to incorrect memory access.42dCVE-2026-46098—2.3%
——1——CVE-2026-230845.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list
When the parameter pmac_id_valid argument of be_cmd_get_mac_from_list() is
set to false, the driver may request the PMAC_ID from the firmware of the
network card, and this function will store that PMAC_ID at the provided
address pmac_id. This is the contract of this function.
However, there is a location within the driver where both
pmac_id_valid == false and pmac_id == NULL are being passed. This could
result in dereferencing a NULL pointer.
To resolve this issue, it is necessary to pass the address of a stub
variable to the function.49dCVE-2026-23310—2.3%
——1——CVE-2026-46179—2.3%
——1——CVE-2026-31594—2.3%
——1——CVE-2026-31524—2.3%
——1——CVE-2026-43104—2.3%
——1——CVE-2026-43085—2.3%
——1——CVE-2026-43361—2.3%
——1——CVE-2026-230875.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
scsi: xen: scsiback: Fix potential memory leak in scsiback_remove()
Memory allocated for struct vscsiblk_info in scsiback_probe() is not
freed in scsiback_remove() leading to potential memory leaks on remove,
as well as in the scsiback_probe() error paths. Fix that by freeing it
in scsiback_remove().49dCVE-2026-43246—2.3%
——1——CVE-2026-31492—2.3%
——1——CVE-2026-43302—2.3%
——1——CVE-2026-46009—2.3%
——1——CVE-2026-45987—2.3%
——1——CVE-2026-46048—2.3%
——1——CVE-2026-43371—2.3%
——1——CVE-2026-31522—2.3%
——1——CVE-2026-23133—2.3%
——1——CVE-2026-43333—2.3%
——1——CVE-2026-234755.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
spi: fix statistics allocation
The controller per-cpu statistics is not allocated until after the
controller has been registered with driver core, which leaves a window
where accessing the sysfs attributes can trigger a NULL-pointer
dereference.
Fix this by moving the statistics allocation to controller allocation
while tying its lifetime to that of the controller (rather than using
implicit devres).39dCVE-2026-43312—2.3%
——1——CVE-2026-43445—2.3%
——1——CVE-2026-43425—2.3%
——1——CVE-2026-43316—2.3%
——1——CVE-2026-46101—2.3%
——1——CVE-2026-43412—2.3%
——1——CVE-2026-31738—2.3%
——1——CVE-2026-532795.5 MED2.3%
——1In the Linux kernel, the following vulnerability has been resolved:
drm/gma500/oaktrail_lvds: fix hang on init failure
The LVDS init code looks up an I2C adapter using i2c_get_adapter() and
tries to read the EDID before falling back to allocating and registering
its own adapter.
The error handling does not separate these cases so on a late init
failure it will try to deregister and free also an adapter that had
previously been registered. Since i2c_get_adapter() takes another
reference to the adapter, deregistration hangs indefinitely while
waiting for the reference to be released.
Fix this by only destroying adapters allocated during LVDS init on
errors.55d