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-2024-27047

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: phy: fix phy_get_internal_delay accessing an empty array<br /> <br /> The phy_get_internal_delay function could try to access to an empty<br /> array in the case that the driver is calling phy_get_internal_delay<br /> without defining delay_values and rx-internal-delay-ps or<br /> tx-internal-delay-ps is defined to 0 in the device-tree.<br /> This will lead to "unable to handle kernel NULL pointer dereference at<br /> virtual address 0". To avoid this kernel oops, the test should be delay<br /> &gt;= 0. As there is already delay
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026

CVE-2024-27048

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: brcm80211: handle pmk_op allocation failure<br /> <br /> The kzalloc() in brcmf_pmksa_v3_op() will return null if the<br /> physical memory has run out. As a result, if we dereference<br /> the null value, the null pointer dereference bug will happen.<br /> <br /> Return -ENOMEM from brcmf_pmksa_v3_op() if kzalloc() fails<br /> for pmk_op.
Severity CVSS v4.0: Pending analysis
Last modification:
23/12/2024

CVE-2024-27028

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> spi: spi-mt65xx: Fix NULL pointer access in interrupt handler<br /> <br /> The TX buffer in spi_transfer can be a NULL pointer, so the interrupt<br /> handler may end up writing to the invalid memory and cause crashes.<br /> <br /> Add a check to trans-&gt;tx_buf before using it.
Severity CVSS v4.0: Pending analysis
Last modification:
08/04/2025

CVE-2024-27029

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: fix mmhub client id out-of-bounds access<br /> <br /> Properly handle cid 0x140.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-27030

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> octeontx2-af: Use separate handlers for interrupts<br /> <br /> For PF to AF interrupt vector and VF to AF vector same<br /> interrupt handler is registered which is causing race condition.<br /> When two interrupts are raised to two CPUs at same time<br /> then two cores serve same event corrupting the data.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-27034

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: compress: fix to cover normal cluster write with cp_rwsem<br /> <br /> When we overwrite compressed cluster w/ normal cluster, we should<br /> not unlock cp_rwsem during f2fs_write_raw_pages(), otherwise data<br /> will be corrupted if partial blocks were persisted before CP &amp; SPOR,<br /> due to cluster metadata wasn&amp;#39;t updated atomically.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-27035

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: compress: fix to guarantee persisting compressed blocks by CP<br /> <br /> If data block in compressed cluster is not persisted with metadata<br /> during checkpoint, after SPOR, the data may be corrupted, let&amp;#39;s<br /> guarantee to write compressed page by checkpoint.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-27043

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: edia: dvbdev: fix a use-after-free<br /> <br /> In dvb_register_device, *pdvbdev is set equal to dvbdev, which is freed<br /> in several error-handling paths. However, *pdvbdev is not set to NULL<br /> after dvbdev&amp;#39;s deallocation, causing use-after-frees in many places,<br /> for example, in the following call chain:<br /> <br /> budget_register<br /> |-&gt; dvb_dmxdev_init<br /> |-&gt; dvb_register_device<br /> |-&gt; dvb_dmxdev_release<br /> |-&gt; dvb_unregister_device<br /> |-&gt; dvb_remove_device<br /> |-&gt; dvb_device_put<br /> |-&gt; kref_put<br /> <br /> When calling dvb_unregister_device, dmxdev-&gt;dvbdev (i.e. *pdvbdev in<br /> dvb_register_device) could point to memory that had been freed in<br /> dvb_register_device. Thereafter, this pointer is transferred to<br /> kref_put and triggering a use-after-free.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-27045

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Fix a potential buffer overflow in &amp;#39;dp_dsc_clock_en_read()&amp;#39;<br /> <br /> Tell snprintf() to store at most 10 bytes in the output buffer<br /> instead of 30.<br /> <br /> Fixes the below:<br /> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_debugfs.c:1508 dp_dsc_clock_en_read() error: snprintf() is printing too much 30 vs 10
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2022-48669

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc/pseries: Fix potential memleak in papr_get_attr()<br /> <br /> `buf` is allocated in papr_get_attr(), and krealloc() of `buf`<br /> could fail. We need to free the original `buf` in the case of failure.
Severity CVSS v4.0: Pending analysis
Last modification:
08/04/2025

CVE-2023-52649

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/vkms: Avoid reading beyond LUT array<br /> <br /> When the floor LUT index (drm_fixp2int(lut_index) is the last<br /> index of the array the ceil LUT index will point to an entry<br /> beyond the array. Make sure we guard against it and use the<br /> value of the floor LUT index.<br /> <br /> v3:<br /> - Drop bits from commit description that didn&amp;#39;t contribute<br /> anything of value
Severity CVSS v4.0: Pending analysis
Last modification:
23/12/2024

CVE-2023-52650

Publication date:
01/05/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/tegra: dsi: Add missing check for of_find_device_by_node<br /> <br /> Add check for the return value of of_find_device_by_node() and return<br /> the error if it fails in order to avoid NULL pointer dereference.
Severity CVSS v4.0: Pending analysis
Last modification:
23/12/2024