In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32 *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -1 0000000000000058 <LBB5_3>: 11: r1 = 0 ll 13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit 00000000000000b8 <LBB5_5>: 23: w0 = 0 24: exit For the first case, the single line execution's exploration will prune the search at insn 14 for the branch insn 9's second leg as it will be verified first using r2 = -1 (UINT_MAX), while as w1 at insn 9 will always be 0 so at runtime we don't get error for being greater than UINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe just sees reg->precise as false for both r2 registers in both states, hence considers them equal for purposes of states_equal. If we propagated precise markers using the backtracking support, we would use the precise marking to then ensure that old r2 (UINT_MAX) was within the new r2 (1) and this would never be true, so the verification would rightfully fail. The end result is that the out of bounds access at instruction 19 would be permitted without this fix. Note that reg->precise is always set to true when user does not have CAP_BPF (or when subprog count is greater than 1 (i.e. use of any static or global functions)), hence this is only a problem when precision marks need to be explicitly propagated (i.e. privileged users with CAP_BPF). A simplified test case has been included in the next patch to prevent future regressions.

The CentOS Linux 8.4 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.4:CLSA-2026:1791858083 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix use-after-free of encap     entry in neigh update handler Function mlx5e_rep_neigh_update() wasn't updated to accommodate rtnl lock     removal from TC filter update path and properly handle concurrent encap entry insertion/deletion which can     lead to following use-after-free: [23827.464923]     ================================================================== [23827.469446] BUG: KASAN: use-after-     free in mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.470971] Read of size 4 at addr ffff8881d132228c by     task kworker/u20:6/21635 [23827.472251] [23827.472615] CPU: 9 PID: 21635 Comm: kworker/u20:6 Not tainted     5.13.0-rc3+ #5 [23827.473788] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS     rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [23827.475639] Workqueue: mlx5e     mlx5e_rep_neigh_update [mlx5_core] [23827.476731] Call Trace: [23827.477260] dump_stack+0xbb/0x107     [23827.477906] print_address_description.constprop.0+0x18/0x140 [23827.478896] ?     mlx5e_encap_take+0x72/0x140 [mlx5_core] [23827.479879] ? mlx5e_encap_take+0x72/0x140 [mlx5_core]     [23827.480905] kasan_report.cold+0x7c/0xd8 [23827.481701] ? mlx5e_encap_take+0x72/0x140 [mlx5_core]     [23827.482744] kasan_check_range+0x145/0x1a0 [23827.493112] mlx5e_encap_take+0x72/0x140 [mlx5_core]     [23827.494054] ? mlx5e_tc_tun_encap_info_equal_generic+0x140/0x140 [mlx5_core] [23827.495296]     mlx5e_rep_neigh_update+0x41e/0x5e0 [mlx5_core] [23827.496338] ? mlx5e_rep_neigh_entry_release+0xb80/0xb80     [mlx5_core] [23827.497486] ? read_word_at_a_time+0xe/0x20 [23827.498250] ? strscpy+0xa0/0x2a0     [23827.498889] process_one_work+0x8ac/0x14e0 [23827.499638] ? lockdep_hardirqs_on_prepare+0x400/0x400     [23827.500537] ? pwq_dec_nr_in_flight+0x2c0/0x2c0 [23827.501359] ? rwlock_bug.part.0+0x90/0x90     [23827.502116] worker_thread+0x53b/0x1220 [23827.502831] ? process_one_work+0x14e0/0x14e0 [23827.503627]     kthread+0x328/0x3f0 [23827.504254] ? _raw_spin_unlock_irq+0x24/0x40 [23827.505065] ?
    __kthread_bind_mask+0x90/0x90 [23827.505912] ret_from_fork+0x1f/0x30 [23827.506621] [23827.506987]     Allocated by task 28248: [23827.507694] kasan_save_stack+0x1b/0x40 [23827.508476]
    __kasan_kmalloc+0x7c/0x90 [23827.509197] mlx5e_attach_encap+0xde1/0x1d40 [mlx5_core] [23827.510194]     mlx5e_tc_add_fdb_flow+0x397/0xc40 [mlx5_core] [23827.511218] __mlx5e_add_fdb_flow+0x519/0xb30 [mlx5_core]     [23827.512234] mlx5e_configure_flower+0x191c/0x4870 [mlx5_core] [23827.513298] tc_setup_cb_add+0x1d5/0x420     [23827.514023] fl_hw_replace_filter+0x382/0x6a0 [cls_flower] [23827.514975] fl_change+0x2ceb/0x4a51     [cls_flower] [23827.515821] tc_new_tfilter+0x89a/0x2070 [23827.516548] rtnetlink_rcv_msg+0x644/0x8c0     [23827.517300] netlink_rcv_skb+0x11d/0x340 [23827.518021] netlink_unicast+0x42b/0x700 [23827.518742]     netlink_sendmsg+0x743/0xc20 [23827.519467] sock_sendmsg+0xb2/0xe0 [23827.520131]
    ____sys_sendmsg+0x590/0x770 [23827.520851] ___sys_sendmsg+0xd8/0x160 [23827.521552]
    __sys_sendmsg+0xb7/0x140 [23827.522238] do_syscall_64+0x3a/0x70 [23827.522907]     entry_SYSCALL_64_after_hwframe+0x44/0xae [23827.523797] [23827.524163] Freed by task 25948: [23827.524780]     kasan_save_stack+0x1b/0x40 [23827.525488] kasan_set_track+0x1c/0x30 [23827.526187]     kasan_set_free_info+0x20/0x30 [23827.526968] __kasan_slab_free+0xed/0x130 [23827.527709]     slab_free_freelist_hook+0xcf/0x1d0 [23827.528528] kmem_cache_free_bulk+0x33a/0x6e0 [23827.529317]     kfree_rcu_work+0x55f/0xb70 [23827.530024] process_one_work+0x8ac/0x14e0 [23827.530770]     worker_thread+0x53b/0x1220 [23827.531480] kthread+0x328/0x3f0 [23827.532114] ret_from_fork+0x1f/0x30     [23827.532785] [23827.533147] Last potentially related work creation: [23827.534007]     kasan_save_stack+0x1b/0x40 [23827.534710] kasan_record_aux_stack+0xab/0xc0 [23827.535492]     kvfree_call_rcu+0x31/0x7b0 [23827.536206] mlx5e_tc_del ---truncated--- (CVE-2021-47247)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for     ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style     argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of     states_equal check when such arguments refine the return value (in this case, set mem_size for     PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier     incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both     registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier     which can do access beyond what should have been the correct mem_size in that explored state. To show a     concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 +     76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32
    *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -1 0000000000000058 <LBB5_3>: 11: r1 = 0 ll     13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18:
    w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit 00000000000000b8     <LBB5_5>: 23: w0 = 0 24: exit For the first case, the single line execution's exploration will prune the     search at insn 14 for the branch insn 9's second leg as it will be verified first using r2 = -1     (UINT_MAX), while as w1 at insn 9 will always be 0 so at runtime we don't get error for being greater than     UINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe just sees reg->precise as false for both     r2 registers in both states, hence considers them equal for purposes of states_equal. If we propagated     precise markers using the backtracking support, we would use the precise marking to then ensure that old     r2 (UINT_MAX) was within the new r2 (1) and this would never be true, so the verification would rightfully     fail. The end result is that the out of bounds access at instruction 19 would be permitted without this     fix. Note that reg->precise is always set to true when user does not have CAP_BPF (or when subprog count     is greater than 1 (i.e. use of any static or global functions)), hence this is only a problem when     precision marks need to be explicitly propagated (i.e. privileged users with CAP_BPF). A simplified test     case has been included in the next patch to prevent future regressions. (CVE-2022-49961)

  - In the Linux kernel, the following vulnerability has been resolved: nfsd: under NFSv4.1, fix double     svc_xprt_put on rpc_create failure On error situation `clp->cl_cb_conn.cb_xprt` should not be given a     reference to the xprt otherwise both client cleanup and the error handling path of the caller call to put     it. Better to delay handing over the reference to a later branch. [ 72.530665] refcount_t: underflow; use-     after-free. [ 72.531933] WARNING: CPU: 0 PID: 173 at lib/refcount.c:28 refcount_warn_saturate+0xcf/0x120 [     72.533075] Modules linked in: nfsd(OE) nfsv4(OE) nfsv3(OE) nfs(OE) lockd(OE) compat_nfs_ssc(OE)     nfs_acl(OE) rpcsec_gss_krb5(OE) auth_rpcgss(OE) rpcrdma(OE) dns_resolver fscache netfs grace rdma_cm iw_cm     ib_cm sunrpc(OE) mlx5_ib mlx5_core mlxfw pci_hyperv_intf ib_uverbs ib_core xt_MASQUERADE     nf_conntrack_netlink nft_counter xt_addrtype nft_compat br_netfilter bridge stp llc 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 overlay nf_tables nfnetlink crct10dif_pclmul crc32_pclmul ghash_clmulni_intel xfs     serio_raw virtio_net virtio_blk net_failover failover fuse [last unloaded: sunrpc] [ 72.540389] CPU: 0     PID: 173 Comm: kworker/u16:5 Tainted: G OE 5.15.82-dan #1 [ 72.541511] Hardware name: Red Hat KVM/RHEL-AV,     BIOS 1.16.0-3.module+el8.7.0+1084+97b81f61 04/01/2014 [ 72.542717] Workqueue: nfsd4_callbacks     nfsd4_run_cb_work [nfsd] [ 72.543575] RIP: 0010:refcount_warn_saturate+0xcf/0x120 [ 72.544299] Code: 55 00     0f 0b 5d e9 01 50 98 00 80 3d 75 9e 39 08 00 0f 85 74 ff ff ff 48 c7 c7 e8 d1 60 8e c6 05 61 9e 39 08 01     e8 f6 51 55 00 <0f> 0b 5d e9 d9 4f 98 00 80 3d 4b 9e 39 08 00 0f 85 4c ff ff ff 48 [ 72.546666] RSP:
    0018:ffffb3f841157cf0 EFLAGS: 00010286 [ 72.547393] RAX: 0000000000000026 RBX: ffff89ac6231d478 RCX:
    0000000000000000 [ 72.548324] RDX: ffff89adb7c2c2c0 RSI: ffff89adb7c205c0 RDI: ffff89adb7c205c0 [     72.549271] RBP: ffffb3f841157cf0 R08: 0000000000000000 R09: c0000000ffefffff [ 72.550209] R10:
    0000000000000001 R11: ffffb3f841157ad0 R12: ffff89ac6231d180 [ 72.551142] R13: ffff89ac6231d478 R14:
    ffff89ac40c06180 R15: ffff89ac6231d4b0 [ 72.552089] FS: 0000000000000000(0000) GS:ffff89adb7c00000(0000)     knlGS:0000000000000000 [ 72.553175] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 72.553934] CR2:
    0000563a310506a8 CR3: 0000000109a66000 CR4: 0000000000350ef0 [ 72.554874] Call Trace: [ 72.555278] <TASK>     [ 72.555614] svc_xprt_put+0xaf/0xe0 [sunrpc] [ 72.556276] nfsd4_process_cb_update.isra.11+0xb7/0x410     [nfsd] [ 72.557087] ? update_load_avg+0x82/0x610 [ 72.557652] ? cpuacct_charge+0x60/0x70 [ 72.558212] ?     dequeue_entity+0xdb/0x3e0 [ 72.558765] ? queued_spin_unlock+0x9/0x20 [ 72.559358]     nfsd4_run_cb_work+0xfc/0x270 [nfsd] [ 72.560031] process_one_work+0x1df/0x390 [ 72.560600]     worker_thread+0x37/0x3b0 [ 72.561644] ? process_one_work+0x390/0x390 [ 72.562247] kthread+0x12f/0x150 [     72.562710] ? set_kthread_struct+0x50/0x50 [ 72.563309] ret_from_fork+0x22/0x30 [ 72.563818] </TASK> [     72.564189] ---[ end trace 031117b1c72ec616 ]--- [ 72.566019] list_add corruption. next->prev should be     prev (ffff89ac4977e538), but was ffff89ac4763e018. (next=ffff89ac4763e018). [ 72.567647] ------------[ cut     here ]------------ (CVE-2022-50401)

  - In the Linux kernel, the following vulnerability has been resolved: blk-mq: use quiesced elevator switch     when reinitializing queues The hctx's run_work may be racing with the elevator switch when reinitializing     hardware queues. The queue is merely frozen in this context, but that only prevents requests from     allocating and doesn't stop the hctx work from running. The work may get an elevator pointer that's being     torn down, and can result in use-after-free errors and kernel panics (example below). Use the quiesced     elevator switch instead, and make the previous one static since it is now only used locally. nvme nvme0:
    resetting controller nvme nvme0: 32/0/0 default/read/poll queues BUG: kernel NULL pointer dereference,     address: 0000000000000008 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present     page PGD 80000020c8861067 P4D 80000020c8861067 PUD 250f8c8067 PMD 0 Oops: 0000 [#1] SMP PTI Workqueue:
    kblockd blk_mq_run_work_fn RIP: 0010:kyber_has_work+0x29/0x70 ... Call Trace:
    __blk_mq_do_dispatch_sched+0x83/0x2b0 __blk_mq_sched_dispatch_requests+0x12e/0x170     blk_mq_sched_dispatch_requests+0x30/0x60 __blk_mq_run_hw_queue+0x2b/0x50 process_one_work+0x1ef/0x380     worker_thread+0x2d/0x3e0 (CVE-2022-50552)

  - The current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The     ib_prctl_set function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL     MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the     TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to     the prctl syscall. The patch that added the support for the conditional mitigation via prctl     (ib_prctl_set) dates back to the kernel 4.9.176. We recommend upgrading past commit     a664ec9158eeddd75121d39c9a0758016097fa96 (CVE-2023-0045)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The CentOS Linux 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2026:1792247642 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: ethtool: do not perform operations on     net devices being unregistered There is a short period between a net device starts to be unregistered and     when it is actually gone. In that time frame ethtool operations could still be performed, which might end     up in unwanted or undefined behaviours[1]. Do not allow ethtool operations after a net device starts its     unregistration. This patch targets the netlink part as the ioctl one isn't affected: the reference to the     net device is taken and the operation is executed within an rtnl lock section and the net device won't be     found after unregister. [1] For example adding Tx queues after unregister ends up in NULL pointer     exceptions and UaFs, such as: BUG: KASAN: use-after-free in kobject_get+0x14/0x90 Read of size 1 at addr     ffff88801961248c by task ethtool/755 CPU: 0 PID: 755 Comm: ethtool Not tainted 5.15.0-rc6+ #778 Hardware     name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-4.fc34 04/014 Call Trace:
    dump_stack_lvl+0x57/0x72 print_address_description.constprop.0+0x1f/0x140 kasan_report.cold+0x7f/0x11b     kobject_get+0x14/0x90 kobject_add_internal+0x3d1/0x450 kobject_init_and_add+0xba/0xf0     netdev_queue_update_kobjects+0xcf/0x200 netif_set_real_num_tx_queues+0xb4/0x310     veth_set_channels+0x1c3/0x550 ethnl_set_channels+0x524/0x610 (CVE-2021-47517)

  - In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix UAF when detecting     digest errors We should also bail from the io_work loop when we set rd_enabled to true, so we don't     attempt to read data from the socket when the TCP stream is already out-of-sync or corrupted.
    (CVE-2022-48686)

  - In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free after     802.3ad slave unbind commit 0622cab0341c (bonding: fix 802.3ad aggregator reselection), resolve case,     when there is several aggregation groups in the same bond. bond_3ad_unbind_slave will invalidate (clear)     aggregator when __agg_active_ports return zero. So, ad_clear_agg can be executed even, when     num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for, previously cleared aggregator.
    NOTE: at this time bond_3ad_unbind_slave will not update slave ports list, because lag_ports==NULL. So,     here we got slave ports, pointing to freed aggregator memory. Fix with checking actual number of ports in     group (as was before commit 0622cab0341c (bonding: fix 802.3ad aggregator reselection) ), before     ad_clear_agg(). The KASAN logs are as follows: [ 767.617392]     ================================================================== [ 767.630776] BUG: KASAN: use-after-     free in bond_3ad_state_machine_handler+0x13dc/0x1470 [ 767.638764] Read of size 2 at addr ffff00011ba9d430     by task kworker/u8:7/767 [ 767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G O 5.15.11 #15 [     767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT) [ 767.660760] Workqueue: lacp_1     bond_3ad_state_machine_handler [ 767.666468] Call trace: [ 767.668930] dump_backtrace+0x0/0x2d0 [     767.672625] show_stack+0x24/0x30 [ 767.675965] dump_stack_lvl+0x68/0x84 [ 767.679659]     print_address_description.constprop.0+0x74/0x2b8 [ 767.685451] kasan_report+0x1f0/0x260 [ 767.689148]
    __asan_load2+0x94/0xd0 [ 767.692667] bond_3ad_state_machine_handler+0x13dc/0x1470 (CVE-2022-49667)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for     ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style     argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of     states_equal check when such arguments refine the return value (in this case, set mem_size for     PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier     incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both     registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier     which can do access beyond what should have been the correct mem_size in that explored state. To show a     concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 +     76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32
    *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -1 0000000000000058 <LBB5_3>: 11: r1 = 0 ll     13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18:
    w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit 00000000000000b8     <LBB5_5>: 23: w0 = 0 24: exit For the first case, the single line execution's exploration will prune the     search at insn 14 for the branch insn 9's second leg as it will be verified first using r2 = -1     (UINT_MAX), while as w1 at insn 9 will always be 0 so at runtime we don't get error for being greater than     UINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe just sees reg->precise as false for both     r2 registers in both states, hence considers them equal for purposes of states_equal. If we propagated     precise markers using the backtracking support, we would use the precise marking to then ensure that old     r2 (UINT_MAX) was within the new r2 (1) and this would never be true, so the verification would rightfully     fail. The end result is that the out of bounds access at instruction 19 would be permitted without this     fix. Note that reg->precise is always set to true when user does not have CAP_BPF (or when subprog count     is greater than 1 (i.e. use of any static or global functions)), hence this is only a problem when     precision marks need to be explicitly propagated (i.e. privileged users with CAP_BPF). A simplified test     case has been included in the next patch to prevent future regressions. (CVE-2022-49961)

  - A use-after-free vulnerability was found in iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in     SCSI sub-component in the Linux Kernel. In this flaw an attacker could leak kernel internal information.
    (CVE-2023-2162)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS-STREAM8:CLSA-2026:1789141176 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Propagate error from     htab_lock_bucket() to userspace In __htab_map_lookup_and_delete_batch() if htab_lock_bucket() returns
    -EBUSY, it will go to next bucket. Going to next bucket may not only skip the elements in current bucket     silently, but also incur out-of-bound memory access or expose kernel memory to userspace if current     bucket_cnt is greater than bucket_size or zero. Fixing it by stopping batch operation and returning -EBUSY     when htab_lock_bucket() fails, and the application can retry or skip the busy batch as needed.
    (CVE-2022-50490)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: hpsa: Fix possible memory leak     in hpsa_init_one() The hpda_alloc_ctlr_info() allocates h and its field reply_map. However, in     hpsa_init_one(), if alloc_percpu() failed, the hpsa_init_one() jumps to clean1 directly, which frees h and     leaks the h->reply_map. Fix by calling hpda_free_ctlr_info() to release h->replay_map and h instead free h     directly. (CVE-2022-50646)

  - The current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The     ib_prctl_set function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL     MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the     TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to     the prctl syscall. The patch that added the support for the conditional mitigation via prctl     (ib_prctl_set) dates back to the kernel 4.9.176. We recommend upgrading past commit     a664ec9158eeddd75121d39c9a0758016097fa96 (CVE-2023-0045)

  - A flaw was found in the Linux kernel's IP framework for transforming packets (XFRM subsystem). This issue     may allow a malicious user with CAP_NET_ADMIN privileges to cause a 4 byte out-of-bounds read of     XFRMA_MTIMER_THRESH when parsing netlink attributes, leading to potential leakage of sensitive heap data     to userspace. (CVE-2023-3773)

  - In the Linux kernel, the following vulnerability has been resolved: fbdev: Fix invalid page access after     closing deferred I/O devices When a fbdev with deferred I/O is once opened and closed, the dirty pages     still remain queued in the pageref list, and eventually later those may be processed in the delayed work.
    This may lead to a corruption of pages, hitting an Oops. This patch makes sure to cancel the delayed work     and clean up the pageref list at closing the device for addressing the bug. A part of the cleanup code is     factored out as a new helper function that is called from the common fb_release(). (CVE-2023-52731)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8668-1 advisory.

    Maxim Suhanov discovered that the NTFS file system implementation in the Linux kernel did not properly     validate file name length in certain situations, leading to an out-of-bounds read. An attacker could use     this to construct a malicious NTFS image that, when mounted and operated on, could expose sensitive     information (kernel memory). (CVE-2023-45896)

    It was discovered that some AMD processors did not properly clear data in the floating point divider unit     during speculative execution. A local attacker could use this to expose sensitive information.
    (CVE-2025-54505)

    It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the     operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a     higher privilege level, resulting in privilege escalation. (CVE-2025-54518)

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - ATM drivers;

    - Drivers core;

    - Power management core;

    - DRBD Distributed Replicated Block Device drivers;

    - RNBD block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Character device driver;

    - TPM device driver;

    - Clocksource drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - CPU idle management framework;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - Arm Firmware Framework for ARMv8-A(FFA);

    - EFI core;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - IIO subsystem;

    - IIO ADC drivers;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - MediaTek SMI driver;

    - NVIDIA Tegra memory controller driver;

    - Multifunction device drivers;

    - IBM Advanced System Management driver;

    - MMC subsystem;

    - MTD block device drivers;

    - Network drivers;

    - Ethernet bonding driver;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - STMicroelectronics network drivers;

    - MediaTek network drivers;

    - Near Field Communication (NFC) drivers;

    - NTB driver;

    - NVDIMM (Non-Volatile Memory Device) drivers;

    - NVME drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Broadcom BCM2835 power domain driver;

    - Power supply drivers;

    - RapidIO drivers;

    - Remote Processor subsystem;

    - RPMSG subsystem;

    - SCSI subsystem;

    - Freescale SoC drivers;

    - Texas Instruments SoC drivers;

    - SPI subsystem;

    - Greybus lights staging drivers;

    - Media staging drivers;

    - Realtek RTL8723BS SDIO drivers;

    - SM750 framebuffer staging driver;

    - TCM subsystem;

    - TTY drivers;

    - UFS subsystem;

    - Cadence USB3 driver;

    - USB Device Class drivers;

    - ULPI bus;

    - USB core drivers;

    - DesignWare USB2 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Mustek MDC800 USB digital camera driver;

    - USB YUREX driver;

    - Renesas USBHS Controller drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - FUSE (File system in Userspace);

    - GFS2 file system;

    - HFS+ file system;

    - JFS file system;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - Proc file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - SquashFS file system;

    - UDF file system;

    - XFS file system;

    - Audit subsystem;

    - RAS (Reliability, Availability, Serviceability) subsystem;

    - Software nodes and device properties;

    - Memory Management;

    - KVM subsystem;

    - Memory management;

    - PPP protocol drivers and compressors;

    - Linux Security Modules (LSM) Framework;

    - Network traffic control;

    - Bluetooth subsystem;

    - MAC80211 subsystem;

    - Netfilter;

    - IP tunnels definitions;

    - Tracing infrastructure;

    - User-space API (UAPI);

    - io_uring subsystem;

    - BPF subsystem;

    - Control group (cgroup);

    - Kernel fork() syscall;

    - Kernel futex primitives;

    - Kernel kexec() syscall;

    - Kernel module support;

    - Scheduler infrastructure;

    - Cryptographic library;

    - KASAN memory debugging framework;

    - Asynchronous Transfer Mode (ATM) subsystem;

    - B.A.T.M.A.N. meshing protocol;

    - Ethernet bridge;

    - CAIF protocol;

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - Distributed Switch Architecture;

    - IPv4 networking;

    - IPv6 networking;

    - XFRM subsystem;

    - L2TP protocol;

    - Management Component Transport Protocol (MCTP);

    - Multipath TCP;

    - NCSI (Network Controller Sideband Interface) driver;

    - NFC subsystem;

    - Open vSwitch;

    - Phonet protocol;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - RF switch subsystem;

    - Rose network layer;

    - RxRPC session sockets;

    - SCTP protocol;

    - SMC sockets;

    - Stream parser;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - X.25 network layer;

    - eXpress Data Path;

    - AppArmor security module;

    - Simplified Mandatory Access Control Kernel framework;

    - ALSA framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - AudioScience HPI driver;

    - Creative Sound Blaster X-Fi driver;

    - AMD SoC Alsa drivers;

    - SoC audio core drivers;

    - STI ASoC drivers;

    - USB sound devices; (CVE-2022-49803, CVE-2022-49961, CVE-2022-50073, CVE-2022-50116, CVE-2022-50552,     CVE-2023-52682, CVE-2023-52737, CVE-2023-53545, CVE-2023-53596, CVE-2023-53629, CVE-2024-27389,     CVE-2024-35865, CVE-2024-36898, CVE-2024-36922, CVE-2024-41079, CVE-2024-46715, CVE-2024-46770,     CVE-2024-47809, CVE-2024-50012, CVE-2024-53221, CVE-2024-56557, CVE-2024-56584, CVE-2024-56657,     CVE-2024-56719, CVE-2024-56727, CVE-2025-21712, CVE-2025-21739, CVE-2025-21863, CVE-2025-22107,     CVE-2025-23141, CVE-2025-37786, CVE-2025-38006, CVE-2025-38105, CVE-2025-38192, CVE-2025-38250,     CVE-2025-38562, CVE-2025-38626, CVE-2025-38659, CVE-2025-38710, CVE-2025-39748, CVE-2025-39764,     CVE-2025-40005, CVE-2025-40016, CVE-2025-40103, CVE-2025-40323, CVE-2025-68206, CVE-2025-68239,     CVE-2025-68256, CVE-2025-68307, CVE-2025-68358, CVE-2025-71150, CVE-2025-71161, CVE-2025-71221,     CVE-2025-71232, CVE-2025-71233, CVE-2025-71235, CVE-2025-71236, CVE-2025-71237, CVE-2025-71238,     CVE-2025-71239, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71274, CVE-2025-71287,     CVE-2025-71292, CVE-2025-71304, CVE-2026-23031, CVE-2026-23066, CVE-2026-23100, CVE-2026-23113,     CVE-2026-23141, CVE-2026-23157, CVE-2026-23169, CVE-2026-23204, CVE-2026-23220, CVE-2026-23221,     CVE-2026-23222, CVE-2026-23227, CVE-2026-23228, CVE-2026-23229, CVE-2026-23234, CVE-2026-23235,     CVE-2026-23236, CVE-2026-23237, CVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,     CVE-2026-23253, CVE-2026-23266, CVE-2026-23270, CVE-2026-23277, CVE-2026-23279, CVE-2026-23281,     CVE-2026-23286, CVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23293, CVE-2026-23296,     CVE-2026-23298, CVE-2026-23300, CVE-2026-23303, CVE-2026-23304, CVE-2026-23307, CVE-2026-23312,     CVE-2026-23318, CVE-2026-23324, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,     CVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23362, CVE-2026-23365,     CVE-2026-23367, CVE-2026-23368, CVE-2026-23370, CVE-2026-23372, CVE-2026-23379, CVE-2026-23381,     CVE-2026-23382, CVE-2026-23388, CVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,     CVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23420, CVE-2026-23434,     CVE-2026-23438, CVE-2026-23439, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446, CVE-2026-23452,     CVE-2026-23454, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23462,     CVE-2026-23463, CVE-2026-23474, CVE-2026-31393, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,     CVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31415,     CVE-2026-31416, CVE-2026-31417, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423, CVE-2026-31424,     CVE-2026-31425, CVE-2026-31427, CVE-2026-31428, CVE-2026-31433, CVE-2026-31446, CVE-2026-31447,     CVE-2026-31450, CVE-2026-31452, CVE-2026-31454, CVE-2026-31455, CVE-2026-31464, CVE-2026-31466,     CVE-2026-31467, CVE-2026-31469, CVE-2026-31473, CVE-2026-31476, CVE-2026-31480, CVE-2026-31483,     CVE-2026-31485, CVE-2026-31489, CVE-2026-31494, CVE-2026-31495, CVE-2026-31497, CVE-2026-31498,     CVE-2026-31507, CVE-2026-31508, CVE-2026-31509, CVE-2026-31510, CVE-2026-31512, CVE-2026-31515,     CVE-2026-31518, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524, CVE-2026-31532,     CVE-2026-31540, CVE-2026-31545, CVE-2026-31546, CVE-2026-31549, CVE-2026-31550, CVE-2026-31551,     CVE-2026-31552, CVE-2026-31555, CVE-2026-31565, CVE-2026-31570, CVE-2026-31576, CVE-2026-31577,     CVE-2026-31578, CVE-2026-31580, CVE-2026-31581, CVE-2026-31583, CVE-2026-31585, CVE-2026-31586,     CVE-2026-31588, CVE-2026-31590, CVE-2026-31594, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598,     CVE-2026-31599, CVE-2026-31602, CVE-2026-31603, CVE-2026-31605, CVE-2026-31615, CVE-2026-31616,     CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,     CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31630,     CVE-2026-31634, CVE-2026-31642, CVE-2026-31651, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,     CVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31670,     CVE-2026-31671, CVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31676, CVE-2026-31679,     CVE-2026-31680, CVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31687,     CVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699,     CVE-2026-31701, CVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31726, CVE-2026-31728,     CVE-2026-31737, CVE-2026-31738, CVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,     CVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,     CVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31770, CVE-2026-31773, CVE-2026-31778,     CVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43014, CVE-2026-43015, CVE-2026-43020,     CVE-2026-43024, CVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,     CVE-2026-43035, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43046, CVE-2026-43047,     CVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43058, CVE-2026-43060,     CVE-2026-43061, CVE-2026-43062, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,     CVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43085,     CVE-2026-43089, CVE-2026-43093, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,     CVE-2026-43105, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43123,     CVE-2026-43124, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134, CVE-2026-43135,     CVE-2026-43136, CVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43145, CVE-2026-43147,     CVE-2026-43148, CVE-2026-43149, CVE-2026-43152, CVE-2026-43156, CVE-2026-43158, CVE-2026-43159,     CVE-2026-43163, CVE-2026-43168, CVE-2026-43171, CVE-2026-43180, CVE-2026-43182, CVE-2026-43183,     CVE-2026-43184, CVE-2026-43187, CVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43200,     CVE-2026-43202, CVE-2026-43203, CVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,     CVE-2026-43211, CVE-2026-43218, CVE-2026-43223, CVE-2026-43225, CVE-2026-43226, CVE-2026-43227,     CVE-2026-43230, CVE-2026-43231, CVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43241,     CVE-2026-43242, CVE-2026-43246, CVE-2026-43251, CVE-2026-43255, CVE-2026-43257, CVE-2026-43261,     CVE-2026-43262, CVE-2026-43264, CVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,     CVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,     CVE-2026-43287, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295, CVE-2026-43296, CVE-2026-43302,     CVE-2026-43312, CVE-2026-43313, CVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43324,     CVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,     CVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343, CVE-2026-43357, CVE-2026-43363,     CVE-2026-43365, CVE-2026-43370, CVE-2026-43373, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,     CVE-2026-43386, CVE-2026-43387, CVE-2026-43405, CVE-2026-43411, CVE-2026-43420, CVE-2026-43425,     CVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429, CVE-2026-43430, CVE-2026-43432,     CVE-2026-43439, CVE-2026-43445, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,     CVE-2026-43453, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43469, CVE-2026-43472,     CVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480, CVE-2026-43484, CVE-2026-43496,     CVE-2026-43497, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,     CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,     CVE-2026-45846, CVE-2026-45847, CVE-2026-45848, CVE-2026-45852, CVE-2026-45856, CVE-2026-45857,     CVE-2026-45860, CVE-2026-45862, CVE-2026-45864, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,     CVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45873, CVE-2026-45875, CVE-2026-45879,     CVE-2026-45883, CVE-2026-45885, CVE-2026-45890, CVE-2026-45891, CVE-2026-45899, CVE-2026-45902,     CVE-2026-45904, CVE-2026-45911, CVE-2026-45912, CVE-2026-45915, CVE-2026-45916, CVE-2026-45919,     CVE-2026-45920, CVE-2026-45924, CVE-2026-45935, CVE-2026-45936, CVE-2026-45941, CVE-2026-45946,     CVE-2026-45948, CVE-2026-45954, CVE-2026-45956, CVE-2026-45958, CVE-2026-45960, CVE-2026-45964,     CVE-2026-45965, CVE-2026-45968, CVE-2026-45969, CVE-2026-45970, CVE-2026-45974, CVE-2026-45978,     CVE-2026-45983, CVE-2026-45984, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987, CVE-2026-45994,     CVE-2026-46002, CVE-2026-46004, CVE-2026-46006, CVE-2026-46009, CVE-2026-46015, CVE-2026-46018,     CVE-2026-46019, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46027, CVE-2026-46033,     CVE-2026-46037, CVE-2026-46040, CVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,     CVE-2026-46050, CVE-2026-46051, CVE-2026-46053, CVE-2026-46062, CVE-2026-46064, CVE-2026-46070,     CVE-2026-46072, CVE-2026-46077, CVE-2026-46080, CVE-2026-46082, CVE-2026-46088, CVE-2026-46098,     CVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46107, CVE-2026-46108, CVE-2026-46112,     CVE-2026-46120, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46127, CVE-2026-46128,     CVE-2026-46132, CVE-2026-46133, CVE-2026-46137, CVE-2026-46146, CVE-2026-46149, CVE-2026-46150,     CVE-2026-46151, CVE-2026-46161, CVE-2026-46163, CVE-2026-46167, CVE-2026-46168, CVE-2026-46172,     CVE-2026-46174, CVE-2026-46177, CVE-2026-46178, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,     CVE-2026-46189, CVE-2026-46197, CVE-2026-46198, CVE-2026-46205, CVE-2026-46206, CVE-2026-46209,     CVE-2026-46212, CVE-2026-46214, CVE-2026-46219, CVE-2026-46220, CVE-2026-46227, CVE-2026-46230,     CVE-2026-46231, CVE-2026-46233, CVE-2026-46234, CVE-2026-46236, CVE-2026-46238, CVE-2026-46249,     CVE-2026-46250, CVE-2026-46253, CVE-2026-46259, CVE-2026-46267, CVE-2026-46270, CVE-2026-46273,     CVE-2026-46274, CVE-2026-46275, CVE-2026-46285, CVE-2026-46294, CVE-2026-46301, CVE-2026-46303,     CVE-2026-46304, CVE-2026-46307, CVE-2026-46319, CVE-2026-46328, CVE-2026-52911, CVE-2026-52912,     CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921,     CVE-2026-52922, CVE-2026-52925, CVE-2026-52926, CVE-2026-52931, CVE-2026-52954, CVE-2026-52955,     CVE-2026-52957, CVE-2026-52958, CVE-2026-52962, CVE-2026-52963, CVE-2026-52969, CVE-2026-52970,     CVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52992, CVE-2026-52993,     CVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003,     CVE-2026-53004, CVE-2026-53006, CVE-2026-53011, CVE-2026-53012, CVE-2026-53016, CVE-2026-53021,     CVE-2026-53022, CVE-2026-53023, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041,     CVE-2026-53043, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,     CVE-2026-53050, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53064,     CVE-2026-53065, CVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,     CVE-2026-53074, CVE-2026-53075, CVE-2026-53077, CVE-2026-53082, CVE-2026-53088, CVE-2026-53093,     CVE-2026-53096, CVE-2026-53112, CVE-2026-53128, CVE-2026-53130, CVE-2026-53287, CVE-2026-53291,     CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53304, CVE-2026-53306, CVE-2026-53309,     CVE-2026-53320, CVE-2026-53369, CVE-2026-53379, CVE-2026-63860, CVE-2026-63865, CVE-2026-64018,     CVE-2026-64032, CVE-2026-64033, CVE-2026-64034, CVE-2026-64039, CVE-2026-64046, CVE-2026-64047,     CVE-2026-64055, CVE-2026-64056, CVE-2026-64083, CVE-2026-64084, CVE-2026-64085, CVE-2026-64086,     CVE-2026-64087, CVE-2026-64088, CVE-2026-64089, CVE-2026-64096, CVE-2026-64102, CVE-2026-64103,     CVE-2026-64113, CVE-2026-64114, CVE-2026-64115, CVE-2026-64125, CVE-2026-64133, CVE-2026-64135,     CVE-2026-64153, CVE-2026-64155, CVE-2026-64164, CVE-2026-64165, CVE-2026-64166, CVE-2026-64168,     CVE-2026-64173, CVE-2026-64174, CVE-2026-64177, CVE-2026-64178, CVE-2026-64179, CVE-2026-64185,     CVE-2026-64218, CVE-2026-64219, CVE-2026-64220, CVE-2026-64221, CVE-2026-64587)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

According to the versions of the kernel packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace(CVE-2022-49932)

    drivers:md:fix a potential use-after-free bug(CVE-2022-50022)

    ceph: don't leak snap_rwsem in handle_cap_grant(CVE-2022-50059)

    posix-cpu-timers: Cleanup CPU timers before freeing them during exec(CVE-2022-50095)

    scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts(CVE-2022-50098)

    sched/core: Do not requeue task on CPU excluded from cpus_mask(CVE-2022-50100)

    sched, cpuset: Fix dl_cpu_busy() panic due to empty cs-cpus_allowed(CVE-2022-50103)

    An issue was discovered in drivers/tty/n_gsm.c in the Linux kernel 6.2. There is a sleeping function     called from an invalid context in gsmld_write, which will block the kernel. Note: This has been disputed     by 3rd parties as not a valid vulnerability.(CVE-2023-31082)

    scsi: qla2xxx: Perform lockless command completion in abort path(CVE-2023-53041)

    drm/nouveau: prime: fix ttm_bo_delayed_delete oops(CVE-2025-37765)

    dmaengine: idxd: fix memory leak in error handling path of idxd_alloc(CVE-2025-38015)

    padata: do not leak refcount in reorder_work(CVE-2025-38031)

    nvmet-tcp: don't restore null sk_state_change(CVE-2025-38035)

    rseq: Fix segfault on registration when rseq_cs is non-zero(CVE-2025-38067)

    libnvdimm/labels: Fix divide error in nd_label_data_init()(CVE-2025-38072)

    HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()(CVE-2025-38103)

    net: openvswitch: Fix the dead loop of MPLS parse(CVE-2025-38146)

    calipso: Don't call calipso functions for AF_INET sk.(CVE-2025-38147)

    tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer(CVE-2025-38184)

    net: clear the dst when changing skb protocol(CVE-2025-38192)

    ipc: fix to protect IPCS lookups using RCU(CVE-2025-38212)

    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38215)

    sched/rt: Fix race in push_rt_task(CVE-2025-38234)

    nvme-tcp: sanitize request list handling(CVE-2025-38264)

    net: tipc: fix refcount warning in tipc_aead_encrypt(CVE-2025-38273)

    fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod()(CVE-2025-38312)

    arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth()(CVE-2025-38320)

    virtio-net: ensure the received length does not exceed allocated size(CVE-2025-38375)

    NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN(CVE-2025-38393)

    perf: Fix sample vs do_exit()(CVE-2025-38424)

    net/sched: Abort __tc_modify_qdisc if parent class does not exist(CVE-2025-38457)

    tipc: Fix use-after-free in tipc_conn_close().(CVE-2025-38464)

    netlink: Fix wraparounds of sk-sk_rmem_alloc.(CVE-2025-38465)

    perf: Revert to requiring CAP_SYS_ADMIN for uprobes(CVE-2025-38466)

    do_change_type(): refuse to operate on unmounted/not ours mounts(CVE-2025-38498)

    tracing: Add down_write(trace_event_sem) when adding trace event(CVE-2025-38539)

    perf/core: Prevent VMA split of buffer mappings(CVE-2025-38563)

    perf/core: Exit early on perf_mmap() fail(CVE-2025-38565)

    pptp: ensure minimal skb length in pptp_xmit()(CVE-2025-38574)

    pinmux: fix race causing mux_owner NULL with active mux_usecount(CVE-2025-38632)

    i2c: qup: jump out of the loop in case of timeout(CVE-2025-38671)

    ipv6: fix panic when forwarding a pkt with no in6 dev(CVE-2022-49048)

    netfilter: conntrack: revisit gc autotuning(CVE-2022-49110)

    bpf, sockmap: Fix memleak in sk_psock_queue_msg(CVE-2022-49207)

    block: fix rq-qos breakage from skipping rq_qos_done_bio()(CVE-2022-49266)

    tcp: add accessors to read/set tp-snd_cwnd(CVE-2022-49325)

    ip_gre: test csum_start instead of transport header(CVE-2022-49340)

    netfilter: nf_tables: double hook unregistration in netns path(CVE-2022-49558)

    tcp: Fix data-races around sysctl_tcp_recovery.(CVE-2022-49574)

    igmp: Fix data-races around sysctl_igmp_llm_reports.(CVE-2022-49590)

    tcp: Fix a data-race around sysctl_tcp_probe_interval.(CVE-2022-49593)

    ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open()(CVE-2022-49772)

    macvlan: enforce a consistent minimal mtu(CVE-2022-49776)

    x86/sgx: Add overflow check in sgx_validate_offset_length()(CVE-2022-49785)

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()(CVE-2022-49787)

    tracing: Fix memory leak in tracing_read_pipe()(CVE-2022-49801)

    netdevsim: Fix memory leak of nsim_dev-fa_cookie(CVE-2022-49803)

    bridge: switchdev: Fix memory leaks when changing VLAN protocol(CVE-2022-49812)

    net: ena: Fix error handling in ena_init()(CVE-2022-49813)

    sctp: clear out_curr if all frag chunks of current msg are pruned(CVE-2022-49838)

    ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network(CVE-2022-49865)

    net: gso: fix panic on frag_list with mixed head alloc types(CVE-2022-49872)

    bpf, sockmap: Fix the sk-sk_forward_alloc warning of sk_stream_kill_queues(CVE-2022-49877)

    ipv6: fix WARNING in ip6_route_net_exit_late()(CVE-2022-49903)

    net, neigh: Fix null-ptr-deref in neigh_table_clear()(CVE-2022-49904)

    net: mdio: fix undefined behavior in bit shift for __mdiobus_register(CVE-2022-49907)

    ipvs: fix WARNING in ip_vs_app_net_cleanup()(CVE-2022-49917)

    ipvs: fix WARNING in __ip_vs_cleanup_batch()(CVE-2022-49918)

    netfilter: nf_tables: release flow rule object from commit path(CVE-2022-49919)

    tty: n_gsm: add sanity check for gsm-receive in gsm_receive_buf()(CVE-2022-49940)

    vt: Clear selection before changing the font(CVE-2022-49948)

    bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO(CVE-2022-49961)

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level(CVE-2022-49964)

    bpf: Fix a data-race around bpf_jit_limit.(CVE-2022-49967)

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead(CVE-2022-49977)

    net: fix refcount bug in sk_psock_get (2)(CVE-2022-49979)

    media: pvrusb2: fix memory leak in pvr_probe(CVE-2022-49982)

    bpf: Don't use tnum_range on array range checking for poke descriptors(CVE-2022-49985)

    ice: xsk: prohibit usage of non-balanced queue id(CVE-2022-50003)

    kprobes: don't call disarm_kprobe() for disabled kprobes(CVE-2022-50008)

    ext4: avoid resizing to a partial cluster size(CVE-2022-50020)

    x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave).(CVE-2022-49557)

    A cross-privilege Spectre v2 vulnerability allows attackers to bypass all deployed mitigations, including     the recent Fine(IBT), and to leak arbitrary Linux kernel memory on Intel systems.(CVE-2024-2201)

    perf/x86/amd/uncore: Fix memory leak for events array(CVE-2022-49784)

    perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling(CVE-2022-49781)

    perf/x86/amd/core: Always clear status for idx(CVE-2023-53073)

    drm/drv: Fix potential memory leak in drm_dev_init().(CVE-2022-49830)

    drm/shmem-helper: Remove another errant put in error path(CVE-2023-53084)

    perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output(CVE-2023-53065)

    arm64: bpf: Only mitigate cBPF programs loaded by unprivileged users(CVE-2025-37963)

    arm64: bpf: Add BHB mitigation to the epilogue for cBPF programs(CVE-2025-37948)

    crypto: null - Use spin lock instead of mutex(CVE-2025-37808)

    tracing: Fix oob write in trace_seq_to_buffer().(CVE-2025-37923)

    media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer().(CVE-2023-53146)

    usb: ucsi: Fix NULL pointer deref in ucsi_connector_change().(CVE-2023-53049)

    iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid(CVE-2025-37927)

    drm     ouveau: Fix WARN_ON in nouveau_fence_context_kill().(CVE-2025-37930)

    module: ensure that kobject_put() is safe for module type kobjects(CVE-2025-37995)

    bnxt_en: Fix out-of-bound memcpy() during ethtool -w(CVE-2025-37911)

    capabilities: fix undefined behavior in bit shift for CAP_TO_MASK(CVE-2022-49870)

    HID: intel-ish-hid: ipc: Fix potential use-after-free in work function(CVE-2023-53039)

    IB/hfi1: Correctly move list in sc_disable().(CVE-2022-49931)

    tpm: do not start chip while suspended(CVE-2025-23149)

    bpf: check changes_pkt_data property for extension programs(CVE-2024-58100)

    ext4: block range must be validated before use in ext4_mb_clear_bb()(CVE-2022-50021)

    iavf: Fix adminq error handling(CVE-2022-50055)

    virtio_net: fix memory leak inside XPD_TX with mergeable(CVE-2022-50065)

    net: atlantic: fix aq_vec index out of range error(CVE-2022-50066)

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()(CVE-2022-50069)

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-dev is null(CVE-2022-50073)

    apparmor: Fix memleak in aa_simple_write_to_buffer()(CVE-2022-50074)

    resolved: apparmor: fix reference count leak in aa_pivotroot() (CVE-2022-50077)

    ext4: fix warning in ext4_iomap_begin as race between bmap and write(CVE-2022-50082)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50083)

    block: don't allow the same type rq_qos add more than once(CVE-2022-50086)

    jbd2: fix assertion 'jh-b_frozen_data == NULL' failure when journal aborted(CVE-2022-50126)

    RDMA/srpt: Fix a use-after-free(CVE-2022-50129)

    RDMA/hfi1: fix potential memory leak in setup_base_ctxt()(CVE-2022-50134)

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr()(CVE-2022-50138)

    bpf: fix potential 32-bit overflow when accessing ARRAY map element(CVE-2022-50167)

    virtio-gpu: fix a missing check to avoid NULL dereference(CVE-2022-50181)

    selinux: Add boundary check in put_entry()(CVE-2022-50200)

    PM: hibernate: defer device probing when resuming from hibernation(CVE-2022-50202)

    arm64: fix oops in concurrently setting insn_emulation sysctls(CVE-2022-50206)

    netfilter: nf_tables: do not allow SET_ID to refer to another table(CVE-2022-50213)

    scsi: sg: Allow waiting for commands to complete on removed device(CVE-2022-50215)

    bpf: Fix KASAN use-after-free Read in compute_effective_progs(CVE-2022-50219)

    usbnet: Fix linkwatch use-after-free on disconnect(CVE-2022-50220)

    tty: vt: initialize unicode screen buffer(CVE-2022-50222)

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0(CVE-2022-50228)

    arm64: set UXN on swapper page tables(CVE-2022-50230)

    crypto: arm64/poly1305 - fix a read out-of-bound(CVE-2022-50231)

    arm64: set UXN on swapper page tables(CVE-2022-50232)

    netfilter: nf_tables: don't fail inserts if duplicate has expired(CVE-2023-52925)

    netfilter: allow exp not to be removed in nf_ct_find_expectation(CVE-2023-52927)

    dm crypt: add cond_resched() to dmcrypt_write()(CVE-2023-53051)

    erspan: do not use skb_mac_header() in ndo_start_xmit()(CVE-2023-53053)

    net/mlx5: E-Switch, Fix an Oops in error handling code(CVE-2023-53058)

    net: usb: smsc95xx: Limit packet length to skb-len(CVE-2023-53062)

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info(CVE-2023-53066)

    net: usb: lan78xx: Limit packet length to skb-len(CVE-2023-53068)

    net/mlx5: Fix steering rules cleanup(CVE-2023-53079)

    xsk: Add missing overflow check in xdp_umem_reg(CVE-2023-53080)

    ice: xsk: disable txq irq before flushing hw(CVE-2023-53102)

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails(CVE-2023-53103)

    net: tunnels: annotate lockless accesses to dev-needed_headroom(CVE-2023-53109)

    i40e: Fix kernel crash during reboot when adapter is in recovery mode(CVE-2023-53114)

    tcp: tcp_make_synack() can be called from process context(CVE-2023-53121)

    net: usb: smsc75xx: Limit packet length to skb-len(CVE-2023-53125)

    SUNRPC: Fix a server shutdown leak(CVE-2023-53131)

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()(CVE-2023-53133)

    bpf: consider that tail calls invalidate packet pointers(CVE-2024-58237)

    net: avoid race between device unregistration and ethnl ops(CVE-2025-21701)

    ata: libata-sff: Ensure that we cannot write outside the allocated buffer(CVE-2025-21738)

    block: mark GFP_NOIO around sysfs -store()(CVE-2025-21817)

    netfilter: nf_tables: reject mismatching sum of field_len with set key length(CVE-2025-21826)

    netfilter: socket: Lookup orig tuple for IPv6 SNAT(CVE-2025-22021)

    net: fix geneve_opt length integer overflow(CVE-2025-22055)

    net: decrease cached dst counters in dst_release(CVE-2025-22057)

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported(CVE-2025-22075)

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow(CVE-2025-22086)

    net: fix NULL pointer dereference in l3mdev_l3_rcv(CVE-2025-22103)

    sctp: detect and prevent references to a freed transport in sendmsg(CVE-2025-23142)

    net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer     from skb before accessing initial bytes.(CVE-2025-37749)

    net: tls: explicitly disallow disconnect(CVE-2025-37756)

    tipc: fix memory leak in tipc_link_xmit(CVE-2025-37757)

    cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path(CVE-2025-37788)

    net: openvswitch: fix nested key length validation in the set() action(CVE-2025-37789)

    net_sched: hfsc: Fix a UAF vulnerability in class handling(CVE-2025-37797)

    codel: remove sch-q.qlen check before qdisc_tree_reduce_backlog()(CVE-2025-37798)

    net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too(CVE-2025-37823)

    tipc: fix NULL pointer dereference in tipc_mon_reinit_self()(CVE-2025-37824)

    page_pool: avoid infinite loop to schedule delayed worker(CVE-2025-37859)

    HID: pidff: Fix null pointer dereference in pidff_find_fields(CVE-2025-37862)

    net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc(CVE-2025-37890)

    net_sched: qfq: Fix double list add in class with netem as child qdisc(CVE-2025-37913)

    net_sched: drr: Fix double list add in class with netem as child qdisc(CVE-2025-37915)

    xsk: Fix race condition in AF_XDP generic RX path(CVE-2025-37920)

    sch_htb: make htb_qlen_notify() idempotent(CVE-2025-37932)

    bpf: Scrub packet on bpf_redirect_peer(CVE-2025-37959)

    ipvs: fix uninit-value for saddr in do_output_route4(CVE-2025-37961)

    net: phy: leds: fix memory leak(CVE-2025-37989)

    net_sched: Flush gso_skb list too during -change()(CVE-2025-37992)

    netfilter: ipset: fix region locking in hash types(CVE-2025-37997)

    openvswitch: Fix unsafe attribute parsing in output_userspace()(CVE-2025-37998)

    sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()(CVE-2025-38000)

    net_sched: hfsc: Address reentrant enqueue adding class to eltree twice(CVE-2025-38001)

    dmaengine: idxd: Refactor remove call with idxd_cleanup() helper(CVE-2025-38014)

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs(CVE-2025-38040)

    media: cx231xx: set device_caps for 417(CVE-2025-38044)

    net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done(CVE-2025-38052)

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write()(CVE-2025-38061)

    dm: fix unconditional IO throttle caused by REQ_PREFLUSH(CVE-2025-38063)

    dm cache: prevent BUG_ON by blocking retries on failed device resumes(CVE-2025-38066)

    crypto: lzo - Fix compression buffer overrun(CVE-2025-38068)

    vhost-scsi: protect vq-log_used with vq-mutex(CVE-2025-38074)

    scsi: target: iscsi: Fix timeout on deleted connection(CVE-2025-38075)

    net_sched: prio: fix a race in prio_tune()(CVE-2025-38083)

    mm/hugetlb: unshare page tables during VMA split, not before(CVE-2025-38084)

    net: ch9200: fix uninitialised access during mii_nway_restart(CVE-2025-38086)

    x86/iopl: Cure TIF_IO_BITMAP inconsistencies(CVE-2025-38100)

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify(CVE-2025-38102)

    net_sched: red: fix a race in __red_change()(CVE-2025-38108)

    net/mdiobus: Fix potential out-of-bounds read/write access(CVE-2025-38111)

    net: Fix TOCTOU issue in sk_is_readable()(CVE-2025-38112)

    net_sched: sch_sfq: fix a potential crash on gso_skb handling(CVE-2025-38115)

    netfilter: nf_set_pipapo_avx2: fix initial map fill(CVE-2025-38120)

    net: fix udp gso skb_segment after pull from frag_list(CVE-2025-38124)

    ice: fix Tx scheduler error handling in XDP callback(CVE-2025-38127)

    page_pool: Fix use-after-free in page_pool_recycle_in_ring(CVE-2025-38129)

    bpf, sockmap: Avoid using sk_socket after free when sending(CVE-2025-38154)

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation(CVE-2025-38162)

    bpf, sockmap: Fix panic when calling skb_linearize(CVE-2025-38165)

    bpf: fix ktls panic with sockmap(CVE-2025-38166)

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction(CVE-2025-38211)

    fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38214)

    ext4: inline: fix len overflow in ext4_prepare_inline_data(CVE-2025-38222)

    media: cxusb: no longer judge rbuf when the write fails(CVE-2025-38229)

    bpf: Avoid __bpf_prog_ret0_warn when jit fails(CVE-2025-38280)

    bpf: Fix WARN() in get_bpf_raw_tp_regs(CVE-2025-38285)

    EDAC/skx_common: Fix general protection fault(CVE-2025-38298)

    mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().(CVE-2025-38324)

    jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()(CVE-2025-38337)

    ACPICA: fix acpi operand cache leak in dswstate.c(CVE-2025-38345)

    ftrace: Fix UAF when lookup kallsym after ftrace disabled(CVE-2025-38346)

    posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()(CVE-2025-38352)

    ACPICA: Refuse to evaluate a method if arguments are missing(CVE-2025-38386)

    usb: typec: altmodes/displayport: do not index invalid pin_assignments(CVE-2025-38391)

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass(CVE-2025-38396)

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()(CVE-2025-38399)

    drm/gem: Acquire references on GEM handles for framebuffers(CVE-2025-38449)

    HID: core: ensure the allocated report buffer can contain the reserved report ID(CVE-2025-38495)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization kernel security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update of the linux package has been released.

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    ipv6: fix panic when forwarding a pkt with no in6 dev(CVE-2022-49048)

    netfilter: conntrack: revisit gc autotuning(CVE-2022-49110)

    bpf, sockmap: Fix memleak in sk_psock_queue_msg(CVE-2022-49207)

    block: fix rq-qos breakage from skipping rq_qos_done_bio()(CVE-2022-49266)

    tcp: add accessors to read/set tp-snd_cwnd(CVE-2022-49325)

    ip_gre: test csum_start instead of transport header(CVE-2022-49340)

    netfilter: nf_tables: double hook unregistration in netns path(CVE-2022-49558)

    tcp: Fix data-races around sysctl_tcp_recovery.(CVE-2022-49574)

    igmp: Fix data-races around sysctl_igmp_llm_reports.(CVE-2022-49590)

    tcp: Fix a data-race around sysctl_tcp_probe_interval.(CVE-2022-49593)

    ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open()(CVE-2022-49772)

    macvlan: enforce a consistent minimal mtu(CVE-2022-49776)

    x86/sgx: Add overflow check in sgx_validate_offset_length()(CVE-2022-49785)

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()(CVE-2022-49787)

    tracing: Fix memory leak in tracing_read_pipe()(CVE-2022-49801)

    netdevsim: Fix memory leak of nsim_dev-fa_cookie(CVE-2022-49803)

    bridge: switchdev: Fix memory leaks when changing VLAN protocol(CVE-2022-49812)

    net: ena: Fix error handling in ena_init()(CVE-2022-49813)

    sctp: clear out_curr if all frag chunks of current msg are pruned(CVE-2022-49838)

    ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network(CVE-2022-49865)

    net: gso: fix panic on frag_list with mixed head alloc types(CVE-2022-49872)

    bpf, sockmap: Fix the sk-sk_forward_alloc warning of sk_stream_kill_queues(CVE-2022-49877)

    ipv6: fix WARNING in ip6_route_net_exit_late()(CVE-2022-49903)

    net, neigh: Fix null-ptr-deref in neigh_table_clear()(CVE-2022-49904)

    net: mdio: fix undefined behavior in bit shift for __mdiobus_register(CVE-2022-49907)

    ipvs: fix WARNING in ip_vs_app_net_cleanup()(CVE-2022-49917)

    ipvs: fix WARNING in __ip_vs_cleanup_batch()(CVE-2022-49918)

    netfilter: nf_tables: release flow rule object from commit path(CVE-2022-49919)

    tty: n_gsm: add sanity check for gsm-receive in gsm_receive_buf()(CVE-2022-49940)

    vt: Clear selection before changing the font(CVE-2022-49948)

    bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO(CVE-2022-49961)

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level(CVE-2022-49964)

    bpf: Fix a data-race around bpf_jit_limit.(CVE-2022-49967)

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead(CVE-2022-49977)

    net: fix refcount bug in sk_psock_get (2)(CVE-2022-49979)

    media: pvrusb2: fix memory leak in pvr_probe(CVE-2022-49982)

    bpf: Don't use tnum_range on array range checking for poke descriptors(CVE-2022-49985)

    ice: xsk: prohibit usage of non-balanced queue id(CVE-2022-50003)

    kprobes: don't call disarm_kprobe() for disabled kprobes(CVE-2022-50008)

    ext4: avoid resizing to a partial cluster size(CVE-2022-50020)

    ext4: block range must be validated before use in ext4_mb_clear_bb()(CVE-2022-50021)

    iavf: Fix adminq error handling(CVE-2022-50055)

    virtio_net: fix memory leak inside XPD_TX with mergeable(CVE-2022-50065)

    net: atlantic: fix aq_vec index out of range error(CVE-2022-50066)

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()(CVE-2022-50069)

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-dev is null(CVE-2022-50073)

    apparmor: Fix memleak in aa_simple_write_to_buffer()(CVE-2022-50074)

    resolved: apparmor: fix reference count leak in aa_pivotroot() (CVE-2022-50077)

    ext4: fix warning in ext4_iomap_begin as race between bmap and write(CVE-2022-50082)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50083)

    block: don't allow the same type rq_qos add more than once(CVE-2022-50086)

    jbd2: fix assertion 'jh-b_frozen_data == NULL' failure when journal aborted(CVE-2022-50126)

    RDMA/srpt: Fix a use-after-free(CVE-2022-50129)

    RDMA/hfi1: fix potential memory leak in setup_base_ctxt()(CVE-2022-50134)

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr()(CVE-2022-50138)

    bpf: fix potential 32-bit overflow when accessing ARRAY map element(CVE-2022-50167)

    virtio-gpu: fix a missing check to avoid NULL dereference(CVE-2022-50181)

    selinux: Add boundary check in put_entry()(CVE-2022-50200)

    PM: hibernate: defer device probing when resuming from hibernation(CVE-2022-50202)

    arm64: fix oops in concurrently setting insn_emulation sysctls(CVE-2022-50206)

    netfilter: nf_tables: do not allow SET_ID to refer to another table(CVE-2022-50213)

    scsi: sg: Allow waiting for commands to complete on removed device(CVE-2022-50215)

    bpf: Fix KASAN use-after-free Read in compute_effective_progs(CVE-2022-50219)

    usbnet: Fix linkwatch use-after-free on disconnect(CVE-2022-50220)

    tty: vt: initialize unicode screen buffer(CVE-2022-50222)

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0(CVE-2022-50228)

    arm64: set UXN on swapper page tables(CVE-2022-50230)

    crypto: arm64/poly1305 - fix a read out-of-bound(CVE-2022-50231)

    arm64: set UXN on swapper page tables(CVE-2022-50232)

    netfilter: nf_tables: don't fail inserts if duplicate has expired(CVE-2023-52925)

    netfilter: allow exp not to be removed in nf_ct_find_expectation(CVE-2023-52927)

    dm crypt: add cond_resched() to dmcrypt_write()(CVE-2023-53051)

    erspan: do not use skb_mac_header() in ndo_start_xmit()(CVE-2023-53053)

    net/mlx5: E-Switch, Fix an Oops in error handling code(CVE-2023-53058)

    net: usb: smsc95xx: Limit packet length to skb-len(CVE-2023-53062)

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info(CVE-2023-53066)

    net: usb: lan78xx: Limit packet length to skb-len(CVE-2023-53068)

    net/mlx5: Fix steering rules cleanup(CVE-2023-53079)

    xsk: Add missing overflow check in xdp_umem_reg(CVE-2023-53080)

    ice: xsk: disable txq irq before flushing hw(CVE-2023-53102)

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails(CVE-2023-53103)

    net: tunnels: annotate lockless accesses to dev-needed_headroom(CVE-2023-53109)

    i40e: Fix kernel crash during reboot when adapter is in recovery mode(CVE-2023-53114)

    tcp: tcp_make_synack() can be called from process context(CVE-2023-53121)

    net: usb: smsc75xx: Limit packet length to skb-len(CVE-2023-53125)

    SUNRPC: Fix a server shutdown leak(CVE-2023-53131)

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()(CVE-2023-53133)

    bpf: consider that tail calls invalidate packet pointers(CVE-2024-58237)

    net: avoid race between device unregistration and ethnl ops(CVE-2025-21701)

    ata: libata-sff: Ensure that we cannot write outside the allocated buffer(CVE-2025-21738)

    block: mark GFP_NOIO around sysfs -store()(CVE-2025-21817)

    netfilter: nf_tables: reject mismatching sum of field_len with set key length(CVE-2025-21826)

    netfilter: socket: Lookup orig tuple for IPv6 SNAT(CVE-2025-22021)

    net: fix geneve_opt length integer overflow(CVE-2025-22055)

    net: decrease cached dst counters in dst_release(CVE-2025-22057)

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported(CVE-2025-22075)

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow(CVE-2025-22086)

    net: fix NULL pointer dereference in l3mdev_l3_rcv(CVE-2025-22103)

    sctp: detect and prevent references to a freed transport in sendmsg(CVE-2025-23142)

    net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer     from skb before accessing initial bytes.(CVE-2025-37749)

    net: tls: explicitly disallow disconnect(CVE-2025-37756)

    tipc: fix memory leak in tipc_link_xmit(CVE-2025-37757)

    cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path(CVE-2025-37788)

    net: openvswitch: fix nested key length validation in the set() action(CVE-2025-37789)

    net_sched: hfsc: Fix a UAF vulnerability in class handling(CVE-2025-37797)

    codel: remove sch-q.qlen check before qdisc_tree_reduce_backlog()(CVE-2025-37798)

    net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too(CVE-2025-37823)

    tipc: fix NULL pointer dereference in tipc_mon_reinit_self()(CVE-2025-37824)

    page_pool: avoid infinite loop to schedule delayed worker(CVE-2025-37859)

    HID: pidff: Fix null pointer dereference in pidff_find_fields(CVE-2025-37862)

    net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc(CVE-2025-37890)

    net_sched: qfq: Fix double list add in class with netem as child qdisc(CVE-2025-37913)

    net_sched: drr: Fix double list add in class with netem as child qdisc(CVE-2025-37915)

    xsk: Fix race condition in AF_XDP generic RX path(CVE-2025-37920)

    sch_htb: make htb_qlen_notify() idempotent(CVE-2025-37932)

    bpf: Scrub packet on bpf_redirect_peer(CVE-2025-37959)

    ipvs: fix uninit-value for saddr in do_output_route4(CVE-2025-37961)

    net: phy: leds: fix memory leak(CVE-2025-37989)

    net_sched: Flush gso_skb list too during -change()(CVE-2025-37992)

    netfilter: ipset: fix region locking in hash types(CVE-2025-37997)

    openvswitch: Fix unsafe attribute parsing in output_userspace()(CVE-2025-37998)

    sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()(CVE-2025-38000)

    net_sched: hfsc: Address reentrant enqueue adding class to eltree twice(CVE-2025-38001)

    dmaengine: idxd: Refactor remove call with idxd_cleanup() helper(CVE-2025-38014)

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs(CVE-2025-38040)

    media: cx231xx: set device_caps for 417(CVE-2025-38044)

    net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done(CVE-2025-38052)

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write()(CVE-2025-38061)

    dm: fix unconditional IO throttle caused by REQ_PREFLUSH(CVE-2025-38063)

    dm cache: prevent BUG_ON by blocking retries on failed device resumes(CVE-2025-38066)

    crypto: lzo - Fix compression buffer overrun(CVE-2025-38068)

    vhost-scsi: protect vq-log_used with vq-mutex(CVE-2025-38074)

    scsi: target: iscsi: Fix timeout on deleted connection(CVE-2025-38075)

    net_sched: prio: fix a race in prio_tune()(CVE-2025-38083)

    mm/hugetlb: unshare page tables during VMA split, not before(CVE-2025-38084)

    net: ch9200: fix uninitialised access during mii_nway_restart(CVE-2025-38086)

    x86/iopl: Cure TIF_IO_BITMAP inconsistencies(CVE-2025-38100)

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify(CVE-2025-38102)

    net_sched: red: fix a race in __red_change()(CVE-2025-38108)

    net/mdiobus: Fix potential out-of-bounds read/write access(CVE-2025-38111)

    net: Fix TOCTOU issue in sk_is_readable()(CVE-2025-38112)

    net_sched: sch_sfq: fix a potential crash on gso_skb handling(CVE-2025-38115)

    netfilter: nf_set_pipapo_avx2: fix initial map fill(CVE-2025-38120)

    net: fix udp gso skb_segment after pull from frag_list(CVE-2025-38124)

    ice: fix Tx scheduler error handling in XDP callback(CVE-2025-38127)

    page_pool: Fix use-after-free in page_pool_recycle_in_ring(CVE-2025-38129)

    bpf, sockmap: Avoid using sk_socket after free when sending(CVE-2025-38154)

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation(CVE-2025-38162)

    bpf, sockmap: Fix panic when calling skb_linearize(CVE-2025-38165)

    bpf: fix ktls panic with sockmap(CVE-2025-38166)

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction(CVE-2025-38211)

    fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38214)

    ext4: inline: fix len overflow in ext4_prepare_inline_data(CVE-2025-38222)

    media: cxusb: no longer judge rbuf when the write fails(CVE-2025-38229)

    bpf: Avoid __bpf_prog_ret0_warn when jit fails(CVE-2025-38280)

    bpf: Fix WARN() in get_bpf_raw_tp_regs(CVE-2025-38285)

    EDAC/skx_common: Fix general protection fault(CVE-2025-38298)

    mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().(CVE-2025-38324)

    jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()(CVE-2025-38337)

    ACPICA: fix acpi operand cache leak in dswstate.c(CVE-2025-38345)

    ftrace: Fix UAF when lookup kallsym after ftrace disabled(CVE-2025-38346)

    posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()(CVE-2025-38352)

    ACPICA: Refuse to evaluate a method if arguments are missing(CVE-2025-38386)

    usb: typec: altmodes/displayport: do not index invalid pin_assignments(CVE-2025-38391)

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass(CVE-2025-38396)

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()(CVE-2025-38399)

    drm/gem: Acquire references on GEM handles for framebuffers(CVE-2025-38449)

    HID: core: ensure the allocated report buffer can contain the reserved report ID(CVE-2025-38495)

Tenable has extracted the preceding description block directly from the EulerOS kernel security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for     ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style     argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of     states_equal check when such arguments refine the return value (in this case, set mem_size for     PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier     incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both     registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier     which can do access beyond what should have been the correct mem_size in that explored state. To show a     concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 +     76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32 *)(r1 + 0) = r2 7: r1 = *(u32
    *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -1 0000000000000058 <LBB5_3>: 11: r1 = 0 ll     13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7 <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18:
    w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22: call bpf_ringbuf_submit 00000000000000b8     <LBB5_5>: 23: w0 = 0 24: exit For the first case, the single line execution's exploration will prune the     search at insn 14 for the branch insn 9's second leg as it will be verified first using r2 = -1     (UINT_MAX), while as w1 at insn 9 will always be 0 so at runtime we don't get error for being greater than     UINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe just sees reg->precise as false for both     r2 registers in both states, hence considers them equal for purposes of states_equal. If we propagated     precise markers using the backtracking support, we would use the precise marking to then ensure that old     r2 (UINT_MAX) was within the new r2 (1) and this would never be true, so the verification would rightfully     fail. The end result is that the out of bounds access at instruction 19 would be permitted without this     fix. Note that reg->precise is always set to true when user does not have CAP_BPF (or when subprog count     is greater than 1 (i.e. use of any static or global functions)), hence this is only a problem when     precision marks need to be explicitly propagated (i.e. privileged users with CAP_BPF). A simplified test     case has been included in the next patch to prevent future regressions. (CVE-2022-49961)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2458 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * use-after-free in l2cap_connect and l2cap_le_connect_req in net/bluetooth/l2cap_core.c (CVE-2022-42896)

    * net/ulp: use-after-free in listening ULP sockets (CVE-2023-0461)

    * cpu: AMD CPUs may transiently execute beyond unconditional direct branch (CVE-2021-26341)

    * malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory (CVE-2021-33655)

    * possible race condition in drivers/tty/tty_buffers.c (CVE-2022-1462)

    * KVM: NULL pointer dereference in kvm_mmu_invpcid_gva (CVE-2022-1789)

    * use-after-free in free_pipe_info() could lead to privilege escalation (CVE-2022-1882)

    * KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks (CVE-2022-2196)

    * netfilter: nf_conntrack_irc message handling issue (CVE-2022-2663)

    * race condition in xfrm_probe_algs can lead to OOB read/write (CVE-2022-3028)

    * out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c (CVE-2022-3435)

    * race condition in hugetlb_no_page() in mm/hugetlb.c (CVE-2022-3522)

    * memory leak in ipv6_renew_options() (CVE-2022-3524)

    * data races around icsk->icsk_af_ops in do_ipv6_setsockopt (CVE-2022-3566)

    * data races around sk->sk_prot (CVE-2022-3567)

    * memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c (CVE-2022-3619)

    * denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry (CVE-2022-3623)

    * use-after-free after failed devlink reload in devlink_param_get (CVE-2022-3625)

    * USB-accessible buffer overflow in brcmfmac (CVE-2022-3628)

    * use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c (CVE-2022-3640)

    * Double-free in split_2MB_gtt_entry when function intel_gvt_dma_map_guest_page failed (CVE-2022-3707)

    * mptcp: NULL pointer dereference in subflow traversal at disconnect time (CVE-2022-4128)

    * l2tp: missing lock when clearing sk_user_data can lead to NULL pointer dereference (CVE-2022-4129)

    * igmp: use-after-free in ip_check_mc_rcu when opening and closing inet sockets (CVE-2022-20141)

    * lockdown bypass using IMA (CVE-2022-21505)

    * double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c (CVE-2022-28388)

    * network backend may cause Linux netfront to use freed SKBs (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() race with munmap() on VM_PFNMAP mappings leads to stale TLB entry (CVE-2022-39188)

    * TLB flush operations are mishandled in certain KVM_VCPU_PREEMPTED leading to guest malfunctioning     (CVE-2022-39189)

    * u8 overflow problem in cfg80211_update_notlisted_nontrans() (CVE-2022-41674)

    * use-after-free related to leaf anon_vma double reuse (CVE-2022-42703)

    * use-after-free in bss_ref_get in net/wireless/scan.c (CVE-2022-42720)

    * BSS list corruption in cfg80211_add_nontrans_list in net/wireless/scan.c (CVE-2022-42721)

    * Denial of service in beacon protection for P2P-device (CVE-2022-42722)

    * memory corruption in usbmon driver (CVE-2022-43750)

    * NULL pointer dereference in traffic control subsystem (CVE-2022-47929)

    * NULL pointer dereference in rawv6_push_pending_frames (CVE-2023-0394)

    * use-after-free due to race condition in qdisc_graft() (CVE-2023-0590)

    * use-after-free caused by invalid pointer hostname in fs/cifs/connect.c (CVE-2023-1195)

    * denial of service in tipc_conn_close (CVE-2023-1382)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.2 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
368032	CentOS Linux 8.4 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.4:CLSA-2026:1791858083)	Nessus	CentOS Local Security Checks	Local	high
366854	CentOS Linux 8.5 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2026:1792247642)	Nessus	CentOS Local Security Checks	Local	high
361969	CentOS Linux 8 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS-STREAM8:CLSA-2026:1789141176)	Nessus	CentOS Local Security Checks	Local	high
340682	Ubuntu 20.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8668-1)	Nessus	Ubuntu Local Security Checks	Local	high
279319	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2581)	Nessus	Huawei Local Security Checks	Local	high
279287	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2546)	Nessus	Huawei Local Security Checks	Local	high
276925	Photon OS 4.0: Linux PHSA-2025-4.0-0914	Nessus	PhotonOS Local Security Checks	Local	high
271309	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2264)	Nessus	Huawei Local Security Checks	Local	high
271298	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2296)	Nessus	Huawei Local Security Checks	Local	high
245820	Linux Distros Unpatched Vulnerability : CVE-2022-49961	Nessus	Misc.	Local	high
175477	RHEL 9 : kernel (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49961

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high