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-2025-71153
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: Fix memory leak in get_file_all_info()<br /> <br /> In get_file_all_info(), if vfs_getattr() fails, the function returns<br /> immediately without freeing the allocated filename, leading to a memory<br /> leak.<br /> <br /> Fix this by freeing the filename before returning in this error case.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71154
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: usb: rtl8150: fix memory leak on usb_submit_urb() failure<br /> <br /> In async_set_registers(), when usb_submit_urb() fails, the allocated<br /> async_req structure and URB are not freed, causing a memory leak.<br /> <br /> The completion callback async_set_reg_cb() is responsible for freeing<br /> these allocations, but it is only called after the URB is successfully<br /> submitted and completes (successfully or with error). If submission<br /> fails, the callback never runs and the memory is leaked.<br /> <br /> Fix this by freeing both the URB and the request structure in the error<br /> path when usb_submit_urb() fails.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71155
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KVM: s390: Fix gmap_helper_zap_one_page() again<br /> <br /> A few checks were missing in gmap_helper_zap_one_page(), which can lead<br /> to memory corruption in the guest under specific circumstances.<br /> <br /> Add the missing checks.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71156
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> gve: defer interrupt enabling until NAPI registration<br /> <br /> Currently, interrupts are automatically enabled immediately upon<br /> request. This allows interrupt to fire before the associated NAPI<br /> context is fully initialized and cause failures like below:<br /> <br /> [ 0.946369] Call Trace:<br /> [ 0.946369] <br /> [ 0.946369] __napi_poll+0x2a/0x1e0<br /> [ 0.946369] net_rx_action+0x2f9/0x3f0<br /> [ 0.946369] handle_softirqs+0xd6/0x2c0<br /> [ 0.946369] ? handle_edge_irq+0xc1/0x1b0<br /> [ 0.946369] __irq_exit_rcu+0xc3/0xe0<br /> [ 0.946369] common_interrupt+0x81/0xa0<br /> [ 0.946369] <br /> [ 0.946369] <br /> [ 0.946369] asm_common_interrupt+0x22/0x40<br /> [ 0.946369] RIP: 0010:pv_native_safe_halt+0xb/0x10<br /> <br /> Use the `IRQF_NO_AUTOEN` flag when requesting interrupts to prevent auto<br /> enablement and explicitly enable the interrupt in NAPI initialization<br /> path (and disable it during NAPI teardown).<br /> <br /> This ensures that interrupt lifecycle is strictly coupled with<br /> readiness of NAPI context.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71157
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/core: always drop device refcount in ib_del_sub_device_and_put()<br /> <br /> Since nldev_deldev() (introduced by commit 060c642b2ab8 ("RDMA/nldev: Add<br /> support to add/delete a sub IB device through netlink") grabs a reference<br /> using ib_device_get_by_index() before calling ib_del_sub_device_and_put(),<br /> we need to drop that reference before returning -EOPNOTSUPP error.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2026-0994
Publication date:
23/01/2026
A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages.<br /> <br /> Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.
Severity CVSS v4.0: HIGH
Last modification:
23/01/2026

CVE-2025-71146
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: nf_conncount: fix leaked ct in error paths<br /> <br /> There are some situations where ct might be leaked as error paths are<br /> skipping the refcounted check and return immediately. In order to solve<br /> it make sure that the check is always called.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71147
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KEYS: trusted: Fix a memory leak in tpm2_load_cmd<br /> <br /> &amp;#39;tpm2_load_cmd&amp;#39; allocates a tempoary blob indirectly via &amp;#39;tpm2_key_decode&amp;#39;<br /> but it is not freed in the failure paths. Address this by wrapping the blob<br /> into with a cleanup helper.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71148
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/handshake: restore destructor on submit failure<br /> <br /> handshake_req_submit() replaces sk-&gt;sk_destruct but never restores it when<br /> submission fails before the request is hashed. handshake_sk_destruct() then<br /> returns early and the original destructor never runs, leaking the socket.<br /> Restore sk_destruct on the error path.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71149
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> io_uring/poll: correctly handle io_poll_add() return value on update<br /> <br /> When the core of io_uring was updated to handle completions<br /> consistently and with fixed return codes, the POLL_REMOVE opcode<br /> with updates got slightly broken. If a POLL_ADD is pending and<br /> then POLL_REMOVE is used to update the events of that request, if that<br /> update causes the POLL_ADD to now trigger, then that completion is lost<br /> and a CQE is never posted.<br /> <br /> Additionally, ensure that if an update does cause an existing POLL_ADD<br /> to complete, that the completion value isn&amp;#39;t always overwritten with<br /> -ECANCELED. For that case, whatever io_poll_add() set the value to<br /> should just be retained.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71150
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: Fix refcount leak when invalid session is found on session lookup<br /> <br /> When a session is found but its state is not SMB2_SESSION_VALID, It<br /> indicates that no valid session was found, but it is missing to decrement<br /> the reference count acquired by the session lookup, which results in<br /> a reference count leak. This patch fixes the issue by explicitly calling<br /> ksmbd_user_session_put to release the reference to the session.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026

CVE-2025-71151
Publication date:
23/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cifs: Fix memory and information leak in smb3_reconfigure()<br /> <br /> In smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the<br /> function returns immediately without freeing and erasing the newly<br /> allocated new_password and new_password2. This causes both a memory leak<br /> and a potential information leak.<br /> <br /> Fix this by calling kfree_sensitive() on both password buffers before<br /> returning in this error case.
Severity CVSS v4.0: Pending analysis
Last modification:
23/01/2026
Subscribe to Vulnerabilities