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

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: dsa: mv88e6060: prevent crash on an unused port<br /> <br /> If the port isn&amp;#39;t a CPU port nor a user port, &amp;#39;cpu_dp&amp;#39;<br /> is a null pointer and a crash happened on dereferencing<br /> it in mv88e6060_setup_port():<br /> <br /> [ 9.575872] Unable to handle kernel NULL pointer dereference at virtual address 00000014<br /> ...<br /> [ 9.942216] mv88e6060_setup from dsa_register_switch+0x814/0xe84<br /> [ 9.948616] dsa_register_switch from mdio_probe+0x2c/0x54<br /> [ 9.954433] mdio_probe from really_probe.part.0+0x98/0x2a0<br /> [ 9.960375] really_probe.part.0 from driver_probe_device+0x30/0x10c<br /> [ 9.967029] driver_probe_device from __device_attach_driver+0xb8/0x13c<br /> [ 9.973946] __device_attach_driver from bus_for_each_drv+0x90/0xe0<br /> [ 9.980509] bus_for_each_drv from __device_attach+0x110/0x184<br /> [ 9.986632] __device_attach from bus_probe_device+0x8c/0x94<br /> [ 9.992577] bus_probe_device from deferred_probe_work_func+0x78/0xa8<br /> [ 9.999311] deferred_probe_work_func from process_one_work+0x290/0x73c<br /> [ 10.006292] process_one_work from worker_thread+0x30/0x4b8<br /> [ 10.012155] worker_thread from kthread+0xd4/0x10c<br /> [ 10.017238] kthread from ret_from_fork+0x14/0x3c
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50048

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: nf_tables: possible module reference underflow in error path<br /> <br /> dst-&gt;ops is set on when nft_expr_clone() fails, but module refcount has<br /> not been bumped yet, therefore nft_expr_destroy() leads to module<br /> reference underflow.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50049

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: DPCM: Don&amp;#39;t pick up BE without substream<br /> <br /> When DPCM tries to add valid BE connections at dpcm_add_paths(), it<br /> doesn&amp;#39;t check whether the picked BE actually supports for the given<br /> stream direction. Due to that, when an asymmetric BE stream is<br /> present, it picks up wrongly and this may result in a NULL dereference<br /> at a later point where the code assumes the existence of a<br /> corresponding BE substream.<br /> <br /> This patch adds the check for the presence of the substream for the<br /> target BE for avoiding the problem above.<br /> <br /> Note that we have already some fix for non-existing BE substream at<br /> commit 6246f283d5e0 ("ASoC: dpcm: skip missing substream while<br /> applying symmetry"). But the code path we&amp;#39;ve hit recently is rather<br /> happening before the previous fix. So this patch tries to fix at<br /> picking up a BE instead of parsing BE lists.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50050

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: SOF: Intel: hda: Fix potential buffer overflow by snprintf()<br /> <br /> snprintf() returns the would-be-filled size when the string overflows<br /> the given buffer size, hence using this value may result in the buffer<br /> overflow (although it&amp;#39;s unrealistic).<br /> <br /> This patch replaces with a safer version, scnprintf() for papering<br /> over such a potential issue.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50051

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: SOF: debug: Fix potential buffer overflow by snprintf()<br /> <br /> snprintf() returns the would-be-filled size when the string overflows<br /> the given buffer size, hence using this value may result in the buffer<br /> overflow (although it&amp;#39;s unrealistic).<br /> <br /> This patch replaces with a safer version, scnprintf() for papering<br /> over such a potential issue.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50052

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: Intel: avs: Fix potential buffer overflow by snprintf()<br /> <br /> snprintf() returns the would-be-filled size when the string overflows<br /> the given buffer size, hence using this value may result in a buffer<br /> overflow (although it&amp;#39;s unrealistic).<br /> <br /> This patch replaces it with a safer version, scnprintf() for papering<br /> over such a potential issue.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50043

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: fix potential refcount leak in ndisc_router_discovery()<br /> <br /> The issue happens on specific paths in the function. After both the<br /> object `rt` and `neigh` are grabbed successfully, when `lifetime` is<br /> nonzero but the metric needs change, the function just deletes the<br /> route and set `rt` to NULL. Then, it may try grabbing `rt` and `neigh`<br /> again if above conditions hold. The function simply overwrite `neigh`<br /> if succeeds or returns if fails, without decreasing the reference<br /> count of previous `neigh`. This may result in memory leaks.<br /> <br /> Fix it by decrementing the reference count of `neigh` in place.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50044

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: qrtr: start MHI channel after endpoit creation<br /> <br /> MHI channel may generates event/interrupt right after enabling.<br /> It may leads to 2 race conditions issues.<br /> <br /> 1)<br /> Such event may be dropped by qcom_mhi_qrtr_dl_callback() at check:<br /> <br /> if (!qdev || mhi_res-&gt;transaction_status)<br /> return;<br /> <br /> Because dev_set_drvdata(&amp;mhi_dev-&gt;dev, qdev) may be not performed at<br /> this moment. In this situation qrtr-ns will be unable to enumerate<br /> services in device.<br /> ---------------------------------------------------------------<br /> <br /> 2)<br /> Such event may come at the moment after dev_set_drvdata() and<br /> before qrtr_endpoint_register(). In this case kernel will panic with<br /> accessing wrong pointer at qcom_mhi_qrtr_dl_callback():<br /> <br /> rc = qrtr_endpoint_post(&amp;qdev-&gt;ep, mhi_res-&gt;buf_addr,<br /> mhi_res-&gt;bytes_xferd);<br /> <br /> Because endpoint is not created yet.<br /> --------------------------------------------------------------<br /> So move mhi_prepare_for_transfer_autoqueue after endpoint creation<br /> to fix it.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50036

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/sun4i: dsi: Prevent underflow when computing packet sizes<br /> <br /> Currently, the packet overhead is subtracted using unsigned arithmetic.<br /> With a short sync pulse, this could underflow and wrap around to near<br /> the maximal u16 value. Fix this by using signed subtraction. The call to<br /> max() will correctly handle any negative numbers that are produced.<br /> <br /> Apply the same fix to the other timings, even though those subtractions<br /> are less likely to underflow.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50037

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/i915/ttm: don&amp;#39;t leak the ccs state<br /> <br /> The kernel only manages the ccs state with lmem-only objects, however<br /> the kernel should still take care not to leak the CCS state from the<br /> previous user.<br /> <br /> (cherry picked from commit 353819d85f87be46aeb9c1dd929d445a006fc6ec)
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50038

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/meson: Fix refcount bugs in meson_vpu_has_available_connectors()<br /> <br /> In this function, there are two refcount leak bugs:<br /> (1) when breaking out of for_each_endpoint_of_node(), we need call<br /> the of_node_put() for the &amp;#39;ep&amp;#39;;<br /> (2) we should call of_node_put() for the reference returned by<br /> of_graph_get_remote_port() when it is not used anymore.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50039

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> stmmac: intel: Add a missing clk_disable_unprepare() call in intel_eth_pci_remove()<br /> <br /> Commit 09f012e64e4b ("stmmac: intel: Fix clock handling on error and remove<br /> paths") removed this clk_disable_unprepare()<br /> <br /> This was partly revert by commit ac322f86b56c ("net: stmmac: Fix clock<br /> handling on remove path") which removed this clk_disable_unprepare()<br /> because:<br /> "<br /> While unloading the dwmac-intel driver, clk_disable_unprepare() is<br /> being called twice in stmmac_dvr_remove() and<br /> intel_eth_pci_remove(). This causes kernel panic on the second call.<br /> "<br /> <br /> However later on, commit 5ec55823438e8 ("net: stmmac: add clocks management<br /> for gmac driver") has updated stmmac_dvr_remove() which do not call<br /> clk_disable_unprepare() anymore.<br /> <br /> So this call should now be called from intel_eth_pci_remove().
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025