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

Publication date:
13/01/2026
Tenda AX-3 v16.03.12.10_CN was discovered to contain a stack overflow in the wanSpeed2 parameter of the fromAdvSetMacMtuWan function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted request.
Severity CVSS v4.0: Pending analysis
Last modification:
16/01/2026

CVE-2025-71027

Publication date:
13/01/2026
Tenda AX-3 v16.03.12.10_CN was discovered to contain a stack overflow in the wanMTU2 parameter of the fromAdvSetMacMtuWan function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted request.
Severity CVSS v4.0: Pending analysis
Last modification:
16/01/2026

CVE-2025-71064

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: hns3: using the num_tqps in the vf driver to apply for resources<br /> <br /> Currently, hdev-&gt;htqp is allocated using hdev-&gt;num_tqps, and kinfo-&gt;tqp<br /> is allocated using kinfo-&gt;num_tqps. However, kinfo-&gt;num_tqps is set to<br /> min(new_tqps, hdev-&gt;num_tqps); Therefore, kinfo-&gt;num_tqps may be smaller<br /> than hdev-&gt;num_tqps, which causes some hdev-&gt;htqp[i] to remain<br /> uninitialized in hclgevf_knic_setup().<br /> <br /> Thus, this patch allocates hdev-&gt;htqp and kinfo-&gt;tqp using hdev-&gt;num_tqps,<br /> ensuring that the lengths of hdev-&gt;htqp and kinfo-&gt;tqp are consistent<br /> and that all elements are properly initialized.
Severity CVSS v4.0: Pending analysis
Last modification:
15/04/2026

CVE-2025-71065

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to avoid potential deadlock<br /> <br /> As Jiaming Zhang and syzbot reported, there is potential deadlock in<br /> f2fs as below:<br /> <br /> Chain exists of:<br /> &amp;sbi-&gt;cp_rwsem --&gt; fs_reclaim --&gt; sb_internal#2<br /> <br /> Possible unsafe locking scenario:<br /> <br /> CPU0 CPU1<br /> ---- ----<br /> rlock(sb_internal#2);<br /> lock(fs_reclaim);<br /> lock(sb_internal#2);<br /> rlock(&amp;sbi-&gt;cp_rwsem);<br /> <br /> *** DEADLOCK ***<br /> <br /> 3 locks held by kswapd0/73:<br /> #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]<br /> #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389<br /> #1: ffff8880118400e0 (&amp;type-&gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]<br /> #1: ffff8880118400e0 (&amp;type-&gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197<br /> #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890<br /> <br /> stack backtrace:<br /> CPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)<br /> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120<br /> print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043<br /> check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175<br /> check_prev_add kernel/locking/lockdep.c:3165 [inline]<br /> check_prevs_add kernel/locking/lockdep.c:3284 [inline]<br /> validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908<br /> __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237<br /> lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868<br /> down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537<br /> f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]<br /> f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]<br /> f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791<br /> f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867<br /> f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925<br /> f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897<br /> evict+0x504/0x9c0 fs/inode.c:810<br /> f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853<br /> evict+0x504/0x9c0 fs/inode.c:810<br /> dispose_list fs/inode.c:852 [inline]<br /> prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000<br /> super_cache_scan+0x39b/0x4b0 fs/super.c:224<br /> do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437<br /> shrink_slab_memcg mm/shrinker.c:550 [inline]<br /> shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628<br /> shrink_one+0x28a/0x7c0 mm/vmscan.c:4955<br /> shrink_many mm/vmscan.c:5016 [inline]<br /> lru_gen_shrink_node mm/vmscan.c:5094 [inline]<br /> shrink_node+0x315d/0x3780 mm/vmscan.c:6081<br /> kswapd_shrink_node mm/vmscan.c:6941 [inline]<br /> balance_pgdat mm/vmscan.c:7124 [inline]<br /> kswapd+0x147c/0x2800 mm/vmscan.c:7389<br /> kthread+0x70e/0x8a0 kernel/kthread.c:463<br /> ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158<br /> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245<br /> <br /> <br /> The root cause is deadlock among four locks as below:<br /> <br /> kswapd<br /> - fs_reclaim --- Lock A<br /> - shrink_one<br /> - evict<br /> - f2fs_evict_inode<br /> - sb_start_intwrite --- Lock B<br /> <br /> - iput<br /> - evict<br /> - f2fs_evict_inode<br /> - sb_start_intwrite --- Lock B<br /> - f2fs_truncate<br /> - f2fs_truncate_blocks<br /> - f2fs_do_truncate_blocks<br /> - f2fs_lock_op --- Lock C<br /> <br /> ioctl<br /> - f2fs_ioc_commit_atomic_write<br /> - f2fs_lock_op --- Lock C<br /> - __f2fs_commit_atomic_write<br /> - __replace_atomic_write_block<br /> - f2fs_get_dnode_of_data<br /> - __get_node_folio<br /> - f2fs_check_nid_range<br /> - f2fs_handle_error<br /> - f2fs_record_errors<br /> - f2fs_down_write --- Lock D<br /> <br /> open<br /> - do_open<br /> - do_truncate<br /> - security_inode_need_killpriv<br /> - f2fs_getxattr<br /> - lookup_all_xattrs<br /> - f2fs_handle_error<br /> - f2fs_record_errors<br /> - f2fs_down_write --- Lock D<br /> - f2fs_commit_super<br /> - read_mapping_folio<br /> - filemap_alloc_folio_noprof<br /> - prepare_alloc_pages<br /> - fs_reclaim_acquire --- Lock A<br /> <br /> In order to a<br /> ---truncated---
Severity CVSS v4.0: Pending analysis
Last modification:
15/04/2026

CVE-2025-71066

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change<br /> <br /> zdi-disclosures@trendmicro.com says:<br /> <br /> The vulnerability is a race condition between `ets_qdisc_dequeue` and<br /> `ets_qdisc_change`. It leads to UAF on `struct Qdisc` object.<br /> Attacker requires the capability to create new user and network namespace<br /> in order to trigger the bug.<br /> See my additional commentary at the end of the analysis.<br /> <br /> Analysis:<br /> <br /> static int ets_qdisc_change(struct Qdisc *sch, struct nlattr *opt,<br /> struct netlink_ext_ack *extack)<br /> {<br /> ...<br /> <br /> // (1) this lock is preventing .change handler (`ets_qdisc_change`)<br /> //to race with .dequeue handler (`ets_qdisc_dequeue`)<br /> sch_tree_lock(sch);<br /> <br /> for (i = nbands; i = q-&gt;nstrict &amp;&amp; q-&gt;classes[i].qdisc-&gt;q.qlen)<br /> list_del_init(&amp;q-&gt;classes[i].alist);<br /> qdisc_purge_queue(q-&gt;classes[i].qdisc);<br /> }<br /> <br /> WRITE_ONCE(q-&gt;nbands, nbands);<br /> for (i = nstrict; i nstrict; i++) {<br /> if (q-&gt;classes[i].qdisc-&gt;q.qlen) {<br /> // (2) the class is added to the q-&gt;active<br /> list_add_tail(&amp;q-&gt;classes[i].alist, &amp;q-&gt;active);<br /> q-&gt;classes[i].deficit = quanta[i];<br /> }<br /> }<br /> WRITE_ONCE(q-&gt;nstrict, nstrict);<br /> memcpy(q-&gt;prio2band, priomap, sizeof(priomap));<br /> <br /> for (i = 0; i nbands; i++)<br /> WRITE_ONCE(q-&gt;classes[i].quantum, quanta[i]);<br /> <br /> for (i = oldbands; i nbands; i++) {<br /> q-&gt;classes[i].qdisc = queues[i];<br /> if (q-&gt;classes[i].qdisc != &amp;noop_qdisc)<br /> qdisc_hash_add(q-&gt;classes[i].qdisc, true);<br /> }<br /> <br /> // (3) the qdisc is unlocked, now dequeue can be called in parallel<br /> // to the rest of .change handler<br /> sch_tree_unlock(sch);<br /> <br /> ets_offload_change(sch);<br /> for (i = q-&gt;nbands; i classes[i].qdisc);<br /> // (5) If we call .dequeue between (4) and (5), we will have<br /> // a strong UAF and we can control RIP<br /> q-&gt;classes[i].qdisc = NULL;<br /> WRITE_ONCE(q-&gt;classes[i].quantum, 0);<br /> q-&gt;classes[i].deficit = 0;<br /> gnet_stats_basic_sync_init(&amp;q-&gt;classes[i].bstats);<br /> memset(&amp;q-&gt;classes[i].qstats, 0, sizeof(q-&gt;classes[i].qstats));<br /> }<br /> return 0;<br /> }<br /> <br /> Comment:<br /> This happens because some of the classes have their qdiscs assigned to<br /> NULL, but remain in the active list. This commit fixes this issue by always<br /> removing the class from the active list before deleting and freeing its<br /> associated qdisc<br /> <br /> Reproducer Steps<br /> (trimmed version of what was sent by zdi-disclosures@trendmicro.com)<br /> <br /> ```<br /> DEV="${DEV:-lo}"<br /> ROOT_HANDLE="${ROOT_HANDLE:-1:}"<br /> BAND2_HANDLE="${BAND2_HANDLE:-20:}" # child under 1:2<br /> PING_BYTES="${PING_BYTES:-48}"<br /> PING_COUNT="${PING_COUNT:-200000}"<br /> PING_DST="${PING_DST:-127.0.0.1}"<br /> <br /> SLOW_TBF_RATE="${SLOW_TBF_RATE:-8bit}"<br /> SLOW_TBF_BURST="${SLOW_TBF_BURST:-100b}"<br /> SLOW_TBF_LAT="${SLOW_TBF_LAT:-1s}"<br /> <br /> cleanup() {<br /> tc qdisc del dev "$DEV" root 2&gt;/dev/null<br /> }<br /> trap cleanup EXIT<br /> <br /> ip link set "$DEV" up<br /> <br /> tc qdisc del dev "$DEV" root 2&gt;/dev/null || true<br /> <br /> tc qdisc add dev "$DEV" root handle "$ROOT_HANDLE" ets bands 2 strict 2<br /> <br /> tc qdisc add dev "$DEV" parent 1:2 handle "$BAND2_HANDLE" \<br /> tbf rate "$SLOW_TBF_RATE" burst "$SLOW_TBF_BURST" latency "$SLOW_TBF_LAT"<br /> <br /> tc filter add dev "$DEV" parent 1: protocol all prio 1 u32 match u32 0 0 flowid 1:2<br /> tc -s qdisc ls dev $DEV<br /> <br /> ping -I "$DEV" -f -c "$PING_COUNT" -s "$PING_BYTES" -W 0.001 "$PING_DST" \<br /> &gt;/dev/null 2&gt;&amp;1 &amp;<br /> tc qdisc change dev "$DEV" root handle "$ROOT_HANDLE" ets bands 2 strict 0<br /> tc qdisc change dev "$DEV" root handle "$ROOT_HANDLE" ets bands 2 strict 2<br /> tc -s qdisc ls dev $DEV<br /> tc qdisc del dev "$DEV" parent <br /> ---truncated---
Severity CVSS v4.0: Pending analysis
Last modification:
15/04/2026

CVE-2025-68823

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ublk: fix deadlock when reading partition table<br /> <br /> When one process(such as udev) opens ublk block device (e.g., to read<br /> the partition table via bdev_open()), a deadlock[1] can occur:<br /> <br /> 1. bdev_open() grabs disk-&gt;open_mutex<br /> 2. The process issues read I/O to ublk backend to read partition table<br /> 3. In __ublk_complete_rq(), blk_update_request() or blk_mq_end_request()<br /> runs bio-&gt;bi_end_io() callbacks<br /> 4. If this triggers fput() on file descriptor of ublk block device, the<br /> work may be deferred to current task&amp;#39;s task work (see fput() implementation)<br /> 5. This eventually calls blkdev_release() from the same context<br /> 6. blkdev_release() tries to grab disk-&gt;open_mutex again<br /> 7. Deadlock: same task waiting for a mutex it already holds<br /> <br /> The fix is to run blk_update_request() and blk_mq_end_request() with bottom<br /> halves disabled. This forces blkdev_release() to run in kernel work-queue<br /> context instead of current task work context, and allows ublk server to make<br /> forward progress, and avoids the deadlock.<br /> <br /> [axboe: rewrite comment in ublk]
Severity CVSS v4.0: Pending analysis
Last modification:
26/02/2026

CVE-2025-69990

Publication date:
13/01/2026
phpgurukul News Portal Project V4.1 has an Arbitrary File Deletion Vulnerability in remove_file.php. The parameter file can cause any file to be deleted.
Severity CVSS v4.0: Pending analysis
Last modification:
16/01/2026

CVE-2025-69991

Publication date:
13/01/2026
phpgurukul News Portal Project V4.1 is vulnerable to SQL Injection in check_availablity.php.
Severity CVSS v4.0: Pending analysis
Last modification:
16/01/2026

CVE-2025-69992

Publication date:
13/01/2026
phpgurukul News Portal Project V4.1 has File Upload Vulnerability via upload.php, which enables the upload of files of any format to the server without identity authentication.
Severity CVSS v4.0: Pending analysis
Last modification:
16/01/2026

CVE-2025-68818

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path"<br /> <br /> This reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.<br /> <br /> The commit being reverted added code to __qla2x00_abort_all_cmds() to<br /> call sp-&gt;done() without holding a spinlock. But unlike the older code<br /> below it, this new code failed to check sp-&gt;cmd_type and just assumed<br /> TYPE_SRB, which results in a jump to an invalid pointer in target-mode<br /> with TYPE_TGT_CMD:<br /> <br /> qla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success<br /> 0000000009f7a79b<br /> qla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h<br /> mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.<br /> qla2xxx [0000:65:00.0]-d01e:8: -&gt; fwdump no buffer<br /> qla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event<br /> 0x8002 occurred<br /> qla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -<br /> ha=0000000058183fda.<br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> PF: supervisor instruction fetch in kernel mode<br /> PF: error_code(0x0010) - not-present page<br /> PGD 0 P4D 0<br /> Oops: 0010 [#1] SMP<br /> CPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G O 6.1.133 #1<br /> Hardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023<br /> RIP: 0010:0x0<br /> Code: Unable to access opcode bytes at 0xffffffffffffffd6.<br /> RSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206<br /> RAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000<br /> RDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0<br /> RBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045<br /> R10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40<br /> R13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400<br /> FS: 0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> <br /> ? __die+0x4d/0x8b<br /> ? page_fault_oops+0x91/0x180<br /> ? trace_buffer_unlock_commit_regs+0x38/0x1a0<br /> ? exc_page_fault+0x391/0x5e0<br /> ? asm_exc_page_fault+0x22/0x30<br /> __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]<br /> qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]<br /> qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]<br /> qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]<br /> qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]<br /> kthread+0xa8/0xd0<br /> <br /> <br /> Then commit 4475afa2646d ("scsi: qla2xxx: Complete command early within<br /> lock") added the spinlock back, because not having the lock caused a<br /> race and a crash. But qla2x00_abort_srb() in the switch below already<br /> checks for qla2x00_chip_is_down() and handles it the same way, so the<br /> code above the switch is now redundant and still buggy in target-mode.<br /> Remove it.
Severity CVSS v4.0: Pending analysis
Last modification:
15/04/2026

CVE-2025-68819

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()<br /> <br /> rlen value is a user-controlled value, but dtv5100_i2c_msg() does not<br /> check the size of the rlen value. Therefore, if it is set to a value<br /> larger than sizeof(st-&gt;data), an out-of-bounds vuln occurs for st-&gt;data.<br /> <br /> Therefore, we need to add proper range checking to prevent this vuln.
Severity CVSS v4.0: Pending analysis
Last modification:
15/04/2026

CVE-2025-68820

Publication date:
13/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ext4: xattr: fix null pointer deref in ext4_raw_inode()<br /> <br /> If ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),<br /> iloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()<br /> lacks error checking, this will lead to a null pointer dereference<br /> in ext4_raw_inode(), called right after ext4_get_inode_loc().<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE.
Severity CVSS v4.0: Pending analysis
Last modification:
15/04/2026