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-50867
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage<br /> <br /> adreno_show_object() is a trap! It will re-allocate the pointer it is<br /> passed on first call, when the data is ascii85 encoded, using kvmalloc/<br /> kvfree(). Which means the data *passed* to it must be kvmalloc&amp;#39;d, ie.<br /> we cannot use the state_kcalloc() helper.<br /> <br /> This partially reverts commit ec8f1813bf8d ("drm/msm/a6xx: Replace<br /> kcalloc() with kvzalloc()"), but adds the missing kvfree() to fix the<br /> memory leak that was present previously. And adds a warning comment.<br /> <br /> Patchwork: https://patchwork.freedesktop.org/patch/507014/
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50868
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hwrng: amd - Fix PCI device refcount leak<br /> <br /> for_each_pci_dev() is implemented by pci_get_device(). The comment of<br /> pci_get_device() says that it will increase the reference count for the<br /> returned pci_dev and also decrease the reference count for the input<br /> pci_dev @from if it is not NULL.<br /> <br /> If we break for_each_pci_dev() loop with pdev not NULL, we need to call<br /> pci_dev_put() to decrease the reference count. Add the missing<br /> pci_dev_put() for the normal and error path.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50869
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Fix slab-out-of-bounds in r_page<br /> <br /> When PAGE_SIZE is 64K, if read_log_page is called by log_read_rst for<br /> the first time, the size of *buffer would be equal to<br /> DefaultLogPageSize(4K).But for *buffer operations like memcpy,<br /> if the memory area size(n) which being assigned to buffer is larger<br /> than 4K (log-&gt;page_size(64K) or bytes(64K-page_off)), it will cause<br /> an out of boundary error.<br /> Call trace:<br /> [...]<br /> kasan_report+0x44/0x130<br /> check_memory_region+0xf8/0x1a0<br /> memcpy+0xc8/0x100<br /> ntfs_read_run_nb+0x20c/0x460<br /> read_log_page+0xd0/0x1f4<br /> log_read_rst+0x110/0x75c<br /> log_replay+0x1e8/0x4aa0<br /> ntfs_loadlog_and_replay+0x290/0x2d0<br /> ntfs_fill_super+0x508/0xec0<br /> get_tree_bdev+0x1fc/0x34c<br /> [...]<br /> <br /> Fix this by setting variable r_page to NULL in log_read_rst.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50870
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc/rtas: avoid device tree lookups in rtas_os_term()<br /> <br /> rtas_os_term() is called during panic. Its behavior depends on a couple<br /> of conditions in the /rtas node of the device tree, the traversal of<br /> which entails locking and local IRQ state changes. If the kernel panics<br /> while devtree_lock is held, rtas_os_term() as currently written could<br /> hang.<br /> <br /> Instead of discovering the relevant characteristics at panic time,<br /> cache them in file-static variables at boot. Note the lookup for<br /> "ibm,extended-os-term" is converted to of_property_read_bool() since it<br /> is a boolean property, not an RTAS function token.<br /> <br /> [mpe: Incorporate suggested change from Nick]
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50853
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> NFSv4: Fix a credential leak in _nfs4_discover_trunking()
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50854
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nfc: virtual_ncidev: Fix memory leak in virtual_nci_send()<br /> <br /> skb should be free in virtual_nci_send(), otherwise kmemleak will report<br /> memleak.<br /> <br /> Steps for reproduction (simulated in qemu):<br /> cd tools/testing/selftests/nci<br /> make<br /> ./nci_dev<br /> <br /> BUG: memory leak<br /> unreferenced object 0xffff888107588000 (size 208):<br /> comm "nci_dev", pid 206, jiffies 4294945376 (age 368.248s)<br /> hex dump (first 32 bytes):<br /> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................<br /> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................<br /> backtrace:<br /> [] __alloc_skb+0x1da/0x290<br /> [] nci_send_cmd+0xa3/0x350<br /> [] nci_reset_req+0x6b/0xa0<br /> [] __nci_request+0x90/0x250<br /> [] nci_dev_up+0x217/0x5b0<br /> [] nfc_dev_up+0x114/0x220<br /> [] nfc_genl_dev_up+0x94/0xe0<br /> [] genl_family_rcv_msg_doit.isra.14+0x228/0x2d0<br /> [] genl_rcv_msg+0x35c/0x640<br /> [] netlink_rcv_skb+0x11e/0x350<br /> [] genl_rcv+0x24/0x40<br /> [] netlink_unicast+0x43f/0x640<br /> [] netlink_sendmsg+0x73a/0xbf0<br /> [] __sys_sendto+0x324/0x370<br /> [] __x64_sys_sendto+0xdd/0x1b0<br /> [] do_syscall_64+0x3f/0x90
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50855
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: prevent leak of lsm program after failed attach<br /> <br /> In [0], we added the ability to bpf_prog_attach LSM programs to cgroups,<br /> but in our validation to make sure the prog is meant to be attached to<br /> BPF_LSM_CGROUP, we return too early if the check fails. This results in<br /> lack of decrementing prog&amp;#39;s refcnt (through bpf_prog_put)<br /> leaving the LSM program alive past the point of the expected lifecycle.<br /> This fix allows for the decrement to take place.<br /> <br /> [0] https://lore.kernel.org/all/20220628174314.1216643-4-sdf@google.com/
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50856
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cifs: Fix xid leak in cifs_ses_add_channel()<br /> <br /> Before return, should free the xid, otherwise, the<br /> xid will be leaked.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50857
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> rapidio: rio: fix possible name leak in rio_register_mport()<br /> <br /> If device_register() returns error, the name allocated by dev_set_name()<br /> need be freed. It should use put_device() to give up the reference in the<br /> error path, so that the name can be freed in kobject_cleanup(), and<br /> list_del() is called to delete the port from rio_mports.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50858
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mmc: alcor: fix return value check of mmc_add_host()<br /> <br /> mmc_add_host() may return error, if we ignore its return value, the memory<br /> that allocated in mmc_alloc_host() will be leaked and it will lead a kernel<br /> crash because of deleting not added device in the remove path.<br /> <br /> So fix this by checking the return value and calling mmc_free_host() in the<br /> error path.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50859
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message<br /> <br /> Commit d5c7076b772a ("smb3: add smb3.1.1 to default dialect list")<br /> extend the dialects from 3 to 4, but forget to decrease the extended<br /> length when specific the dialect, then the message length is larger<br /> than expected.<br /> <br /> This maybe leak some info through network because not initialize the<br /> message body.<br /> <br /> After apply this patch, the VALIDATE_NEGOTIATE_INFO message length is<br /> reduced from 28 bytes to 26 bytes.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025

CVE-2022-50860
Publication date:
30/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> apparmor: Fix memleak in alloc_ns()<br /> <br /> After changes in commit a1bd627b46d1 ("apparmor: share profile name on<br /> replacement"), the hname member of struct aa_policy is not valid slab<br /> object, but a subset of that, it can not be freed by kfree_sensitive(),<br /> use aa_policy_destroy() to fix it.
Severity CVSS v4.0: Pending analysis
Last modification:
31/12/2025
Subscribe to Vulnerabilities