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-2022-50399
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: atomisp: prevent integer overflow in sh_css_set_black_frame()<br /> <br /> The "height" and "width" values come from the user so the "height * width"<br /> multiplication can overflow.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2022-50400
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> staging: greybus: audio_helper: remove unused and wrong debugfs usage<br /> <br /> In the greybus audio_helper code, the debugfs file for the dapm has the<br /> potential to be removed and memory will be leaked. There is also the<br /> very real potential for this code to remove ALL debugfs entries from the<br /> system, and it seems like this is what will really happen if this code<br /> ever runs. This all is very wrong as the greybus audio driver did not<br /> create this debugfs file, the sound core did and controls the lifespan<br /> of it.<br /> <br /> So remove all of the debugfs logic from the audio_helper code as there&amp;#39;s<br /> no way it could be correct. If this really is needed, it can come back<br /> with a fixup for the incorrect usage of the debugfs_lookup() call which<br /> is what caused this to be noticed at all.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2023-53369
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: dcb: choose correct policy to parse DCB_ATTR_BCN<br /> <br /> The dcbnl_bcn_setcfg uses erroneous policy to parse tb[DCB_ATTR_BCN],<br /> which is introduced in commit 859ee3c43812 ("DCB: Add support for DCB<br /> BCN"). Please see the comment in below code<br /> <br /> static int dcbnl_bcn_setcfg(...)<br /> {<br /> ...<br /> ret = nla_parse_nested_deprecated(..., dcbnl_pfc_up_nest, .. )<br /> // !!! dcbnl_pfc_up_nest for attributes<br /> // DCB_PFC_UP_ATTR_0 to DCB_PFC_UP_ATTR_ALL in enum dcbnl_pfc_up_attrs<br /> ...<br /> for (i = DCB_BCN_ATTR_RP_0; i
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2023-53370
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: fix memory leak in mes self test<br /> <br /> The fences associated with mes queue have to be freed<br /> up during amdgpu_ring_fini.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2023-53371
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/mlx5e: fix memory leak in mlx5e_fs_tt_redirect_any_create<br /> <br /> The memory pointed to by the fs-&gt;any pointer is not freed in the error<br /> path of mlx5e_fs_tt_redirect_any_create, which can lead to a memory leak.<br /> Fix by freeing the memory in the error path, thereby making the error path<br /> identical to mlx5e_fs_tt_redirect_any_destroy().
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2023-53372
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> sctp: fix a potential overflow in sctp_ifwdtsn_skip<br /> <br /> Currently, when traversing ifwdtsn skips with _sctp_walk_ifwdtsn, it only<br /> checks the pos against the end of the chunk. However, the data left for<br /> the last pos may be
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2023-53373
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: seqiv - Handle EBUSY correctly<br /> <br /> As it is seqiv only handles the special return value of EINPROGERSS,<br /> which means that in all other cases it will free data related to the<br /> request.<br /> <br /> However, as the caller of seqiv may specify MAY_BACKLOG, we also need<br /> to expect EBUSY and treat it in the same way. Otherwise backlogged<br /> requests will trigger a use-after-free.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2022-50391
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mm/mempolicy: fix memory leak in set_mempolicy_home_node system call<br /> <br /> When encountering any vma in the range with policy other than MPOL_BIND or<br /> MPOL_PREFERRED_MANY, an error is returned without issuing a mpol_put on<br /> the policy just allocated with mpol_dup().<br /> <br /> This allows arbitrary users to leak kernel memory.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2022-50392
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: mediatek: mt8183: fix refcount leak in mt8183_mt6358_ts3a227_max98357_dev_probe()<br /> <br /> The node returned by of_parse_phandle() with refcount incremented,<br /> of_node_put() needs be called when finish using it. So add it in the<br /> error path in mt8183_mt6358_ts3a227_max98357_dev_probe().
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2022-50393
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: SDMA update use unlocked iterator<br /> <br /> SDMA update page table may be called from unlocked context, this<br /> generate below warning. Use unlocked iterator to handle this case.<br /> <br /> WARNING: CPU: 0 PID: 1475 at<br /> drivers/dma-buf/dma-resv.c:483 dma_resv_iter_next<br /> Call Trace:<br /> dma_resv_iter_first+0x43/0xa0<br /> amdgpu_vm_sdma_update+0x69/0x2d0 [amdgpu]<br /> amdgpu_vm_ptes_update+0x29c/0x870 [amdgpu]<br /> amdgpu_vm_update_range+0x2f6/0x6c0 [amdgpu]<br /> svm_range_unmap_from_gpus+0x115/0x300 [amdgpu]<br /> svm_range_cpu_invalidate_pagetables+0x510/0x5e0 [amdgpu]<br /> __mmu_notifier_invalidate_range_start+0x1d3/0x230<br /> unmap_vmas+0x140/0x150<br /> unmap_region+0xa8/0x110
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2022-50394
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> i2c: ismt: Fix an out-of-bounds bug in ismt_access()<br /> <br /> When the driver does not check the data from the user, the variable<br /> &amp;#39;data-&gt;block[0]&amp;#39; may be very large to cause an out-of-bounds bug.<br /> <br /> The following log can reveal it:<br /> <br /> [ 33.995542] i2c i2c-1: ioctl, cmd=0x720, arg=0x7ffcb3dc3a20<br /> [ 33.995978] ismt_smbus 0000:00:05.0: I2C_SMBUS_BLOCK_DATA: WRITE<br /> [ 33.996475] ==================================================================<br /> [ 33.996995] BUG: KASAN: out-of-bounds in ismt_access.cold+0x374/0x214b<br /> [ 33.997473] Read of size 18446744073709551615 at addr ffff88810efcfdb1 by task ismt_poc/485<br /> [ 33.999450] Call Trace:<br /> [ 34.001849] memcpy+0x20/0x60<br /> [ 34.002077] ismt_access.cold+0x374/0x214b<br /> [ 34.003382] __i2c_smbus_xfer+0x44f/0xfb0<br /> [ 34.004007] i2c_smbus_xfer+0x10a/0x390<br /> [ 34.004291] i2cdev_ioctl_smbus+0x2c8/0x710<br /> [ 34.005196] i2cdev_ioctl+0x5ec/0x74c<br /> <br /> Fix this bug by checking the size of &amp;#39;data-&gt;block[0]&amp;#39; first.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025

CVE-2022-50395
Publication date:
18/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> integrity: Fix memory leakage in keyring allocation error path<br /> <br /> Key restriction is allocated in integrity_init_keyring(). However, if<br /> keyring allocation failed, it is not freed, causing memory leaks.
Severity CVSS v4.0: Pending analysis
Last modification:
18/09/2025
Subscribe to Vulnerabilities