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

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.<br /> <br /> While reading sysctl_icmp_errors_use_inbound_ifaddr, it can be changed<br /> concurrently. Thus, we need to add READ_ONCE() to its reader.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49633

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> icmp: Fix data-races around sysctl_icmp_echo_enable_probe.<br /> <br /> While reading sysctl_icmp_echo_enable_probe, it can be changed<br /> concurrently. Thus, we need to add READ_ONCE() to its readers.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49634

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> sysctl: Fix data-races in proc_dou8vec_minmax().<br /> <br /> A sysctl variable is accessed concurrently, and there is always a chance<br /> of data-race. So, all readers and writers need some basic protection to<br /> avoid load/store-tearing.<br /> <br /> This patch changes proc_dou8vec_minmax() to use READ_ONCE() and<br /> WRITE_ONCE() internally to fix data-races on the sysctl side. For now,<br /> proc_dou8vec_minmax() itself is tolerant to a data-race, but we still<br /> need to add annotations on the other subsystem&amp;#39;s side.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49635

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/i915/selftests: fix subtraction overflow bug<br /> <br /> On some machines hole_end can be small enough to cause subtraction<br /> overflow. On the other side (addr + 2 * min_alignment) can overflow<br /> in case of mock tests. This patch should handle both cases.<br /> <br /> (cherry picked from commit ab3edc679c552a466e4bf0b11af3666008bd65a2)
Severity CVSS v4.0: Pending analysis
Last modification:
23/10/2025

CVE-2022-49636

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> vlan: fix memory leak in vlan_newlink()<br /> <br /> Blamed commit added back a bug I fixed in commit 9bbd917e0bec<br /> ("vlan: fix memory leak in vlan_dev_set_egress_priority")<br /> <br /> If a memory allocation fails in vlan_changelink() after other allocations<br /> succeeded, we need to call vlan_dev_free_egress_priority()<br /> to free all allocated memory because after a failed -&gt;newlink()<br /> we do not call any methods like ndo_uninit() or dev-&gt;priv_destructor().<br /> <br /> In following example, if the allocation for last element 2000:2001 fails,<br /> we need to free eight prior allocations:<br /> <br /> ip link add link dummy0 dummy0.100 type vlan id 100 \<br /> egress-qos-map 1:2 2:3 3:4 4:5 5:6 6:7 7:8 8:9 2000:2001<br /> <br /> syzbot report was:<br /> <br /> BUG: memory leak<br /> unreferenced object 0xffff888117bd1060 (size 32):<br /> comm "syz-executor408", pid 3759, jiffies 4294956555 (age 34.090s)<br /> hex dump (first 32 bytes):<br /> 09 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 ................<br /> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................<br /> backtrace:<br /> [] kmalloc include/linux/slab.h:600 [inline]<br /> [] vlan_dev_set_egress_priority+0xed/0x170 net/8021q/vlan_dev.c:193<br /> [] vlan_changelink+0x178/0x1d0 net/8021q/vlan_netlink.c:128<br /> [] vlan_newlink+0x148/0x260 net/8021q/vlan_netlink.c:185<br /> [] rtnl_newlink_create net/core/rtnetlink.c:3363 [inline]<br /> [] __rtnl_newlink+0xa58/0xdc0 net/core/rtnetlink.c:3580<br /> [] rtnl_newlink+0x49/0x70 net/core/rtnetlink.c:3593<br /> [] rtnetlink_rcv_msg+0x21c/0x5c0 net/core/rtnetlink.c:6089<br /> [] netlink_rcv_skb+0x87/0x1d0 net/netlink/af_netlink.c:2501<br /> [] netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]<br /> [] netlink_unicast+0x397/0x4c0 net/netlink/af_netlink.c:1345<br /> [] netlink_sendmsg+0x396/0x710 net/netlink/af_netlink.c:1921<br /> [] sock_sendmsg_nosec net/socket.c:714 [inline]<br /> [] sock_sendmsg+0x56/0x80 net/socket.c:734<br /> [] ____sys_sendmsg+0x36c/0x390 net/socket.c:2488<br /> [] ___sys_sendmsg+0x8b/0xd0 net/socket.c:2542<br /> [] __sys_sendmsg net/socket.c:2571 [inline]<br /> [] __do_sys_sendmsg net/socket.c:2580 [inline]<br /> [] __se_sys_sendmsg net/socket.c:2578 [inline]<br /> [] __x64_sys_sendmsg+0x78/0xf0 net/socket.c:2578<br /> [] do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80<br /> [] entry_SYSCALL_64_after_hwframe+0x46/0xb0
Severity CVSS v4.0: Pending analysis
Last modification:
10/04/2025

CVE-2022-49637

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv4: Fix a data-race around sysctl_fib_sync_mem.<br /> <br /> While reading sysctl_fib_sync_mem, it can be changed concurrently.<br /> So, we need to add READ_ONCE() to avoid a data-race.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49616

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: rt7*-sdw: harden jack_detect_handler<br /> <br /> Realtek headset codec drivers typically check if the card is<br /> instantiated before proceeding with the jack detection.<br /> <br /> The rt700, rt711 and rt711-sdca are however missing a check on the<br /> card pointer, which can lead to NULL dereferences encountered in<br /> driver bind/unbind tests.
Severity CVSS v4.0: Pending analysis
Last modification:
23/10/2025

CVE-2022-49617

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: Intel: sof_sdw: handle errors on card registration<br /> <br /> If the card registration fails, typically because of deferred probes,<br /> the device properties added for headset codecs are not removed, which<br /> leads to kernel oopses in driver bind/unbind tests.<br /> <br /> We already clean-up the device properties when the card is removed,<br /> this code can be moved as a helper and called upon card registration<br /> errors.
Severity CVSS v4.0: Pending analysis
Last modification:
23/10/2025

CVE-2022-49618

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux()<br /> <br /> pdesc could be null but still dereference pdesc-&gt;name and it will lead to<br /> a null pointer access. So we move a null check before dereference.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49619

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: sfp: fix memory leak in sfp_probe()<br /> <br /> sfp_probe() allocates a memory chunk from sfp with sfp_alloc(). When<br /> devm_add_action() fails, sfp is not freed, which leads to a memory leak.<br /> <br /> We should use devm_add_action_or_reset() instead of devm_add_action().
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49620

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: tipc: fix possible refcount leak in tipc_sk_create()<br /> <br /> Free sk in case tipc_sk_insert() fails.
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025

CVE-2022-49621

Publication date:
26/02/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cpufreq: pmac32-cpufreq: Fix refcount leak bug<br /> <br /> In pmac_cpufreq_init_MacRISC3(), we need to add corresponding<br /> of_node_put() for the three node pointers whose refcount have<br /> been incremented by of_find_node_by_name().
Severity CVSS v4.0: Pending analysis
Last modification:
01/10/2025