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-2026-63860
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/core: Prefer NLA_NUL_STRING<br /> <br /> These attributes are evaluated as c-string (passed to strcmp), but<br /> NLA_STRING doesn&amp;#39;t check for the presence of a \0 terminator.<br /> <br /> Either this needs to switch to nla_strcmp() and needs to adjust printf fmt<br /> specifier to not use plain %s, or this needs to use NLA_NUL_STRING.<br /> <br /> As the code has been this way for long time, it seems to me that userspace<br /> does include the terminating nul, even tough its not enforced so far, and<br /> thus NLA_NUL_STRING use is the simpler solution.
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63861
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback<br /> <br /> mtk_snand_probe() registers the on-host NAND ECC engine, but teardown was<br /> missing from both probe unwind and remove-time cleanup. Add a devm cleanup<br /> action after successful registration so<br /> nand_ecc_unregister_on_host_hw_engine() runs automatically on probe<br /> failures and during device removal.
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63843
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring<br /> <br /> JPEG rings do not support 64-bit user fence writes, reject CS<br /> submissions with user fences.<br /> <br /> (cherry picked from commit f05d0a4f21fc720116d6e238f23308b199891058)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63844
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring<br /> <br /> JPEG rings do not support 64-bit user fence writes, reject CS<br /> submissions with user fences.<br /> <br /> (cherry picked from commit 2f6afc97d259d530f4f86c7743efbc573a8da927)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63845
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring<br /> <br /> JPEG rings do not support 64-bit user fence writes, reject CS<br /> submissions with user fences.<br /> <br /> (cherry picked from commit 8d0cac9478a3f046279c657d6a2545de49ae675a)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63846
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring<br /> <br /> JPEG rings do not support 64-bit user fence writes, reject CS<br /> submissions with user fences.<br /> <br /> (cherry picked from commit 4d7d774f100efb5089c86a1fb8c5bf47c63fc9ef)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63847
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring<br /> <br /> JPEG rings do not support 64-bit user fence writes, reject CS<br /> submissions with user fences.<br /> <br /> (cherry picked from commit 3216a7f4e2642bda5fd14f57586e835ae9202587)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63848
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring<br /> <br /> JPEG rings do not support 64-bit user fence writes, reject CS<br /> submissions with user fences.<br /> <br /> (cherry picked from commit 96179da0c6b059eb31706a0abe8dd6381c533143)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63849
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/vcn: set no_user_fence for VCN v5.0.1 enc ring<br /> <br /> VCN encoder and decoder rings do not support 64-bit user fence writes,<br /> reject CS submissions with user fences.<br /> <br /> (cherry picked from commit e16be95a2c3ee712b142cb27d2dca0b461181359)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63850
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring<br /> <br /> VCN encoder and decoder rings do not support 64-bit user fence writes,<br /> reject CS submissions with user fences.<br /> <br /> (cherry picked from commit 49b1fbbb5a071197ee71e2d70959b1cb29bdc317)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63851
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring<br /> <br /> VCN encoder and decoder rings do not support 64-bit user fence writes,<br /> reject CS submissions with user fences.<br /> <br /> (cherry picked from commit 084d94ac93707bdda07efb5cee786f632de4219b)
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026

CVE-2026-63837
Publication date:
19/07/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: ena: PHC: Check return code before setting timestamp output<br /> <br /> ena_phc_gettimex64() is setting the output parameter regardless<br /> of whether ena_com_phc_get_timestamp() succeeded or failed.<br /> <br /> When ena_com_phc_get_timestamp() returns an error, the timestamp<br /> parameter may contain uninitialized stack memory (e.g., when PHC is<br /> disabled or in blocked state) or invalid hardware values. Passing<br /> these to userspace via the PTP ioctl is both a security issue<br /> (information leak) and a correctness bug.<br /> <br /> Fix by checking the return code after releasing the lock and only<br /> setting the output timestamp on success.
Severity CVSS v4.0: Pending analysis
Last modification:
27/07/2026
Subscribe to Vulnerabilities