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

Go to Calendar     Go to Press Room     Go to Newsletters subscription

Search

Vulnerabilities

With the aim of informing, warning and helping professionals with the latest security vulnerabilities in technology systems, we have made a database available for users interested in this information, which is in Spanish and includes all of the latest documented and recognised vulnerabilities.

This repository, with over 75,000 registers, is based on the information from the NVD (National Vulnerability Database) – by virtue of a partnership agreement – through which INCIBE translates the included information into Spanish.

On occasions this list will show vulnerabilities that have still not been translated, as they are added while the INCIBE team is still carrying out the translation process. The CVE  (Common Vulnerabilities and Exposures) Standard for Information Security Vulnerability Names is used with the aim to support the exchange of information between different tools and databases.

All vulnerabilities collected are linked to different information sources, as well as available patches or solutions provided by manufacturers and developers. It is possible to carry out advanced searches, as there is the option to select different criteria to narrow down the results, some examples being vulnerability types, manufacturers and impact levels, among others.

Through RSS feeds or Newsletters we can be informed daily about the latest vulnerabilities added to the repository. Below there is a list, updated daily, where you can discover the latest vulnerabilities.

CVE-2025-37977
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: ufs: exynos: Disable iocc if dma-coherent property isn&amp;#39;t set<br /> <br /> If dma-coherent property isn&amp;#39;t set then descriptors are non-cacheable<br /> and the iocc shareability bits should be disabled. Without this UFS can<br /> end up in an incompatible configuration and suffer from random cache<br /> related stability issues.
Severity CVSS v4.0: Pending analysis
Last modification:
14/11/2025

CVE-2025-37978
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block: integrity: Do not call set_page_dirty_lock()<br /> <br /> Placing multiple protection information buffers inside the same page<br /> can lead to oopses because set_page_dirty_lock() can&amp;#39;t be called from<br /> interrupt context.<br /> <br /> Since a protection information buffer is not backed by a file there is<br /> no point in setting its page dirty, there is nothing to synchronize.<br /> Drop the call to set_page_dirty_lock() and remove the last argument to<br /> bio_integrity_unpin_bvec().
Severity CVSS v4.0: Pending analysis
Last modification:
14/11/2025

CVE-2025-37979
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: qcom: Fix sc7280 lpass potential buffer overflow<br /> <br /> Case values introduced in commit<br /> 5f78e1fb7a3e ("ASoC: qcom: Add driver support for audioreach solution")<br /> cause out of bounds access in arrays of sc7280 driver data (e.g. in case<br /> of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).<br /> <br /> Redefine LPASS_MAX_PORTS to consider the maximum possible port id for<br /> q6dsp as sc7280 driver utilizes some of those values.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE.
Severity CVSS v4.0: Pending analysis
Last modification:
16/12/2025

CVE-2025-37980
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block: fix resource leak in blk_register_queue() error path<br /> <br /> When registering a queue fails after blk_mq_sysfs_register() is<br /> successful but the function later encounters an error, we need<br /> to clean up the blk_mq_sysfs resources.<br /> <br /> Add the missing blk_mq_sysfs_unregister() call in the error path<br /> to properly clean up these resources and prevent a memory leak.
Severity CVSS v4.0: Pending analysis
Last modification:
11/04/2026

CVE-2025-37981
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: smartpqi: Use is_kdump_kernel() to check for kdump<br /> <br /> The smartpqi driver checks the reset_devices variable to determine<br /> whether special adjustments need to be made for kdump. This has the<br /> effect that after a regular kexec reboot, some driver parameters such as<br /> max_transfer_size are much lower than usual. More importantly, kexec<br /> reboot tests have revealed memory corruption caused by the driver log<br /> being written to system memory after a kexec.<br /> <br /> Fix this by testing is_kdump_kernel() rather than reset_devices where<br /> appropriate.
Severity CVSS v4.0: Pending analysis
Last modification:
14/11/2025

CVE-2025-37982
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: wl1251: fix memory leak in wl1251_tx_work<br /> <br /> The skb dequeued from tx_queue is lost when wl1251_ps_elp_wakeup fails<br /> with a -ETIMEDOUT error. Fix that by queueing the skb back to tx_queue.
Severity CVSS v4.0: Pending analysis
Last modification:
16/12/2025

CVE-2025-37966
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL<br /> <br /> When userspace does PR_SET_TAGGED_ADDR_CTRL, but Supm extension is not<br /> available, the kernel crashes:<br /> <br /> Oops - illegal instruction [#1]<br /> [snip]<br /> epc : set_tagged_addr_ctrl+0x112/0x15a<br /> ra : set_tagged_addr_ctrl+0x74/0x15a<br /> epc : ffffffff80011ace ra : ffffffff80011a30 sp : ffffffc60039be10<br /> [snip]<br /> status: 0000000200000120 badaddr: 0000000010a79073 cause: 0000000000000002<br /> set_tagged_addr_ctrl+0x112/0x15a<br /> __riscv_sys_prctl+0x352/0x73c<br /> do_trap_ecall_u+0x17c/0x20c<br /> andle_exception+0x150/0x15c<br /> <br /> Fix it by checking if Supm is available.
Severity CVSS v4.0: Pending analysis
Last modification:
17/03/2026

CVE-2025-37967
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: typec: ucsi: displayport: Fix deadlock<br /> <br /> This patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock<br /> functions to the UCSI driver. ucsi_con_mutex_lock ensures the connector<br /> mutex is only locked if a connection is established and the partner pointer<br /> is valid. This resolves a deadlock scenario where<br /> ucsi_displayport_remove_partner holds con-&gt;mutex waiting for<br /> dp_altmode_work to complete while dp_altmode_work attempts to acquire it.
Severity CVSS v4.0: Pending analysis
Last modification:
16/12/2025

CVE-2025-37968
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: light: opt3001: fix deadlock due to concurrent flag access<br /> <br /> The threaded IRQ function in this driver is reading the flag twice: once to<br /> lock a mutex and once to unlock it. Even though the code setting the flag<br /> is designed to prevent it, there are subtle cases where the flag could be<br /> true at the mutex_lock stage and false at the mutex_unlock stage. This<br /> results in the mutex not being unlocked, resulting in a deadlock.<br /> <br /> Fix it by making the opt3001_irq() code generally more robust, reading the<br /> flag into a variable and using the variable value at both stages.
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026

CVE-2025-37969
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_tagged_fifo<br /> <br /> Prevent st_lsm6dsx_read_tagged_fifo from falling in an infinite loop in<br /> case pattern_len is equal to zero and the device FIFO is not empty.
Severity CVSS v4.0: Pending analysis
Last modification:
16/12/2025

CVE-2025-37970
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo<br /> <br /> Prevent st_lsm6dsx_read_fifo from falling in an infinite loop in case<br /> pattern_len is equal to zero and the device FIFO is not empty.
Severity CVSS v4.0: Pending analysis
Last modification:
16/12/2025

CVE-2025-37971
Publication date:
20/05/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> staging: bcm2835-camera: Initialise dev in v4l2_dev<br /> <br /> Commit 42a2f6664e18 ("staging: vc04_services: Move global g_state to<br /> vchiq_state") changed mmal_init to pass dev-&gt;v4l2_dev.dev to<br /> vchiq_mmal_init, however nothing iniitialised dev-&gt;v4l2_dev, so we got<br /> a NULL pointer dereference.<br /> <br /> Set dev-&gt;v4l2_dev.dev during bcm2835_mmal_probe. The device pointer<br /> could be passed into v4l2_device_register to set it, however that also<br /> has other effects that would need additional changes.
Severity CVSS v4.0: Pending analysis
Last modification:
14/11/2025
Subscribe to Vulnerabilities