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-2023-52694
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/bridge: tpd12s015: Drop buggy __exit annotation for remove function<br /> <br /> With tpd12s015_remove() marked with __exit this function is discarded<br /> when the driver is compiled as a built-in. The result is that when the<br /> driver unbinds there is no cleanup done which results in resource<br /> leakage or worse.
Severity CVSS v4.0: Pending analysis
Last modification:
17/12/2025

CVE-2023-52693
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ACPI: video: check for error while searching for backlight device parent<br /> <br /> If acpi_get_parent() called in acpi_video_dev_register_backlight()<br /> fails, for example, because acpi_ut_acquire_mutex() fails inside<br /> acpi_get_parent), this can lead to incorrect (uninitialized)<br /> acpi_parent handle being passed to acpi_get_pci_dev() for detecting<br /> the parent pci device.<br /> <br /> Check acpi_get_parent() result and set parent device only in case of success.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE.
Severity CVSS v4.0: Pending analysis
Last modification:
17/12/2025

CVE-2023-52678
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdkfd: Confirm list is non-empty before utilizing list_first_entry in kfd_topology.c<br /> <br /> Before using list_first_entry, make sure to check that list is not<br /> empty, if list is empty return -ENODATA.<br /> <br /> Fixes the below:<br /> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:1347 kfd_create_indirect_link_prop() warn: can &amp;#39;gpu_link&amp;#39; even be NULL?<br /> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:1428 kfd_add_peer_prop() warn: can &amp;#39;iolink1&amp;#39; even be NULL?<br /> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:1433 kfd_add_peer_prop() warn: can &amp;#39;iolink2&amp;#39; even be NULL?
Severity CVSS v4.0: Pending analysis
Last modification:
25/09/2025

CVE-2023-52679
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> of: Fix double free in of_parse_phandle_with_args_map<br /> <br /> In of_parse_phandle_with_args_map() the inner loop that<br /> iterates through the map entries calls of_node_put(new)<br /> to free the reference acquired by the previous iteration<br /> of the inner loop. This assumes that the value of "new" is<br /> NULL on the first iteration of the inner loop.<br /> <br /> Make sure that this is true in all iterations of the outer<br /> loop by setting "new" to NULL after its value is assigned to "cur".<br /> <br /> Extend the unittest to detect the double free and add an additional<br /> test case that actually triggers this path.
Severity CVSS v4.0: Pending analysis
Last modification:
10/01/2025

CVE-2023-52680
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ALSA: scarlett2: Add missing error checks to *_ctl_get()<br /> <br /> The *_ctl_get() functions which call scarlett2_update_*() were not<br /> checking the return value. Fix to check the return value and pass to<br /> the caller.
Severity CVSS v4.0: Pending analysis
Last modification:
25/09/2025

CVE-2023-52681
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> efivarfs: Free s_fs_info on unmount<br /> <br /> Now that we allocate a s_fs_info struct on fs context creation, we<br /> should ensure that we free it again when the superblock goes away.
Severity CVSS v4.0: Pending analysis
Last modification:
25/09/2025

CVE-2023-52682
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to wait on block writeback for post_read case<br /> <br /> If inode is compressed, but not encrypted, it missed to call<br /> f2fs_wait_on_block_writeback() to wait for GCed page writeback<br /> in IPU write path.<br /> <br /> Thread A GC-Thread<br /> - f2fs_gc<br /> - do_garbage_collect<br /> - gc_data_segment<br /> - move_data_block<br /> - f2fs_submit_page_write<br /> migrate normal cluster&amp;#39;s block via<br /> meta_inode&amp;#39;s page cache<br /> - f2fs_write_single_data_page<br /> - f2fs_do_write_data_page<br /> - f2fs_inplace_write_data<br /> - f2fs_submit_page_bio<br /> <br /> IRQ<br /> - f2fs_read_end_io<br /> IRQ<br /> old data overrides new data due to<br /> out-of-order GC and common IO.<br /> - f2fs_read_end_io
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-52684
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> firmware: qcom: qseecom: fix memory leaks in error paths<br /> <br /> Fix instances of returning error codes directly instead of jumping to<br /> the relevant labels where memory allocated for the SCM calls would be<br /> freed.
Severity CVSS v4.0: Pending analysis
Last modification:
07/04/2025

CVE-2023-52685
Publication date:
17/05/2024
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Severity CVSS v4.0: Pending analysis
Last modification:
18/06/2024

CVE-2023-52686
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc/powernv: Add a null pointer check in opal_event_init()<br /> <br /> kasprintf() returns a pointer to dynamically allocated memory<br /> which can be NULL upon failure.
Severity CVSS v4.0: Pending analysis
Last modification:
04/11/2024

CVE-2023-52687
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: safexcel - Add error handling for dma_map_sg() calls<br /> <br /> Macro dma_map_sg() may return 0 on error. This patch enables<br /> checks in case of the macro failure and ensures unmapping of<br /> previously mapped buffers with dma_unmap_sg().<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with static<br /> analysis tool SVACE.
Severity CVSS v4.0: Pending analysis
Last modification:
25/09/2025

CVE-2023-52688
Publication date:
17/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: ath12k: fix the error handler of rfkill config<br /> <br /> When the core rfkill config throws error, it should free the<br /> allocated resources. Currently it is not freeing the core pdev<br /> create resources. Avoid this issue by calling the core pdev<br /> destroy in the error handler of core rfkill config.<br /> <br /> Found this issue in the code review and it is compile tested only.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025
Subscribe to Vulnerabilities