Vulnerabilidades explotables hoy
367,165en 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,263
- Alto9,268
- Medio5,273
- Bajo508
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2023-40111—0.7%
——0——CVE-2023-42730—0.7%
——0——CVE-2023-42710—0.7%
——0——CVE-2026-42487—0.7%
——0——CVE-2023-21011—0.7%
——0——CVE-2022-20241—0.7%
——0——CVE-2026-40951—0.7%
——0——CVE-2023-20985—0.7%
——0——CVE-2023-20993—0.7%
——0——CVE-2025-22422—0.7%
——0——CVE-2025-3395—0.7%
——0——CVE-2025-20740—0.7%
——0——CVE-2026-122356.3 MED0.7%
——0The Linkable Loadable Extensions (llext) subsystem mis-handles PLT/RELA relocation entries when linking a relocatable (partially-linked) ELF extension. In llext_link_plt() (subsys/llext/llext_link.c), the relocatable branch (tgt != NULL, the path used for Xtensa relocatable objects) computed the patch address as ext->mem[LLEXT_MEM_TEXT] - text.sh_offset + rela.r_offset + tgt->sh_offset and then performed the relocation write there without validating rela.r_offset. Its sibling shared/dynamic branch already rejected out-of-range offsets via llext_file_offset().
rela.r_offset is read directly from the ELF's RELA table, so a crafted entry with an offset larger than the target section makes the write land arbitrarily far outside the extension's text buffer. The result is an attacker-influenced out-of-bounds write (the location via r_offset, the written value being the resolved symbol address) performed in supervisor context at link time, before any extension code runs.
The path is reached from llext_load() whenever an application loads an attacker-influenced ELF extension on Xtensa with writable storage; llext is documented to accept extensions of untrusted origin. Impact is supervisor-context memory corruption (integrity and availability loss, and a sandbox-boundary escape for user-mode extensions). Exploitation is gated by the Xtensa relocatable PLT path and writable storage, and turning the out-of-range write into a useful primitive is non-trivial.
The fix adds a bound check rejecting any RELA entry whose r_offset >= tgt->sh_size, mirroring the existing validation in the shared branch.5dCVE-2023-42677—0.7%
——0——CVE-2023-42707—0.7%
——0——CVE-2023-42714—0.7%
——0——CVE-2026-2915—0.7%
——0——CVE-2026-4159—0.7%
——0——CVE-2023-42705—0.7%
——0——CVE-2023-21022—0.7%
——0——CVE-2025-14596—0.7%
——0——CVE-2024-23707—0.7%
——0——CVE-2024-36323—0.7%
——0——CVE-2024-20015—0.7%
——0——CVE-2023-42713—0.7%
——0——CVE-2023-42704—0.7%
——0——CVE-2022-47462—0.7%
——0——CVE-2026-200646.5 MED0.7%
——0A vulnerability in of Cisco Secure Firewall Threat Defense (FTD) Software could allow an authenticated, local attacker to cause the device to unexpectedly reload, causing a denial of service (DoS) condition.
This vulnerability is due to improper validation of user-supplied input. An attacker with a low-privileged account could exploit this vulnerability by using crafted commands at the CLI prompt. A successful exploit could allow the attacker to cause the device to reload, resulting in a DoS condition.20dCVE-2026-20037—0.7%
——0——CVE-2026-0017—0.7%
——0——CVE-2022-47461—0.7%
——0——CVE-2023-21279—0.7%
——0——CVE-2024-27220—0.7%
——0——CVE-2023-42700—0.7%
——0——CVE-2023-42733—0.7%
——0——CVE-2026-231104.7 MED0.7%
——0In the Linux kernel, the following vulnerability has been resolved:
scsi: core: Wake up the error handler when final completions race against each other
The fragile ordering between marking commands completed or failed so
that the error handler only wakes when the last running command
completes or times out has race conditions. These race conditions can
cause the SCSI layer to fail to wake the error handler, leaving I/O
through the SCSI host stuck as the error state cannot advance.
First, there is an memory ordering issue within scsi_dec_host_busy().
The write which clears SCMD_STATE_INFLIGHT may be reordered with reads
counting in scsi_host_busy(). While the local CPU will see its own
write, reordering can allow other CPUs in scsi_dec_host_busy() or
scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to
see a host busy equal to the host_failed count.
This race condition can be prevented with a memory barrier on the error
path to force the write to be visible before counting host busy
commands.
Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By
counting busy commands before incrementing host_failed, it can race with a
final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does
not see host_failed incremented but scsi_eh_inc_host_failed() counts busy
commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(),
resulting in neither waking the error handler task.
This needs the call to scsi_host_busy() to be moved after host_failed is
incremented to close the race condition.48dCVE-2023-42712—0.7%
——0——CVE-2025-43914—0.7%
——0——CVE-2024-47124—0.7%
——0——CVE-2026-24986—0.7%
——0——