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

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result()<br /> <br /> If the ssid-&gt;datalen is more than IEEE80211_MAX_SSID_LEN (32) it would<br /> lead to memory corruption so add some bounds checking.
Severity CVSS v4.0: Pending analysis
Last modification:
19/10/2026

CVE-2025-39850

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects<br /> <br /> When the "proxy" option is enabled on a VXLAN device, the device will<br /> suppress ARP requests and IPv6 Neighbor Solicitation messages if it is<br /> able to reply on behalf of the remote host. That is, if a matching and<br /> valid neighbor entry is configured on the VXLAN device whose MAC address<br /> is not behind the "any" remote (0.0.0.0 / ::).<br /> <br /> The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC<br /> address points to a valid remote destination, but this is incorrect if<br /> the entry is associated with an FDB nexthop group. This can result in a<br /> NPD [1][3] which can be reproduced using [2][4].<br /> <br /> Fix by checking that the remote destination exists before dereferencing<br /> it.<br /> <br /> [1]<br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> [...]<br /> CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary)<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014<br /> RIP: 0010:vxlan_xmit+0xb58/0x15f0<br /> [...]<br /> Call Trace:<br /> <br /> dev_hard_start_xmit+0x5d/0x1c0<br /> __dev_queue_xmit+0x246/0xfd0<br /> packet_sendmsg+0x113a/0x1850<br /> __sock_sendmsg+0x38/0x70<br /> __sys_sendto+0x126/0x180<br /> __x64_sys_sendto+0x24/0x30<br /> do_syscall_64+0xa4/0x260<br /> entry_SYSCALL_64_after_hwframe+0x4b/0x53<br /> <br /> [2]<br /> #!/bin/bash<br /> <br /> ip address add 192.0.2.1/32 dev lo<br /> <br /> ip nexthop add id 1 via 192.0.2.2 fdb<br /> ip nexthop add id 10 group 1 fdb<br /> <br /> ip link add name vx0 up type vxlan id 10010 local 192.0.2.1 dstport 4789 proxy<br /> <br /> ip neigh add 192.0.2.3 lladdr 00:11:22:33:44:55 nud perm dev vx0<br /> <br /> bridge fdb add 00:11:22:33:44:55 dev vx0 self static nhid 10<br /> <br /> arping -b -c 1 -s 192.0.2.1 -I vx0 192.0.2.3<br /> <br /> [3]<br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> [...]<br /> CPU: 13 UID: 0 PID: 372 Comm: ndisc6 Not tainted 6.17.0-rc2-virtmne-g6ee90cb26014 #3 PREEMPT(voluntary)<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1v996), BIOS 1.17.0-4.fc41 04/01/2x014<br /> RIP: 0010:vxlan_xmit+0x803/0x1600<br /> [...]<br /> Call Trace:<br /> <br /> dev_hard_start_xmit+0x5d/0x1c0<br /> __dev_queue_xmit+0x246/0xfd0<br /> ip6_finish_output2+0x210/0x6c0<br /> ip6_finish_output+0x1af/0x2b0<br /> ip6_mr_output+0x92/0x3e0<br /> ip6_send_skb+0x30/0x90<br /> rawv6_sendmsg+0xe6e/0x12e0<br /> __sock_sendmsg+0x38/0x70<br /> __sys_sendto+0x126/0x180<br /> __x64_sys_sendto+0x24/0x30<br /> do_syscall_64+0xa4/0x260<br /> entry_SYSCALL_64_after_hwframe+0x4b/0x53<br /> RIP: 0033:0x7f383422ec77<br /> <br /> [4]<br /> #!/bin/bash<br /> <br /> ip address add 2001:db8:1::1/128 dev lo<br /> <br /> ip nexthop add id 1 via 2001:db8:1::1 fdb<br /> ip nexthop add id 10 group 1 fdb<br /> <br /> ip link add name vx0 up type vxlan id 10010 local 2001:db8:1::1 dstport 4789 proxy<br /> <br /> ip neigh add 2001:db8:1::3 lladdr 00:11:22:33:44:55 nud perm dev vx0<br /> <br /> bridge fdb add 00:11:22:33:44:55 dev vx0 self static nhid 10<br /> <br /> ndisc6 -r 1 -s 2001:db8:1::1 -w 1 2001:db8:1::3 vx0
Severity CVSS v4.0: Pending analysis
Last modification:
30/10/2026

CVE-2025-39851

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> vxlan: Fix NPD when refreshing an FDB entry with a nexthop object<br /> <br /> VXLAN FDB entries can point to either a remote destination or an FDB<br /> nexthop group. The latter is usually used in EVPN deployments where<br /> learning is disabled.<br /> <br /> However, when learning is enabled, an incoming packet might try to<br /> refresh an FDB entry that points to an FDB nexthop group and therefore<br /> does not have a remote. Such packets should be dropped, but they are<br /> only dropped after dereferencing the non-existent remote, resulting in a<br /> NPD [1] which can be reproduced using [2].<br /> <br /> Fix by dropping such packets earlier. Remove the misleading comment from<br /> first_remote_rcu().<br /> <br /> [1]<br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> [...]<br /> CPU: 13 UID: 0 PID: 361 Comm: mausezahn Not tainted 6.17.0-rc1-virtme-g9f6b606b6b37 #1 PREEMPT(voluntary)<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014<br /> RIP: 0010:vxlan_snoop+0x98/0x1e0<br /> [...]<br /> Call Trace:<br /> <br /> vxlan_encap_bypass+0x209/0x240<br /> encap_bypass_if_local+0xb1/0x100<br /> vxlan_xmit_one+0x1375/0x17e0<br /> vxlan_xmit+0x6b4/0x15f0<br /> dev_hard_start_xmit+0x5d/0x1c0<br /> __dev_queue_xmit+0x246/0xfd0<br /> packet_sendmsg+0x113a/0x1850<br /> __sock_sendmsg+0x38/0x70<br /> __sys_sendto+0x126/0x180<br /> __x64_sys_sendto+0x24/0x30<br /> do_syscall_64+0xa4/0x260<br /> entry_SYSCALL_64_after_hwframe+0x4b/0x53<br /> <br /> [2]<br /> #!/bin/bash<br /> <br /> ip address add 192.0.2.1/32 dev lo<br /> ip address add 192.0.2.2/32 dev lo<br /> <br /> ip nexthop add id 1 via 192.0.2.3 fdb<br /> ip nexthop add id 10 group 1 fdb<br /> <br /> ip link add name vx0 up type vxlan id 10010 local 192.0.2.1 dstport 12345 localbypass<br /> ip link add name vx1 up type vxlan id 10020 local 192.0.2.2 dstport 54321 learning<br /> <br /> bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 192.0.2.2 port 54321 vni 10020<br /> bridge fdb add 00:aa:bb:cc:dd:ee dev vx1 self static nhid 10<br /> <br /> mausezahn vx0 -a 00:aa:bb:cc:dd:ee -b 00:11:22:33:44:55 -c 1 -q
Severity CVSS v4.0: Pending analysis
Last modification:
30/10/2026

CVE-2025-10718

Publication date:
19/09/2025
A vulnerability was found in Ooma Office Business Phone App up to 7.2.2 on Android. This affects an unknown part of the component com.ooma.office2. The manipulation results in improper export of android application components. The attack needs to be approached locally. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
Severity CVSS v4.0: LOW
Last modification:
30/09/2026

CVE-2025-39837

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> platform/x86: asus-wmi: Fix racy registrations<br /> <br /> asus_wmi_register_driver() may be called from multiple drivers<br /> concurrently, which can lead to the racy list operations, eventually<br /> corrupting the memory and hitting Oops on some ASUS machines.<br /> Also, the error handling is missing, and it forgot to unregister ACPI<br /> lps0 dev ops in the error case.<br /> <br /> This patch covers those issues by introducing a simple mutex at<br /> acpi_wmi_register_driver() &amp; *_unregister_driver, and adding the<br /> proper call of asus_s2idle_check_unregister() in the error path.
Severity CVSS v4.0: Pending analysis
Last modification:
19/10/2026

CVE-2025-39838

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cifs: prevent NULL pointer dereference in UTF16 conversion<br /> <br /> There can be a NULL pointer dereference bug here. NULL is passed to<br /> __cifs_sfu_make_node without checks, which passes it unchecked to<br /> cifs_strndup_to_utf16, which in turn passes it to<br /> cifs_local_to_utf16_bytes where &amp;#39;*from&amp;#39; is dereferenced, causing a crash.<br /> <br /> This patch adds a check for NULL &amp;#39;src&amp;#39; in cifs_strndup_to_utf16 and<br /> returns NULL early to prevent dereferencing NULL pointer.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE
Severity CVSS v4.0: Pending analysis
Last modification:
05/11/2026

CVE-2025-39839

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> batman-adv: fix OOB read/write in network-coding decode<br /> <br /> batadv_nc_skb_decode_packet() trusts coded_len and checks only against<br /> skb-&gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing<br /> payload headroom, and the source skb length is not verified, allowing an<br /> out-of-bounds read and a small out-of-bounds write.<br /> <br /> Validate that coded_len fits within the payload area of both destination<br /> and source sk_buffs before XORing.
Severity CVSS v4.0: Pending analysis
Last modification:
19/10/2026

CVE-2025-39840

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> audit: fix out-of-bounds read in audit_compare_dname_path()<br /> <br /> When a watch on dir=/ is combined with an fsnotify event for a<br /> single-character name directly under / (e.g., creating /a), an<br /> out-of-bounds read can occur in audit_compare_dname_path().<br /> <br /> The helper parent_len() returns 1 for "/". In audit_compare_dname_path(),<br /> when parentlen equals the full path length (1), the code sets p = path + 1<br /> and pathlen = 1 - 1 = 0. The subsequent loop then dereferences<br /> p[pathlen - 1] (i.e., p[-1]), causing an out-of-bounds read.<br /> <br /> Fix this by adding a pathlen &gt; 0 check to the while loop condition<br /> to prevent the out-of-bounds access.<br /> <br /> [PM: subject tweak, sign-off email fixes]
Severity CVSS v4.0: Pending analysis
Last modification:
19/10/2026

CVE-2025-39841

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: lpfc: Fix buffer free/clear order in deferred receive path<br /> <br /> Fix a use-after-free window by correcting the buffer release sequence in<br /> the deferred receive path. The code freed the RQ buffer first and only<br /> then cleared the context pointer under the lock. Concurrent paths (e.g.,<br /> ABTS and the repost path) also inspect and release the same pointer under<br /> the lock, so the old order could lead to double-free/UAF.<br /> <br /> Note that the repost path already uses the correct pattern: detach the<br /> pointer under the lock, then free it after dropping the lock. The<br /> deferred path should do the same.
Severity CVSS v4.0: Pending analysis
Last modification:
19/10/2026

CVE-2025-39842

Publication date:
19/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ocfs2: prevent release journal inode after journal shutdown<br /> <br /> Before calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already<br /> been executed in ocfs2_dismount_volume(), so osb-&gt;journal must be NULL. <br /> Therefore, the following calltrace will inevitably fail when it reaches<br /> jbd2_journal_release_jbd_inode().<br /> <br /> ocfs2_dismount_volume()-&gt;<br /> ocfs2_delete_osb()-&gt;<br /> ocfs2_free_slot_info()-&gt;<br /> __ocfs2_free_slot_info()-&gt;<br /> evict()-&gt;<br /> ocfs2_evict_inode()-&gt;<br /> ocfs2_clear_inode()-&gt;<br /> jbd2_journal_release_jbd_inode(osb-&gt;journal-&gt;j_journal,<br /> <br /> Adding osb-&gt;journal checks will prevent null-ptr-deref during the above<br /> execution path.
Severity CVSS v4.0: Pending analysis
Last modification:
19/10/2026

CVE-2025-57528

Publication date:
19/09/2025
An issue was discovered in Tenda AC6 US_AC6V1.0BR_V15.03.05.16_multi_TD01 allowing attackers to cause a denial of service via the funcname, funcpara1, funcpara2 parameters to the formSetCfm function (uri path: SetCfm).
Severity CVSS v4.0: Pending analysis
Last modification:
07/11/2026

CVE-2025-8532

Publication date:
19/09/2025
Authorization Bypass Through User-Controlled Key, Improper Authorization vulnerability in Bimser Solution Software Trade Inc. EBA Document and Workflow Management System allows Forceful Browsing.<br /> <br /> This issue affects eBA Document and Workflow Management System: from 6.7.164 before 6.7.166.
Severity CVSS v4.0: Pending analysis
Last modification:
05/06/2026