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

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/ttm: Fix dummy res NULL ptr deref bug<br /> <br /> Check the bo-&gt;resource value before accessing the resource<br /> mem_type.<br /> <br /> v2: Fix commit description unwrapped warning<br /> <br /> <br /> [ 40.191227][ T184] general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] SMP KASAN PTI<br /> [ 40.192995][ T184] KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]<br /> [ 40.194411][ T184] CPU: 1 PID: 184 Comm: systemd-udevd Not tainted 5.19.0-rc4-00721-gb297c22b7070 #1<br /> [ 40.196063][ T184] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-debian-1.16.0-4 04/01/2014<br /> [ 40.199605][ T184] RIP: 0010:ttm_bo_validate+0x1b3/0x240 [ttm]<br /> [ 40.200754][ T184] Code: e8 72 c5 ff ff 83 f8 b8 74 d4 85 c0 75 54 49 8b 9e 58 01 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 10 48 89 fa 48 c1 ea 03 b6 04 02 84 c0 74 04 3c 03 7e 44 8b 53 10 31 c0 85 d2 0f 85 58<br /> [ 40.203685][ T184] RSP: 0018:ffffc900006df0c8 EFLAGS: 00010202<br /> [ 40.204630][ T184] RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 1ffff1102f4bb71b<br /> [ 40.205864][ T184] RDX: 0000000000000002 RSI: ffffc900006df208 RDI: 0000000000000010<br /> [ 40.207102][ T184] RBP: 1ffff920000dbe1a R08: ffffc900006df208 R09: 0000000000000000<br /> [ 40.208394][ T184] R10: ffff88817a5f0000 R11: 0000000000000001 R12: ffffc900006df110<br /> [ 40.209692][ T184] R13: ffffc900006df0f0 R14: ffff88817a5db800 R15: ffffc900006df208<br /> [ 40.210862][ T184] FS: 00007f6b1d16e8c0(0000) GS:ffff88839d700000(0000) knlGS:0000000000000000<br /> [ 40.212250][ T184] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 40.213275][ T184] CR2: 000055a1001d4ff0 CR3: 00000001700f4000 CR4: 00000000000006e0<br /> [ 40.214469][ T184] Call Trace:<br /> [ 40.214974][ T184] <br /> [ 40.215438][ T184] ? ttm_bo_bounce_temp_buffer+0x140/0x140 [ttm]<br /> [ 40.216572][ T184] ? mutex_spin_on_owner+0x240/0x240<br /> [ 40.217456][ T184] ? drm_vma_offset_add+0xaa/0x100 [drm]<br /> [ 40.218457][ T184] ttm_bo_init_reserved+0x3d6/0x540 [ttm]<br /> [ 40.219410][ T184] ? shmem_get_inode+0x744/0x980<br /> [ 40.220231][ T184] ttm_bo_init_validate+0xb1/0x200 [ttm]<br /> [ 40.221172][ T184] ? bo_driver_evict_flags+0x340/0x340 [drm_vram_helper]<br /> [ 40.222530][ T184] ? ttm_bo_init_reserved+0x540/0x540 [ttm]<br /> [ 40.223643][ T184] ? __do_sys_finit_module+0x11a/0x1c0<br /> [ 40.224654][ T184] ? __shmem_file_setup+0x102/0x280<br /> [ 40.234764][ T184] drm_gem_vram_create+0x305/0x480 [drm_vram_helper]<br /> [ 40.235766][ T184] ? bo_driver_evict_flags+0x340/0x340 [drm_vram_helper]<br /> [ 40.236846][ T184] ? __kasan_slab_free+0x108/0x180<br /> [ 40.237650][ T184] drm_gem_vram_fill_create_dumb+0x134/0x340 [drm_vram_helper]<br /> [ 40.238864][ T184] ? local_pci_probe+0xdf/0x180<br /> [ 40.239674][ T184] ? drmm_vram_helper_init+0x400/0x400 [drm_vram_helper]<br /> [ 40.240826][ T184] drm_client_framebuffer_create+0x19c/0x400 [drm]<br /> [ 40.241955][ T184] ? drm_client_buffer_delete+0x200/0x200 [drm]<br /> [ 40.243001][ T184] ? drm_client_pick_crtcs+0x554/0xb80 [drm]<br /> [ 40.244030][ T184] drm_fb_helper_generic_probe+0x23f/0x940 [drm_kms_helper]<br /> [ 40.245226][ T184] ? __cond_resched+0x1c/0xc0<br /> [ 40.245987][ T184] ? drm_fb_helper_memory_range_to_clip+0x180/0x180 [drm_kms_helper]<br /> [ 40.247316][ T184] ? mutex_unlock+0x80/0x100<br /> [ 40.248005][ T184] ? __mutex_unlock_slowpath+0x2c0/0x2c0<br /> [ 40.249083][ T184] drm_fb_helper_single_fb_probe+0x907/0xf00 [drm_kms_helper]<br /> [ 40.250314][ T184] ? drm_fb_helper_check_var+0x1180/0x1180 [drm_kms_helper]<br /> [ 40.251540][ T184] ? __cond_resched+0x1c/0xc0<br /> [ 40.252321][ T184] ? mutex_lock+0x9f/0x100<br /> [ 40.253062][ T184] __drm_fb_helper_initial_config_and_unlock+0xb9/0x2c0 [drm_kms_helper]<br /> [ 40.254394][ T184] drm_fbdev_client_hotplug+0x56f/0x840 [drm_kms_helper]<br /> [ 40.255477][ T184] drm_fbdev_generic_setup+0x165/0x3c0 [drm_kms_helper]<br /> [ 40.256607][ T184] bochs_pci_probe+0x6b7/0x900 [bochs]<br /> [ <br /> ---truncated---
Severity CVSS v4.0: Pending analysis
Last modification:
17/11/2025

CVE-2022-50067

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()<br /> <br /> In btrfs_relocate_block_group(), the rc is allocated. Then<br /> btrfs_relocate_block_group() calls<br /> <br /> relocate_block_group()<br /> prepare_to_relocate()<br /> set_reloc_control()<br /> <br /> that assigns rc to the variable fs_info-&gt;reloc_ctl. When<br /> prepare_to_relocate() returns, it calls<br /> <br /> btrfs_commit_transaction()<br /> btrfs_start_dirty_block_groups()<br /> btrfs_alloc_path()<br /> kmem_cache_zalloc()<br /> <br /> which may fail for example (or other errors could happen). When the<br /> failure occurs, btrfs_relocate_block_group() detects the error and frees<br /> rc and doesn&amp;#39;t set fs_info-&gt;reloc_ctl to NULL. After that, in<br /> btrfs_init_reloc_root(), rc is retrieved from fs_info-&gt;reloc_ctl and<br /> then used, which may cause a use-after-free bug.<br /> <br /> This possible bug can be triggered by calling btrfs_ioctl_balance()<br /> before calling btrfs_ioctl_defrag().<br /> <br /> To fix this possible bug, in prepare_to_relocate(), check if<br /> btrfs_commit_transaction() fails. If the failure occurs,<br /> unset_reloc_control() is called to set fs_info-&gt;reloc_ctl to NULL.<br /> <br /> The error log in our fault-injection testing is shown as follows:<br /> <br /> [ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs]<br /> ...<br /> [ 58.753577] Call Trace:<br /> ...<br /> [ 58.755800] kasan_report+0x45/0x60<br /> [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs]<br /> [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs]<br /> [ 58.757748] btrfs_record_root_in_trans+0x463/0x4f0 [btrfs]<br /> [ 58.758231] start_transaction+0x896/0x2950 [btrfs]<br /> [ 58.758661] btrfs_defrag_root+0x250/0xc00 [btrfs]<br /> [ 58.759083] btrfs_ioctl_defrag+0x467/0xa00 [btrfs]<br /> [ 58.759513] btrfs_ioctl+0x3c95/0x114e0 [btrfs]<br /> ...<br /> [ 58.768510] Allocated by task 23683:<br /> [ 58.768777] ____kasan_kmalloc+0xb5/0xf0<br /> [ 58.769069] __kmalloc+0x227/0x3d0<br /> [ 58.769325] alloc_reloc_control+0x10a/0x3d0 [btrfs]<br /> [ 58.769755] btrfs_relocate_block_group+0x7aa/0x1e20 [btrfs]<br /> [ 58.770228] btrfs_relocate_chunk+0xf1/0x760 [btrfs]<br /> [ 58.770655] __btrfs_balance+0x1326/0x1f10 [btrfs]<br /> [ 58.771071] btrfs_balance+0x3150/0x3d30 [btrfs]<br /> [ 58.771472] btrfs_ioctl_balance+0xd84/0x1410 [btrfs]<br /> [ 58.771902] btrfs_ioctl+0x4caa/0x114e0 [btrfs]<br /> ...<br /> [ 58.773337] Freed by task 23683:<br /> ...<br /> [ 58.774815] kfree+0xda/0x2b0<br /> [ 58.775038] free_reloc_control+0x1d6/0x220 [btrfs]<br /> [ 58.775465] btrfs_relocate_block_group+0x115c/0x1e20 [btrfs]<br /> [ 58.775944] btrfs_relocate_chunk+0xf1/0x760 [btrfs]<br /> [ 58.776369] __btrfs_balance+0x1326/0x1f10 [btrfs]<br /> [ 58.776784] btrfs_balance+0x3150/0x3d30 [btrfs]<br /> [ 58.777185] btrfs_ioctl_balance+0xd84/0x1410 [btrfs]<br /> [ 58.777621] btrfs_ioctl+0x4caa/0x114e0 [btrfs]<br /> ...
Severity CVSS v4.0: Pending analysis
Last modification:
17/11/2025

CVE-2022-50066

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: atlantic: fix aq_vec index out of range error<br /> <br /> The final update statement of the for loop exceeds the array range, the<br /> dereference of self-&gt;aq_vec[i] is not checked and then leads to the<br /> index out of range error.<br /> Also fixed this kind of coding style in other for loop.<br /> <br /> [ 97.937604] UBSAN: array-index-out-of-bounds in drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1404:48<br /> [ 97.937607] index 8 is out of range for type &amp;#39;aq_vec_s *[8]&amp;#39;<br /> [ 97.937608] CPU: 38 PID: 3767 Comm: kworker/u256:18 Not tainted 5.19.0+ #2<br /> [ 97.937610] Hardware name: Dell Inc. Precision 7865 Tower/, BIOS 1.0.0 06/12/2022<br /> [ 97.937611] Workqueue: events_unbound async_run_entry_fn<br /> [ 97.937616] Call Trace:<br /> [ 97.937617] <br /> [ 97.937619] dump_stack_lvl+0x49/0x63<br /> [ 97.937624] dump_stack+0x10/0x16<br /> [ 97.937626] ubsan_epilogue+0x9/0x3f<br /> [ 97.937627] __ubsan_handle_out_of_bounds.cold+0x44/0x49<br /> [ 97.937629] ? __scm_send+0x348/0x440<br /> [ 97.937632] ? aq_vec_stop+0x72/0x80 [atlantic]<br /> [ 97.937639] aq_nic_stop+0x1b6/0x1c0 [atlantic]<br /> [ 97.937644] aq_suspend_common+0x88/0x90 [atlantic]<br /> [ 97.937648] aq_pm_suspend_poweroff+0xe/0x20 [atlantic]<br /> [ 97.937653] pci_pm_suspend+0x7e/0x1a0<br /> [ 97.937655] ? pci_pm_suspend_noirq+0x2b0/0x2b0<br /> [ 97.937657] dpm_run_callback+0x54/0x190<br /> [ 97.937660] __device_suspend+0x14c/0x4d0<br /> [ 97.937661] async_suspend+0x23/0x70<br /> [ 97.937663] async_run_entry_fn+0x33/0x120<br /> [ 97.937664] process_one_work+0x21f/0x3f0<br /> [ 97.937666] worker_thread+0x4a/0x3c0<br /> [ 97.937668] ? process_one_work+0x3f0/0x3f0<br /> [ 97.937669] kthread+0xf0/0x120<br /> [ 97.937671] ? kthread_complete_and_exit+0x20/0x20<br /> [ 97.937672] ret_from_fork+0x22/0x30<br /> [ 97.937676] <br /> <br /> v2. fixed "warning: variable &amp;#39;aq_vec&amp;#39; set but not used"<br /> <br /> v3. simplified a for loop
Severity CVSS v4.0: Pending analysis
Last modification:
17/11/2025

CVE-2022-50065

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> virtio_net: fix memory leak inside XPD_TX with mergeable<br /> <br /> When we call xdp_convert_buff_to_frame() to get xdpf, if it returns<br /> NULL, we should check if xdp_page was allocated by xdp_linearize_page().<br /> If it is newly allocated, it should be freed here alone. Just like any<br /> other "goto err_xdp".
Severity CVSS v4.0: Pending analysis
Last modification:
17/11/2025

CVE-2022-50062

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: bgmac: Fix a BUG triggered by wrong bytes_compl<br /> <br /> On one of our machines we got:<br /> <br /> kernel BUG at lib/dynamic_queue_limits.c:27!<br /> Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM<br /> CPU: 0 PID: 1166 Comm: irq/41-bgmac Tainted: G W O 4.14.275-rt132 #1<br /> Hardware name: BRCM XGS iProc<br /> task: ee3415c0 task.stack: ee32a000<br /> PC is at dql_completed+0x168/0x178<br /> LR is at bgmac_poll+0x18c/0x6d8<br /> pc : [] lr : [] psr: 800a0313<br /> sp : ee32be14 ip : 000005ea fp : 00000bd4<br /> r10: ee558500 r9 : c0116298 r8 : 00000002<br /> r7 : 00000000 r6 : ef128810 r5 : 01993267 r4 : 01993851<br /> r3 : ee558000 r2 : 000070e1 r1 : 00000bd4 r0 : ee52c180<br /> Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none<br /> Control: 12c5387d Table: 8e88c04a DAC: 00000051<br /> Process irq/41-bgmac (pid: 1166, stack limit = 0xee32a210)<br /> Stack: (0xee32be14 to 0xee32c000)<br /> be00: ee558520 ee52c100 ef128810<br /> be20: 00000000 00000002 c0116298 c04b5a18 00000000 c0a0c8c4 c0951780 00000040<br /> be40: c0701780 ee558500 ee55d520 ef05b340 ef6f9780 ee558520 00000001 00000040<br /> be60: ffffe000 c0a56878 ef6fa040 c0952040 0000012c c0528744 ef6f97b0 fffcfb6a<br /> be80: c0a04104 2eda8000 c0a0c4ec c0a0d368 ee32bf44 c0153534 ee32be98 ee32be98<br /> bea0: ee32bea0 ee32bea0 ee32bea8 ee32bea8 00000000 c01462e4 ffffe000 ef6f22a8<br /> bec0: ffffe000 00000008 ee32bee4 c0147430 ffffe000 c094a2a8 00000003 ffffe000<br /> bee0: c0a54528 00208040 0000000c c0a0c8c4 c0a65980 c0124d3c 00000008 ee558520<br /> bf00: c094a23c c0a02080 00000000 c07a9910 ef136970 ef136970 ee30a440 ef136900<br /> bf20: ee30a440 00000001 ef136900 ee30a440 c016d990 00000000 c0108db0 c012500c<br /> bf40: ef136900 c016da14 ee30a464 ffffe000 00000001 c016dd14 00000000 c016db28<br /> bf60: ffffe000 ee21a080 ee30a400 00000000 ee32a000 ee30a440 c016dbfc ee25fd70<br /> bf80: ee21a09c c013edcc ee32a000 ee30a400 c013ec7c 00000000 00000000 00000000<br /> bfa0: 00000000 00000000 00000000 c0108470 00000000 00000000 00000000 00000000<br /> bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000<br /> bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000<br /> [] (dql_completed) from [] (bgmac_poll+0x18c/0x6d8)<br /> [] (bgmac_poll) from [] (net_rx_action+0x1c4/0x494)<br /> [] (net_rx_action) from [] (do_current_softirqs+0x1ec/0x43c)<br /> [] (do_current_softirqs) from [] (__local_bh_enable+0x80/0x98)<br /> [] (__local_bh_enable) from [] (irq_forced_thread_fn+0x84/0x98)<br /> [] (irq_forced_thread_fn) from [] (irq_thread+0x118/0x1c0)<br /> [] (irq_thread) from [] (kthread+0x150/0x158)<br /> [] (kthread) from [] (ret_from_fork+0x14/0x24)<br /> Code: a83f15e0 0200001a 0630a0e1 c3ffffea (f201f0e7)<br /> <br /> The issue seems similar to commit 90b3b339364c ("net: hisilicon: Fix a BUG<br /> trigered by wrong bytes_compl") and potentially introduced by commit<br /> b38c83dd0866 ("bgmac: simplify tx ring index handling").<br /> <br /> If there is an RX interrupt between setting ring-&gt;end<br /> and netdev_sent_queue() we can hit the BUG_ON as bgmac_dma_tx_free()<br /> can miscalculate the queue size while called from bgmac_poll().<br /> <br /> The machine which triggered the BUG runs a v4.14 RT kernel - but the issue<br /> seems present in mainline too.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50061

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map<br /> <br /> of_parse_phandle() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when not need anymore.<br /> Add missing of_node_put() to avoid refcount leak."
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50056

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Fix missing i_op in ntfs_read_mft<br /> <br /> There is null pointer dereference because i_op == NULL.<br /> The bug happens because we don&amp;#39;t initialize i_op for records in $Extend.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50057

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr<br /> <br /> If ntfs_fill_super() wasn&amp;#39;t called then sbi-&gt;sb will be equal to NULL.<br /> Code should check this ptr before dereferencing. Syzbot hit this issue<br /> via passing wrong mount param as can be seen from log below<br /> <br /> Fail log:<br /> ntfs3: Unknown parameter &amp;#39;iochvrset&amp;#39;<br /> general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN<br /> KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]<br /> CPU: 1 PID: 3589 Comm: syz-executor210 Not tainted 5.18.0-rc3-syzkaller-00016-gb253435746d9 #0<br /> ...<br /> Call Trace:<br /> <br /> put_ntfs+0x1ed/0x2a0 fs/ntfs3/super.c:463<br /> ntfs_fs_free+0x6a/0xe0 fs/ntfs3/super.c:1363<br /> put_fs_context+0x119/0x7a0 fs/fs_context.c:469<br /> do_new_mount+0x2b4/0xad0 fs/namespace.c:3044<br /> do_mount fs/namespace.c:3383 [inline]<br /> __do_sys_mount fs/namespace.c:3591 [inline]
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50058

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> vdpa_sim_blk: set number of address spaces and virtqueue groups<br /> <br /> Commit bda324fd037a ("vdpasim: control virtqueue support") added two<br /> new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to<br /> initialize them for vdpa_sim_blk.<br /> <br /> When creating a new vdpa_sim_blk device this causes the kernel<br /> to panic in this way:<br />    $ vdpa dev add mgmtdev vdpasim_blk name blk0<br />    BUG: kernel NULL pointer dereference, address: 0000000000000030<br />    ...<br />    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]<br />    ...<br />    Call Trace:<br />     <br />     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]<br />     vdpasim_map_range+0x91/0xd0 [vdpa_sim]<br />     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]<br />     ...<br /> <br /> This happens because vdpasim-&gt;iommu[0] is not initialized when<br /> dev_attr.nas is 0.<br /> <br /> Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for<br /> vdpa_sim_blk.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50059

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ceph: don&amp;#39;t leak snap_rwsem in handle_cap_grant<br /> <br /> When handle_cap_grant is called on an IMPORT op, then the snap_rwsem is<br /> held and the function is expected to release it before returning. It<br /> currently fails to do that in all cases which could lead to a deadlock.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50060

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> octeontx2-af: Fix mcam entry resource leak<br /> <br /> The teardown sequence in FLR handler returns if no NIX LF<br /> is attached to PF/VF because it indicates that graceful<br /> shutdown of resources already happened. But there is a<br /> chance of all allocated MCAM entries not being freed by<br /> PF/VF. Hence free mcam entries even in case of detached LF.
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025

CVE-2022-50054

Publication date:
18/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iavf: Fix NULL pointer dereference in iavf_get_link_ksettings<br /> <br /> Fix possible NULL pointer dereference, due to freeing of adapter-&gt;vf_res<br /> in iavf_init_get_resources. Previous commit introduced a regression,<br /> where receiving IAVF_ERR_ADMIN_QUEUE_NO_WORK from iavf_get_vf_config<br /> would free adapter-&gt;vf_res. However, netdev is still registered, so<br /> ethtool_ops can be called. Calling iavf_get_link_ksettings with no vf_res,<br /> will result with:<br /> [ 9385.242676] BUG: kernel NULL pointer dereference, address: 0000000000000008<br /> [ 9385.242683] #PF: supervisor read access in kernel mode<br /> [ 9385.242686] #PF: error_code(0x0000) - not-present page<br /> [ 9385.242690] PGD 0 P4D 0<br /> [ 9385.242696] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC PTI<br /> [ 9385.242701] CPU: 6 PID: 3217 Comm: pmdalinux Kdump: loaded Tainted: G S E 5.18.0-04958-ga54ce3703613-dirty #1<br /> [ 9385.242708] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.11.0 11/02/2019<br /> [ 9385.242710] RIP: 0010:iavf_get_link_ksettings+0x29/0xd0 [iavf]<br /> [ 9385.242745] Code: 00 0f 1f 44 00 00 b8 01 ef ff ff 48 c7 46 30 00 00 00 00 48 c7 46 38 00 00 00 00 c6 46 0b 00 66 89 46 08 48 8b 87 68 0e 00 00 40 08 80 75 50 8b 87 5c 0e 00 00 83 f8 08 74 7a 76 1d 83 f8 20<br /> [ 9385.242749] RSP: 0018:ffffc0560ec7fbd0 EFLAGS: 00010246<br /> [ 9385.242755] RAX: 0000000000000000 RBX: ffffc0560ec7fc08 RCX: 0000000000000000<br /> [ 9385.242759] RDX: ffffffffc0ad4550 RSI: ffffc0560ec7fc08 RDI: ffffa0fc66674000<br /> [ 9385.242762] RBP: 00007ffd1fb2bf50 R08: b6a2d54b892363ee R09: ffffa101dc14fb00<br /> [ 9385.242765] R10: 0000000000000000 R11: 0000000000000004 R12: ffffa0fc66674000<br /> [ 9385.242768] R13: 0000000000000000 R14: ffffa0fc66674000 R15: 00000000ffffffa1<br /> [ 9385.242771] FS: 00007f93711a2980(0000) GS:ffffa0fad72c0000(0000) knlGS:0000000000000000<br /> [ 9385.242775] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 9385.242778] CR2: 0000000000000008 CR3: 0000000a8e61c003 CR4: 00000000003706e0<br /> [ 9385.242781] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> [ 9385.242784] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> [ 9385.242787] Call Trace:<br /> [ 9385.242791] <br /> [ 9385.242793] ethtool_get_settings+0x71/0x1a0<br /> [ 9385.242814] __dev_ethtool+0x426/0x2f40<br /> [ 9385.242823] ? slab_post_alloc_hook+0x4f/0x280<br /> [ 9385.242836] ? kmem_cache_alloc_trace+0x15d/0x2f0<br /> [ 9385.242841] ? dev_ethtool+0x59/0x170<br /> [ 9385.242848] dev_ethtool+0xa7/0x170<br /> [ 9385.242856] dev_ioctl+0xc3/0x520<br /> [ 9385.242866] sock_do_ioctl+0xa0/0xe0<br /> [ 9385.242877] sock_ioctl+0x22f/0x320<br /> [ 9385.242885] __x64_sys_ioctl+0x84/0xc0<br /> [ 9385.242896] do_syscall_64+0x3a/0x80<br /> [ 9385.242904] entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> [ 9385.242918] RIP: 0033:0x7f93702396db<br /> [ 9385.242923] Code: 73 01 c3 48 8b 0d ad 57 38 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 00 00 00 0f 05 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7d 57 38 00 f7 d8 64 89 01 48<br /> [ 9385.242927] RSP: 002b:00007ffd1fb2bf18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010<br /> [ 9385.242932] RAX: ffffffffffffffda RBX: 000055671b1d2fe0 RCX: 00007f93702396db<br /> [ 9385.242935] RDX: 00007ffd1fb2bf20 RSI: 0000000000008946 RDI: 0000000000000007<br /> [ 9385.242937] RBP: 00007ffd1fb2bf20 R08: 0000000000000003 R09: 0030763066307330<br /> [ 9385.242940] R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd1fb2bf80<br /> [ 9385.242942] R13: 0000000000000007 R14: 0000556719f6de90 R15: 00007ffd1fb2c1b0<br /> [ 9385.242948] <br /> [ 9385.242949] Modules linked in: iavf(E) xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nft_compat nf_nat_tftp nft_objref nf_conntrack_tftp bridge stp llc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables rfkill nfnetlink vfat fat irdma ib_uverbs ib_core intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretem<br /> ---truncated---
Severity CVSS v4.0: Pending analysis
Last modification:
13/11/2025