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 últimas 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 últimas 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 últimas vulnerabilidades incorporadas al repositorio.

CVE-2026-43359
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> btrfs: fix transaction abort on set received ioctl due to item overflow<br /> <br /> If the set received ioctl fails due to an item overflow when attempting to<br /> add the BTRFS_UUID_KEY_RECEIVED_SUBVOL we have to abort the transaction<br /> since we did some metadata updates before.<br /> <br /> This means that if a user calls this ioctl with the same received UUID<br /> field for a lot of subvolumes, we will hit the overflow, trigger the<br /> transaction abort and turn the filesystem into RO mode. A malicious user<br /> could exploit this, and this ioctl does not even requires that a user<br /> has admin privileges (CAP_SYS_ADMIN), only that he/she owns the subvolume.<br /> <br /> Fix this by doing an early check for item overflow before starting a<br /> transaction. This is also race safe because we are holding the subvol_sem<br /> semaphore in exclusive (write) mode.<br /> <br /> A test case for fstests will follow soon.
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43355
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: light: bh1780: fix PM runtime leak on error path<br /> <br /> Move pm_runtime_put_autosuspend() before the error check to ensure<br /> the PM runtime reference count is always decremented after<br /> pm_runtime_get_sync(), regardless of whether the read operation<br /> succeeds or fails.
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43356
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: imu: adis: Fix NULL pointer dereference in adis_init<br /> <br /> The adis_init() function dereferences adis-&gt;ops to check if the<br /> individual function pointers (write, read, reset) are NULL, but does<br /> not first check if adis-&gt;ops itself is NULL.<br /> <br /> Drivers like adis16480, adis16490, adis16545 and others do not set<br /> custom ops and rely on adis_init() assigning the defaults. Since struct<br /> adis is zero-initialized by devm_iio_device_alloc(), adis-&gt;ops is NULL<br /> when adis_init() is called, causing a NULL pointer dereference:<br /> <br /> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000<br /> pc : adis_init+0xc0/0x118<br /> Call trace:<br /> adis_init+0xc0/0x118<br /> adis16480_probe+0xe0/0x670<br /> <br /> Fix this by checking if adis-&gt;ops is NULL before dereferencing it,<br /> falling through to assign the default ops in that case.
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43357
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: gyro: mpu3050-core: fix pm_runtime error handling<br /> <br /> The return value of pm_runtime_get_sync() is not checked, allowing<br /> the driver to access hardware that may fail to resume. The device<br /> usage count is also unconditionally incremented. Use<br /> pm_runtime_resume_and_get() which propagates errors and avoids<br /> incrementing the usage count on failure.<br /> <br /> In preenable, add pm_runtime_put_autosuspend() on set_8khz_samplerate()<br /> failure since postdisable does not run when preenable fails.
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43358
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> btrfs: add missing RCU unlock in error path in try_release_subpage_extent_buffer()<br /> <br /> Call rcu_read_lock() before exiting the loop in<br /> try_release_subpage_extent_buffer() because there is a rcu_read_unlock()<br /> call past the loop.<br /> <br /> This has been detected by the Clang thread-safety analyzer.
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43354
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: proximity: hx9023s: Protect against division by zero in set_samp_freq<br /> <br /> Avoid division by zero when sampling frequency is unspecified.
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43353
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> i3c: mipi-i3c-hci: Fix race in DMA ring dequeue<br /> <br /> The HCI DMA dequeue path (hci_dma_dequeue_xfer()) may be invoked for<br /> multiple transfers that timeout around the same time. However, the<br /> function is not serialized and can race with itself.<br /> <br /> When a timeout occurs, hci_dma_dequeue_xfer() stops the ring, processes<br /> incomplete transfers, and then restarts the ring. If another timeout<br /> triggers a parallel call into the same function, the two instances may<br /> interfere with each other - stopping or restarting the ring at unexpected<br /> times.<br /> <br /> Add a mutex so that hci_dma_dequeue_xfer() is serialized with respect to<br /> itself.
Gravedad CVSS v3.1: ALTA
Última modificación:
15/05/2026

CVE-2026-43351
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KVM: arm64: Eagerly init vgic dist/redist on vgic creation<br /> <br /> If vgic_allocate_private_irqs_locked() fails for any odd reason,<br /> we exit kvm_vgic_create() early, leaving dist-&gt;rd_regions uninitialised.<br /> <br /> kvm_vgic_dist_destroy() then comes along and walks into the weeds<br /> trying to free the RDs. Got to love this stuff.<br /> <br /> Solve it by moving all the static initialisation early, and make<br /> sure that if we fail halfway, we&amp;#39;re in a reasonable shape to<br /> perform the rest of the teardown. While at it, reset the vgic model<br /> on failure, just in case...
Gravedad CVSS v3.1: MEDIA
Última modificación:
15/05/2026

CVE-2026-43352
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> i3c: mipi-i3c-hci: Correct RING_CTRL_ABORT handling in DMA dequeue<br /> <br /> The logic used to abort the DMA ring contains several flaws:<br /> <br /> 1. The driver unconditionally issues a ring abort even when the ring has<br /> already stopped.<br /> 2. The completion used to wait for abort completion is never<br /> re-initialized, resulting in incorrect wait behavior.<br /> 3. The abort sequence unintentionally clears RING_CTRL_ENABLE, which<br /> resets hardware ring pointers and disrupts the controller state.<br /> 4. If the ring is already stopped, the abort operation should be<br /> considered successful without attempting further action.<br /> <br /> Fix the abort handling by checking whether the ring is running before<br /> issuing an abort, re-initializing the completion when needed, ensuring that<br /> RING_CTRL_ENABLE remains asserted during abort, and treating an already<br /> stopped ring as a successful condition.
Gravedad CVSS v3.1: ALTA
Última modificación:
15/05/2026

CVE-2026-41588
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** RELATE is a web-based courseware package. Prior to commit 2f68e16, there is a timing attack vulnerability in course/auth.py — check_sign_in_key(). This issue has been patched via commit 2f68e16.
Gravedad CVSS v3.1: CRÍTICA
Última modificación:
12/05/2026

CVE-2026-41585
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** ZEBRA is a Zcash node written entirely in Rust. From zebrad versions 2.2.0 to before 4.3.1 and from zebra-rpc versions 1.0.0-beta.45 to before 6.0.2, a vulnerability in Zebra&amp;#39;s JSON-RPC HTTP middleware allows an authenticated RPC client to cause a Zebra node to crash by disconnecting before the request body is fully received. The node treats the failure to read the HTTP request body as an unrecoverable error and aborts the process instead of returning an error response. This issue has been patched in zebrad version 4.3.1 and zebra-rpc version 6.0.2.
Gravedad CVSS v4.0: MEDIA
Última modificación:
08/05/2026

CVE-2026-41584
Fecha de publicación:
08/05/2026
Idioma:
Inglés
*** Pendiente de traducción *** ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-chain version 6.0.2, Orchard transactions contain a rk field which is a randomized validating key and also an elliptic curve point. The Zcash specification allows the field to be the identity (a "zero" value), however, the orchard crate which is used to verify Orchard proofs would panic when fed a rk with the identity value. Thus an attacker could send a crafted transaction that would make a Zebra node crash. This issue has been patched in zebrad version 4.3.1 and zebra-chain version 6.0.2.
Gravedad CVSS v4.0: CRÍTICA
Última modificación:
08/05/2026
Suscribirse a Vulnerabilidades