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-2024-53198

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xen: Fix the issue of resource not being properly released in xenbus_dev_probe()<br /> <br /> This patch fixes an issue in the function xenbus_dev_probe(). In the<br /> xenbus_dev_probe() function, within the if (err) branch at line 313, the<br /> program incorrectly returns err directly without releasing the resources<br /> allocated by err = drv-&gt;probe(dev, id). As the return value is non-zero,<br /> the upper layers assume the processing logic has failed. However, the probe<br /> operation was performed earlier without a corresponding remove operation.<br /> Since the probe actually allocates resources, failing to perform the remove<br /> operation could lead to problems.<br /> <br /> To fix this issue, we followed the resource release logic of the<br /> xenbus_dev_remove() function by adding a new block fail_remove before the<br /> fail_put block. After entering the branch if (err) at line 313, the<br /> function will use a goto statement to jump to the fail_remove block,<br /> ensuring that the previously acquired resources are correctly released,<br /> thus preventing the reference count leak.<br /> <br /> This bug was identified by an experimental static analysis tool developed<br /> by our team. The tool specializes in analyzing reference count operations<br /> and detecting potential issues where resources are not properly managed.<br /> In this case, the tool flagged the missing release operation as a<br /> potential problem, which led to the development of this patch.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-53199

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: imx-audmix: Add NULL check in imx_audmix_probe<br /> <br /> devm_kasprintf() can return a NULL pointer on failure,but this<br /> returned value in imx_audmix_probe() is not checked.<br /> Add NULL check in imx_audmix_probe(), to handle kernel NULL<br /> pointer dereference error.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-53200

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Fix null check for pipe_ctx-&gt;plane_state in hwss_setup_dpp<br /> <br /> This commit addresses a null pointer dereference issue in<br /> hwss_setup_dpp(). The issue could occur when pipe_ctx-&gt;plane_state is<br /> null. The fix adds a check to ensure `pipe_ctx-&gt;plane_state` is not null<br /> before accessing. This prevents a null pointer dereference.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-53201

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Fix null check for pipe_ctx-&gt;plane_state in dcn20_program_pipe<br /> <br /> This commit addresses a null pointer dereference issue in<br /> dcn20_program_pipe(). Previously, commit 8e4ed3cf1642 ("drm/amd/display:<br /> Add null check for pipe_ctx-&gt;plane_state in dcn20_program_pipe")<br /> partially fixed the null pointer dereference issue. However, in<br /> dcn20_update_dchubp_dpp(), the variable pipe_ctx is passed in, and<br /> plane_state is accessed again through pipe_ctx. Multiple if statements<br /> directly call attributes of plane_state, leading to potential null<br /> pointer dereference issues. This patch adds necessary null checks to<br /> ensure stability.
Severity CVSS v4.0: Pending analysis
Last modification:
30/10/2026

CVE-2024-53202

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> firmware_loader: Fix possible resource leak in fw_log_firmware_info()<br /> <br /> The alg instance should be released under the exception path, otherwise<br /> there may be resource leak here.<br /> <br /> To mitigate this, free the alg instance with crypto_free_shash when kmalloc<br /> fails.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-53186

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: fix use-after-free in SMB request handling<br /> <br /> A race condition exists between SMB request handling in<br /> `ksmbd_conn_handler_loop()` and the freeing of `ksmbd_conn` in the<br /> workqueue handler `handle_ksmbd_work()`. This leads to a UAF.<br /> - KASAN: slab-use-after-free Read in handle_ksmbd_work<br /> - KASAN: slab-use-after-free in rtlock_slowlock_locked<br /> <br /> This race condition arises as follows:<br /> - `ksmbd_conn_handler_loop()` waits for `conn-&gt;r_count` to reach zero:<br /> `wait_event(conn-&gt;r_count_q, atomic_read(&amp;conn-&gt;r_count) == 0);`<br /> - Meanwhile, `handle_ksmbd_work()` decrements `conn-&gt;r_count` using<br /> `atomic_dec_return(&amp;conn-&gt;r_count)`, and if it reaches zero, calls<br /> `ksmbd_conn_free()`, which frees `conn`.<br /> - However, after `handle_ksmbd_work()` decrements `conn-&gt;r_count`,<br /> it may still access `conn-&gt;r_count_q` in the following line:<br /> `waitqueue_active(&amp;conn-&gt;r_count_q)` or `wake_up(&amp;conn-&gt;r_count_q)`<br /> This results in a UAF, as `conn` has already been freed.<br /> <br /> The discovery of this UAF can be referenced in the following PR for<br /> syzkaller&amp;#39;s support for SMB requests.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-53187

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> io_uring: check for overflows in io_pin_pages<br /> <br /> WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144<br /> CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0<br /> Call Trace:<br /> <br /> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183<br /> io_rings_map io_uring/io_uring.c:2611 [inline]<br /> io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470<br /> io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692<br /> io_uring_setup io_uring/io_uring.c:3781 [inline]<br /> ...<br /> <br /> <br /> io_pin_pages()&amp;#39;s uaddr parameter came directly from the user and can be<br /> garbage. Don&amp;#39;t just add size to it as it can overflow.
Severity CVSS v4.0: Pending analysis
Last modification:
30/10/2026

CVE-2024-53188

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: ath12k: fix crash when unbinding<br /> <br /> If there is an error during some initialization related to firmware,<br /> the function ath12k_dp_cc_cleanup is called to release resources.<br /> However this is released again when the device is unbinded (ath12k_pci),<br /> and we get:<br /> BUG: kernel NULL pointer dereference, address: 0000000000000020<br /> at RIP: 0010:ath12k_dp_cc_cleanup.part.0+0xb6/0x500 [ath12k]<br /> Call Trace:<br /> ath12k_dp_cc_cleanup<br /> ath12k_dp_free<br /> ath12k_core_deinit<br /> ath12k_pci_remove<br /> ...<br /> <br /> The issue is always reproducible from a VM because the MSI addressing<br /> initialization is failing.<br /> <br /> In order to fix the issue, just set to NULL the released structure in<br /> ath12k_dp_cc_cleanup at the end.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026

CVE-2024-53189

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: nl80211: fix bounds checker error in nl80211_parse_sched_scan<br /> <br /> The channels array in the cfg80211_scan_request has a __counted_by<br /> attribute attached to it, which points to the n_channels variable. This<br /> attribute is used in bounds checking, and if it is not set before the<br /> array is filled, then the bounds sanitizer will issue a warning or a<br /> kernel panic if CONFIG_UBSAN_TRAP is set.<br /> <br /> This patch sets the size of allocated memory as the initial value for<br /> n_channels. It is updated with the actual number of added elements after<br /> the array is filled.
Severity CVSS v4.0: Pending analysis
Last modification:
05/11/2026

CVE-2024-53190

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures<br /> <br /> Syzkaller reported a hung task with uevent_show() on stack trace. That<br /> specific issue was addressed by another commit [0], but even with that<br /> fix applied (for example, running v6.12-rc5) we face another type of hung<br /> task that comes from the same reproducer [1]. By investigating that, we<br /> could narrow it to the following path:<br /> <br /> (a) Syzkaller emulates a Realtek USB WiFi adapter using raw-gadget and<br /> dummy_hcd infrastructure.<br /> <br /> (b) During the probe of rtl8192cu, the driver ends-up performing an efuse<br /> read procedure (which is related to EEPROM load IIUC), and here lies the<br /> issue: the function read_efuse() calls read_efuse_byte() many times, as<br /> loop iterations depending on the efuse size (in our example, 512 in total).<br /> <br /> This procedure for reading efuse bytes relies in a loop that performs an<br /> I/O read up to *10k* times in case of failures. We measured the time of<br /> the loop inside read_efuse_byte() alone, and in this reproducer (which<br /> involves the dummy_hcd emulation layer), it takes 15 seconds each. As a<br /> consequence, we have the driver stuck in its probe routine for big time,<br /> exposing a stack trace like below if we attempt to reboot the system, for<br /> example:<br /> <br /> task:kworker/0:3 state:D stack:0 pid:662 tgid:662 ppid:2 flags:0x00004000<br /> Workqueue: usb_hub_wq hub_event<br /> Call Trace:<br /> __schedule+0xe22/0xeb6<br /> schedule_timeout+0xe7/0x132<br /> __wait_for_common+0xb5/0x12e<br /> usb_start_wait_urb+0xc5/0x1ef<br /> ? usb_alloc_urb+0x95/0xa4<br /> usb_control_msg+0xff/0x184<br /> _usbctrl_vendorreq_sync+0xa0/0x161<br /> _usb_read_sync+0xb3/0xc5<br /> read_efuse_byte+0x13c/0x146<br /> read_efuse+0x351/0x5f0<br /> efuse_read_all_map+0x42/0x52<br /> rtl_efuse_shadow_map_update+0x60/0xef<br /> rtl_get_hwinfo+0x5d/0x1c2<br /> rtl92cu_read_eeprom_info+0x10a/0x8d5<br /> ? rtl92c_read_chip_version+0x14f/0x17e<br /> rtl_usb_probe+0x323/0x851<br /> usb_probe_interface+0x278/0x34b<br /> really_probe+0x202/0x4a4<br /> __driver_probe_device+0x166/0x1b2<br /> driver_probe_device+0x2f/0xd8<br /> [...]<br /> <br /> We propose hereby to drastically reduce the attempts of doing the I/O<br /> reads in case of failures, restricted to USB devices (given that<br /> they&amp;#39;re inherently slower than PCIe ones). By retrying up to 10 times<br /> (instead of 10000), we got reponsiveness in the reproducer, while seems<br /> reasonable to believe that there&amp;#39;s no sane USB device implementation in<br /> the field requiring this amount of retries at every I/O read in order<br /> to properly work. Based on that assumption, it&amp;#39;d be good to have it<br /> backported to stable but maybe not since driver implementation (the 10k<br /> number comes from day 0), perhaps up to 6.x series makes sense.<br /> <br /> [0] Commit 15fffc6a5624 ("driver core: Fix uevent_show() vs driver detach race")<br /> <br /> [1] A note about that: this syzkaller report presents multiple reproducers<br /> that differs by the type of emulated USB device. For this specific case,<br /> check the entry from 2024/08/08 06:23 in the list of crashes; the C repro<br /> is available at https://syzkaller.appspot.com/text?tag=ReproC&amp;x=1521fc83980000.
Severity CVSS v4.0: Pending analysis
Last modification:
03/11/2025

CVE-2024-53191

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: ath12k: fix warning when unbinding<br /> <br /> If there is an error during some initialization related to firmware,<br /> the buffers dp-&gt;tx_ring[i].tx_status are released.<br /> However this is released again when the device is unbinded (ath12k_pci),<br /> and we get:<br /> WARNING: CPU: 0 PID: 2098 at mm/slub.c:4689 free_large_kmalloc+0x4d/0x80<br /> Call Trace:<br /> free_large_kmalloc<br /> ath12k_dp_free<br /> ath12k_core_deinit<br /> ath12k_pci_remove<br /> ...<br /> <br /> The issue is always reproducible from a VM because the MSI addressing<br /> initialization is failing.<br /> <br /> In order to fix the issue, just set the buffers to NULL after releasing in<br /> order to avoid the double free.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2024-53192

Publication date:
27/12/2024
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access<br /> <br /> Flexible-array member `hws` in `struct clk_hw_onecell_data` is annotated<br /> with the `counted_by()` attribute. This means that when memory is<br /> allocated for this array, the _counter_, which in this case is member<br /> `num` in the flexible structure, should be set to the maximum number of<br /> elements the flexible array can contain, or fewer.<br /> <br /> In this case, the total number of elements for the flexible array is<br /> determined by variable `clks_num` when allocating heap space via<br /> `devm_kzalloc()`, as shown below:<br /> <br /> 289 struct loongson2_clk_provider *clp;<br /> ...<br /> 296 for (p = data; p-&gt;name; p++)<br /> 297 clks_num++;<br /> 298<br /> 299 clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num),<br /> 300 GFP_KERNEL);<br /> <br /> So, `clp-&gt;clk_data.num` should be set to `clks_num` or less, and not<br /> exceed `clks_num`, as is currently the case. Otherwise, if data is<br /> written into `clp-&gt;clk_data.hws[clks_num]`, the instrumentation<br /> provided by the compiler won&amp;#39;t detect the overflow, leading to a<br /> memory corruption bug at runtime.<br /> <br /> Fix this issue by setting `clp-&gt;clk_data.num` to `clks_num`.
Severity CVSS v4.0: Pending analysis
Last modification:
04/08/2026