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-26920

Publication date:
17/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tracing/trigger: Fix to return error if failed to alloc snapshot<br /> <br /> Fix register_snapshot_trigger() to return error code if it failed to<br /> allocate a snapshot instead of 0 (success). Unless that, it will register<br /> snapshot trigger without an error.
Severity CVSS v4.0: Pending analysis
Last modification:
16/09/2025

CVE-2024-30979

Publication date:
17/04/2024
Cross Site Scripting vulnerability in Cyber Cafe Management System 1.0 allows a remote attacker to execute arbitrary code via the compname parameter in edit-computer-details.php.
Severity CVSS v4.0: Pending analysis
Last modification:
07/04/2025

CVE-2024-31463

Publication date:
17/04/2024
Ironic-image is an OpenStack Ironic deployment packaged and configured by Metal3. When the reverse proxy mode is enabled by the `IRONIC_REVERSE_PROXY_SETUP` variable set to `true`, 1) HTTP basic credentials are validated on the HTTPD side in a separate container, not in the Ironic service itself and 2) Ironic listens in host network on a private port 6388 on localhost by default. As a result, when the reverse proxy mode is used, any Pod or local Unix user on the control plane Node can access the Ironic API on the private port without authentication. A similar problem affects Ironic Inspector (`INSPECTOR_REVERSE_PROXY_SETUP` set to `true`), although the attack potential is smaller there. This issue affects operators deploying ironic-image in the reverse proxy mode, which is the recommended mode when TLS is used (also recommended), with the `IRONIC_PRIVATE_PORT` variable unset or set to a numeric value. In this case, an attacker with enough privileges to launch a pod on the control plane with host networking can access Ironic API and use it to modify bare-metal machine, e.g. provision them with a new image or change their BIOS settings. This vulnerability is fixed in 24.1.1.
Severity CVSS v4.0: Pending analysis
Last modification:
17/04/2024

CVE-2024-32303

Publication date:
17/04/2024
Tenda AC15 v15.03.20_multi, v15.03.05.19, and v15.03.05.18 firmware has a stack overflow vulnerability located via the PPW parameter in the fromWizardHandle function.
Severity CVSS v4.0: Pending analysis
Last modification:
30/06/2025

CVE-2024-32305

Publication date:
17/04/2024
Tenda A18 v15.03.05.05 firmware has a stack overflow vulnerability located via the PPW parameter in the fromWizardHandle function.
Severity CVSS v4.0: Pending analysis
Last modification:
09/04/2025

CVE-2024-32314

Publication date:
17/04/2024
Tenda AC500 V2.0.1.9(1307) firmware contains a command injection vulnerablility in the formexeCommand function via the cmdinput parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
17/03/2025

CVE-2024-26914

Publication date:
17/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: fix incorrect mpc_combine array size<br /> <br /> [why]<br /> MAX_SURFACES is per stream, while MAX_PLANES is per asic. The<br /> mpc_combine is an array that records all the planes per asic. Therefore<br /> MAX_PLANES should be used as the array size. Using MAX_SURFACES causes<br /> array overflow when there are more than 3 planes.<br /> <br /> [how]<br /> Use the MAX_PLANES for the mpc_combine array size.
Severity CVSS v4.0: Pending analysis
Last modification:
25/11/2025

CVE-2023-46060

Publication date:
17/04/2024
A Buffer Overflow vulnerability in Tenda AC500 v.2.0.1.9 allows a remote attacker to cause a denial of service via the port parameter at the goform/setVlanInfo component.
Severity CVSS v4.0: Pending analysis
Last modification:
09/04/2025

CVE-2023-52645

Publication date:
17/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pmdomain: mediatek: fix race conditions with genpd<br /> <br /> If the power domains are registered first with genpd and *after that*<br /> the driver attempts to power them on in the probe sequence, then it is<br /> possible that a race condition occurs if genpd tries to power them on<br /> in the same time.<br /> The same is valid for powering them off before unregistering them<br /> from genpd.<br /> Attempt to fix race conditions by first removing the domains from genpd<br /> and *after that* powering down domains.<br /> Also first power up the domains and *after that* register them<br /> to genpd.
Severity CVSS v4.0: Pending analysis
Last modification:
29/04/2024

CVE-2024-26910

Publication date:
17/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: ipset: fix performance regression in swap operation<br /> <br /> The patch "netfilter: ipset: fix race condition between swap/destroy<br /> and kernel side add/del/test", commit 28628fa9 fixes a race condition.<br /> But the synchronize_rcu() added to the swap function unnecessarily slows<br /> it down: it can safely be moved to destroy and use call_rcu() instead.<br /> <br /> Eric Dumazet pointed out that simply calling the destroy functions as<br /> rcu callback does not work: sets with timeout use garbage collectors<br /> which need cancelling at destroy which can wait. Therefore the destroy<br /> functions are split into two: cancelling garbage collectors safely at<br /> executing the command received by netlink and moving the remaining<br /> part only into the rcu callback.
Severity CVSS v4.0: Pending analysis
Last modification:
05/11/2024

CVE-2024-26911

Publication date:
17/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/buddy: Fix alloc_range() error handling code<br /> <br /> Few users have observed display corruption when they boot<br /> the machine to KDE Plasma or playing games. We have root<br /> caused the problem that whenever alloc_range() couldn&amp;#39;t<br /> find the required memory blocks the function was returning<br /> SUCCESS in some of the corner cases.<br /> <br /> The right approach would be if the total allocated size<br /> is less than the required size, the function should<br /> return -ENOSPC.
Severity CVSS v4.0: Pending analysis
Last modification:
29/04/2024

CVE-2024-26912

Publication date:
17/04/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/nouveau: fix several DMA buffer leaks<br /> <br /> Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects. Several of<br /> these buffers are never dealloced. Some of them can be deallocated<br /> right after GSP-RM is initialized, but the rest need to stay until the<br /> driver unloads.<br /> <br /> Also futher bullet-proof these objects by poisoning the buffer and<br /> clearing the nvkm_gsp_mem object when it is deallocated. Poisoning<br /> the buffer should trigger an error (or crash) from GSP-RM if it tries<br /> to access the buffer after we&amp;#39;ve deallocated it, because we were wrong<br /> about when it is safe to deallocate.<br /> <br /> Finally, change the mem-&gt;size field to a size_t because that&amp;#39;s the same<br /> type that dma_alloc_coherent expects.
Severity CVSS v4.0: Pending analysis
Last modification:
29/04/2024