Instituto Nacional de ciberseguridad. Sección Incibe
Instituto Nacional de Ciberseguridad. Sección INCIBE-CERT

017 - Ir a la línea de ayuda en Ciberseguridad    Ir a Agenda     Ir a Sala de prensa     Ir a suscripción de boletines

Ir al buscador

Vulnerabilidades

Con el objetivo de informar, advertir y ayudar a los profesionales sobre las ultimas vulnerabilidades de seguridad en sistemas tecnológicos, ponemos a disposición de los usuarios interesados en esta información una base de datos con información en castellano sobre cada una de las ultimas vulnerabilidades documentadas y conocidas.

Este repositorio con más de 75.000 registros esta basado en la información de NVD (National Vulnerability Database) – en función de un acuerdo de colaboración – por el cual desde INCIBE realizamos la traducción al castellano de la información incluida. En ocasiones este listado mostrará vulnerabilidades que aún no han sido traducidas debido a que se recogen en el transcurso del tiempo en el que el equipo de INCIBE realiza el proceso de traducción.

Se emplea el estándar de nomenclatura de vulnerabilidades CVE (Common Vulnerabilities and Exposures), con el fin de facilitar el intercambio de información entre diferentes bases de datos y herramientas. Cada una de las vulnerabilidades recogidas enlaza a diversas fuentes de información así como a parches disponibles o soluciones aportadas por los fabricantes y desarrolladores. Es posible realizar búsquedas avanzadas teniendo la opción de seleccionar diferentes criterios como el tipo de vulnerabilidad, fabricante, tipo de impacto entre otros, con el fin de acortar los resultados.

Mediante suscripción RSS o Boletines podemos estar informados diariamente de las ultimas vulnerabilidades incorporadas al repositorio.

CVE-2025-2154
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Echo Call Center Services Trade and Industry Inc. Specto CM allows Stored XSS.This issue affects Specto CM: before 17032025.
Gravedad CVSS v3.1: MEDIA
Última modificación:
24/12/2025

CVE-2025-5448
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** Rejected reason: This CVE id was assigned but later discarded.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68746
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> spi: tegra210-quad: Fix timeout handling<br /> <br /> When the CPU that the QSPI interrupt handler runs on (typically CPU 0)<br /> is excessively busy, it can lead to rare cases of the IRQ thread not<br /> running before the transfer timeout is reached.<br /> <br /> While handling the timeouts, any pending transfers are cleaned up and<br /> the message that they correspond to is marked as failed, which leaves<br /> the curr_xfer field pointing at stale memory.<br /> <br /> To avoid this, clear curr_xfer to NULL upon timeout and check for this<br /> condition when the IRQ thread is finally run.<br /> <br /> While at it, also make sure to clear interrupts on failure so that new<br /> interrupts can be run.<br /> <br /> A better, more involved, fix would move the interrupt clearing into a<br /> hard IRQ handler. Ideally we would also want to signal that the IRQ<br /> thread no longer needs to be run after the timeout is hit to avoid the<br /> extra check for a valid transfer.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68747
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/panthor: Fix UAF on kernel BO VA nodes<br /> <br /> If the MMU is down, panthor_vm_unmap_range() might return an error.<br /> We expect the page table to be updated still, and if the MMU is blocked,<br /> the rest of the GPU should be blocked too, so no risk of accessing<br /> physical memory returned to the system (which the current code doesn&amp;#39;t<br /> cover for anyway).<br /> <br /> Proceed with the rest of the cleanup instead of bailing out and leaving<br /> the va_node inserted in the drm_mm, which leads to UAF when other<br /> adjacent nodes are removed from the drm_mm tree.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68748
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/panthor: Fix UAF race between device unplug and FW event processing<br /> <br /> The function panthor_fw_unplug() will free the FW memory sections.<br /> The problem is that there could still be pending FW events which are yet<br /> not handled at this point. process_fw_events_work() can in this case try<br /> to access said freed memory.<br /> <br /> Simply call disable_work_sync() to both drain and prevent future<br /> invocation of process_fw_events_work().
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68749
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> accel/ivpu: Fix race condition when unbinding BOs<br /> <br /> Fix &amp;#39;Memory manager not clean during takedown&amp;#39; warning that occurs<br /> when ivpu_gem_bo_free() removes the BO from the BOs list before it<br /> gets unmapped. Then file_priv_unbind() triggers a warning in<br /> drm_mm_takedown() during context teardown.<br /> <br /> Protect the unmapping sequence with bo_list_lock to ensure the BO is<br /> always fully unmapped when removed from the list. This ensures the BO<br /> is either fully unmapped at context teardown time or present on the<br /> list and unmapped by file_priv_unbind().
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68741
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qla2xxx: Fix improper freeing of purex item<br /> <br /> In qla2xxx_process_purls_iocb(), an item is allocated via<br /> qla27xx_copy_multiple_pkt(), which internally calls<br /> qla24xx_alloc_purex_item().<br /> <br /> The qla24xx_alloc_purex_item() function may return a pre-allocated item<br /> from a per-adapter pool for small allocations, instead of dynamically<br /> allocating memory with kzalloc().<br /> <br /> An error handling path in qla2xxx_process_purls_iocb() incorrectly uses<br /> kfree() to release the item. If the item was from the pre-allocated<br /> pool, calling kfree() on it is a bug that can lead to memory corruption.<br /> <br /> Fix this by using the correct deallocation function,<br /> qla24xx_free_purex_item(), which properly handles both dynamically<br /> allocated and pre-allocated items.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68742
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: Fix invalid prog-&gt;stats access when update_effective_progs fails<br /> <br /> Syzkaller triggers an invalid memory access issue following fault<br /> injection in update_effective_progs. The issue can be described as<br /> follows:<br /> <br /> __cgroup_bpf_detach<br /> update_effective_progs<br /> compute_effective_progs<br /> bpf_prog_array_alloc items[index] = &amp;dummy_bpf_prog.prog<br /> <br /> ---softirq start---<br /> __do_softirq<br /> ...<br /> __cgroup_bpf_run_filter_skb<br /> __bpf_prog_run_save_cb<br /> bpf_prog_run<br /> stats = this_cpu_ptr(prog-&gt;stats)<br /> /* invalid memory access */<br /> flags = u64_stats_update_begin_irqsave(&amp;stats-&gt;syncp)<br /> ---softirq end---<br /> <br /> static_branch_dec(&amp;cgroup_bpf_enabled_key[atype])<br /> <br /> The reason is that fault injection caused update_effective_progs to fail<br /> and then changed the original prog into dummy_bpf_prog.prog in<br /> purge_effective_progs. Then a softirq came, and accessing the members of<br /> dummy_bpf_prog.prog in the softirq triggers invalid mem access.<br /> <br /> To fix it, skip updating stats when stats is NULL.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68743
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mshv: Fix create memory region overlap check<br /> <br /> The current check is incorrect; it only checks if the beginning or end<br /> of a region is within an existing region. This doesn&amp;#39;t account for<br /> userspace specifying a region that begins before and ends after an<br /> existing region.<br /> <br /> Change the logic to a range intersection check against gfns and uaddrs<br /> for each region.<br /> <br /> Remove mshv_partition_region_by_uaddr() as it is no longer used.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68744
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: Free special fields when update [lru_,]percpu_hash maps<br /> <br /> As [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing<br /> calls to &amp;#39;bpf_obj_free_fields()&amp;#39; in &amp;#39;pcpu_copy_value()&amp;#39; could cause the<br /> memory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the<br /> map gets freed.<br /> <br /> Fix this by calling &amp;#39;bpf_obj_free_fields()&amp;#39; after<br /> &amp;#39;copy_map_value[,_long]()&amp;#39; in &amp;#39;pcpu_copy_value()&amp;#39;.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68745
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qla2xxx: Clear cmds after chip reset<br /> <br /> Commit aefed3e5548f ("scsi: qla2xxx: target: Fix offline port handling<br /> and host reset handling") caused two problems:<br /> <br /> 1. Commands sent to FW, after chip reset got stuck and never freed as FW<br /> is not going to respond to them anymore.<br /> <br /> 2. BUG_ON(cmd-&gt;sg_mapped) in qlt_free_cmd(). Commit 26f9ce53817a<br /> ("scsi: qla2xxx: Fix missed DMA unmap for aborted commands")<br /> attempted to fix this, but introduced another bug under different<br /> circumstances when two different CPUs were racing to call<br /> qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in<br /> dma_unmap_sg_attrs().<br /> <br /> So revert "scsi: qla2xxx: Fix missed DMA unmap for aborted commands" and<br /> partially revert "scsi: qla2xxx: target: Fix offline port handling and<br /> host reset handling" at __qla2x00_abort_all_cmds.
Gravedad: Pendiente de análisis
Última modificación:
24/12/2025

CVE-2025-68605
Fecha de publicación:
24/12/2025
Idioma:
Inglés
*** Pendiente de traducción *** Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in PickPlugins Post Grid and Gutenberg Blocks post-grid allows Stored XSS.This issue affects Post Grid and Gutenberg Blocks: from n/a through
Gravedad CVSS v3.1: MEDIA
Última modificación:
24/12/2025
Suscribirse a Vulnerabilidades