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

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: sl811: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53418

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: gadget: lpc32xx_udc: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53406

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: gadget: pxa25x_udc: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53407

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: gadget: pxa27x_udc: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53408

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> trace/blktrace: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53409

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drivers: base: component: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53410

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: ULPI: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53411

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> PM: EM: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53412

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53413

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> USB: isp116x: fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic<br /> at once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53414

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: snic: Fix memory leak with using debugfs_lookup()<br /> <br /> When calling debugfs_lookup() the result must have dput() called on it,<br /> otherwise the memory will leak over time. To make things simpler, just<br /> call debugfs_lookup_and_remove() instead which handles all of the logic at<br /> once.
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025

CVE-2023-53398

Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mlx5: fix possible ptp queue fifo use-after-free<br /> <br /> Fifo indexes are not checked during pop operations and it leads to<br /> potential use-after-free when poping from empty queue. Such case was<br /> possible during re-sync action. WARN_ON_ONCE covers future cases.<br /> <br /> There were out-of-order cqe spotted which lead to drain of the queue and<br /> use-after-free because of lack of fifo pointers check. Special check and<br /> counter are added to avoid resync operation if SKB could not exist in the<br /> fifo because of OOO cqe (skb_id must be between consumer and producer<br /> index).
Severity CVSS v4.0: Pending analysis
Last modification:
19/09/2025