In the Linux kernel, the following vulnerability has been resolved: platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() The ACPI buffer memory (out.pointer) returned by wmi_evaluate_method() is not freed after the call, so it leads to memory leak. The method results in ACPI buffer is not used, so just pass NULL to wmi_evaluate_method() which fixes the memory leak.

The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1778756832 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix out-of-bound     read in resp_readcap16() The following warning was observed running syzkaller: [ 3813.830724] sg_write:
    data in/out 65466/242 bytes for SCSI command 0x9e-- guessing data in; [ 3813.830724] program syz-executor     not setting count and/or reply_len properly [ 3813.836956]     ================================================================== [ 3813.839465] BUG: KASAN: stack-out-     of-bounds in sg_copy_buffer+0x157/0x1e0 [ 3813.841773] Read of size 4096 at addr ffff8883cf80f540 by task     syz-executor/1549 [ 3813.846612] Call Trace: [ 3813.846995] dump_stack+0x108/0x15f [ 3813.847524]     print_address_description+0xa5/0x372 [ 3813.848243] kasan_report.cold+0x236/0x2a8 [ 3813.849439]     check_memory_region+0x240/0x270 [ 3813.850094] memcpy+0x30/0x80 [ 3813.850553] sg_copy_buffer+0x157/0x1e0     [ 3813.853032] sg_copy_from_buffer+0x13/0x20 [ 3813.853660] fill_from_dev_buffer+0x135/0x370 [     3813.854329] resp_readcap16+0x1ac/0x280 [ 3813.856917] schedule_resp+0x41f/0x1630 [ 3813.858203]     scsi_debug_queuecommand+0xb32/0x17e0 [ 3813.862699] scsi_dispatch_cmd+0x330/0x950 [ 3813.863329]     scsi_request_fn+0xd8e/0x1710 [ 3813.863946] __blk_run_queue+0x10b/0x230 [ 3813.864544]     blk_execute_rq_nowait+0x1d8/0x400 [ 3813.865220] sg_common_write.isra.0+0xe61/0x2420 [ 3813.871637]     sg_write+0x6c8/0xef0 [ 3813.878853] __vfs_write+0xe4/0x800 [ 3813.883487] vfs_write+0x17b/0x530 [     3813.884008] ksys_write+0x103/0x270 [ 3813.886268] __x64_sys_write+0x77/0xc0 [ 3813.886841]     do_syscall_64+0x106/0x360 [ 3813.887415] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This issue can be     reproduced with the following syzkaller log: r0 = openat(0xffffffffffffff9c,     &(0x7f0000000040)='./file0\x00', 0x26e1, 0x0) r1 = syz_open_procfs(0xffffffffffffffff,     &(0x7f0000000000)='fd/3\x00') open_by_handle_at(r1, &(0x7f00000003c0)=ANY=[@ANYRESHEX], 0x602000) r2 =     syz_open_dev$sg(&(0x7f0000000000), 0x0, 0x40782) write$binfmt_aout(r2, &(0x7f0000000340)=ANY=[@ANYBLOB=00     000000deff000000000000000000000000000000000000000000000000000047f007af9e107a41ec395f1bded7be24277a1501ff61     96a83366f4e6362bc0ff2b247f68a972989b094b2da4fb3607fcf611a22dd04310d28c75039d], 0x126) In resp_readcap16()     we get int alloc_len value -1104926854, and then pass the huge arr_len to fill_from_dev_buffer(), but     arr is only 32 bytes. This leads to OOB in sg_copy_buffer(). To solve this issue, define alloc_len as u32.
    (CVE-2021-47191)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix out-of-bound     read in resp_report_tgtpgs() The following issue was observed running syzkaller: BUG: KASAN: slab-out-of-     bounds in memcpy include/linux/string.h:377 [inline] BUG: KASAN: slab-out-of-bounds in     sg_copy_buffer+0x150/0x1c0 lib/scatterlist.c:831 Read of size 2132 at addr ffff8880aea95dc8 by task syz-     executor.0/9815 CPU: 0 PID: 9815 Comm: syz-executor.0 Not tainted 4.19.202-00874-gfc0fe04215a9 #2 Hardware     name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Call Trace: __dump_stack     lib/dump_stack.c:77 [inline] dump_stack+0xe4/0x14a lib/dump_stack.c:118     print_address_description+0x73/0x280 mm/kasan/report.c:253 kasan_report_error mm/kasan/report.c:352     [inline] kasan_report+0x272/0x370 mm/kasan/report.c:410 memcpy+0x1f/0x50 mm/kasan/kasan.c:302 memcpy     include/linux/string.h:377 [inline] sg_copy_buffer+0x150/0x1c0 lib/scatterlist.c:831     fill_from_dev_buffer+0x14f/0x340 drivers/scsi/scsi_debug.c:1021 resp_report_tgtpgs+0x5aa/0x770     drivers/scsi/scsi_debug.c:1772 schedule_resp+0x464/0x12f0 drivers/scsi/scsi_debug.c:4429     scsi_debug_queuecommand+0x467/0x1390 drivers/scsi/scsi_debug.c:5835 scsi_dispatch_cmd+0x3fc/0x9b0     drivers/scsi/scsi_lib.c:1896 scsi_request_fn+0x1042/0x1810 drivers/scsi/scsi_lib.c:2034
    __blk_run_queue_uncond block/blk-core.c:464 [inline] __blk_run_queue+0x1a4/0x380 block/blk-core.c:484     blk_execute_rq_nowait+0x1c2/0x2d0 block/blk-exec.c:78 sg_common_write.isra.19+0xd74/0x1dc0     drivers/scsi/sg.c:847 sg_write.part.23+0x6e0/0xd00 drivers/scsi/sg.c:716 sg_write+0x64/0xa0     drivers/scsi/sg.c:622 __vfs_write+0xed/0x690 fs/read_write.c:485 kill_bdev:block_device:00000000e138492c     vfs_write+0x184/0x4c0 fs/read_write.c:549 ksys_write+0x107/0x240 fs/read_write.c:599     do_syscall_64+0xc2/0x560 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe We get     'alen' from command its type is int. If userspace passes a large length we will get a negative 'alen'.
    Switch n, alen, and rlen to u32. (CVE-2021-47219)

  - In the Linux kernel, the following vulnerability has been resolved: kvm: avoid speculation-based attacks     from out-of-range memslot accesses KVM's mechanism for accessing guest memory translates a guest physical     address (gpa) to a host virtual address using the right-shifted gpa (also known as gfn) and a struct     kvm_memory_slot. The translation is performed in __gfn_to_hva_memslot using the following formula: hva =     slot->userspace_addr + (gfn - slot->base_gfn) * PAGE_SIZE It is expected that gfn falls within the     boundaries of the guest's physical memory. However, a guest can access invalid physical addresses in such     a way that the gfn is invalid. __gfn_to_hva_memslot is called from kvm_vcpu_gfn_to_hva_prot, which first     retrieves a memslot through __gfn_to_memslot. While __gfn_to_memslot does check that the gfn falls within     the boundaries of the guest's physical memory or not, a CPU can speculate the result of the check and     continue execution speculatively using an illegal gfn. The speculation can result in calculating an out-     of-bounds hva. If the resulting host virtual address is used to load another guest physical address, this     is effectively a Spectre gadget consisting of two consecutive reads, the second of which is data dependent     on the first. Right now it's not clear if there are any cases in which this is exploitable. One     interesting case was reported by the original author of this patch, and involves visiting guest page     tables on x86. Right now these are not vulnerable because the hva read goes through get_user(), which     contains an LFENCE speculation barrier. However, there are patches in progress for x86 uaccess.h to mask     kernel addresses instead of using LFENCE; once these land, a guest could use speculation to read from the     VMM's ring 3 address space. Other architectures such as ARM already use the address masking method, and     would be susceptible to this same kind of data-dependent access gadgets. Therefore, this patch proactively     protects from these attacks by masking out-of-bounds gfns in __gfn_to_hva_memslot, which blocks     speculation of invalid hvas. Sean Christopherson noted that this patch does not cover     kvm_read_guest_offset_cached. This however is limited to a few bytes past the end of the cache, and     therefore it is unlikely to be useful in the context of building a chain of data dependent accesses.
    (CVE-2021-47277)

  - In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero     to fix bug In current async pagefault logic, when a page is ready, KVM relies on     kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This     function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when     a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can     deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value, which is     confused with previous mention and may lead the loss of this READY event. This bug may cause task blocked     forever in Guest: INFO: task stress:7532 blocked for more than 1254 seconds. Not tainted 5.10.0 #16 echo     0 > /proc/sys/kernel/hung_task_timeout_secs disables this message. task:stress state:D stack: 0 pid: 7532     ppid: 1409 flags:0x00000080 Call Trace: __schedule+0x1e7/0x650 schedule+0x46/0xb0     kvm_async_pf_task_wait_schedule+0xad/0xe0 ? exit_to_user_mode_prepare+0x60/0x70
    __kvm_handle_async_pf+0x4f/0xb0 ? asm_exc_page_fault+0x8/0x30 exc_page_fault+0x6f/0x110 ?     asm_exc_page_fault+0x8/0x30 asm_exc_page_fault+0x1e/0x30 RIP: 0033:0x402d00 RSP: 002b:00007ffd31912500     EFLAGS: 00010206 RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0 RDX: 000000000007d011     RSI: 000000000007d000 RDI: 00000000021262b0 RBP: 00000000021262b0 R08: 0000000000000003 R09:
    0000000000000086 R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000 R13: 0000000000000002     R14: 000000000007d000 R15: 0000000000001000 (CVE-2022-48943)

  - In the Linux kernel, the following vulnerability has been resolved: ipv6: addrlabel: fix infoleak when     sending struct ifaddrlblmsg to network When copying a `struct ifaddrlblmsg` to the network,
    __ifal_reserved remained uninitialized, resulting in a 1-byte infoleak: BUG: KMSAN: kernel-network-     infoleak in __netdev_start_xmit ./include/linux/netdevice.h:4841 __netdev_start_xmit     ./include/linux/netdevice.h:4841 netdev_start_xmit ./include/linux/netdevice.h:4857 xmit_one     net/core/dev.c:3590 dev_hard_start_xmit+0x1dc/0x800 net/core/dev.c:3606 __dev_queue_xmit+0x17e8/0x4350     net/core/dev.c:4256 dev_queue_xmit ./include/linux/netdevice.h:3009 __netlink_deliver_tap_skb     net/netlink/af_netlink.c:307 __netlink_deliver_tap+0x728/0xad0 net/netlink/af_netlink.c:325     netlink_deliver_tap net/netlink/af_netlink.c:338 __netlink_sendskb net/netlink/af_netlink.c:1263     netlink_sendskb+0x1d9/0x200 net/netlink/af_netlink.c:1272 netlink_unicast+0x56d/0xf50     net/netlink/af_netlink.c:1360 nlmsg_unicast ./include/net/netlink.h:1061 rtnl_unicast+0x5a/0x80     net/core/rtnetlink.c:758 ip6addrlbl_get+0xfad/0x10f0 net/ipv6/addrlabel.c:628     rtnetlink_rcv_msg+0xb33/0x1570 net/core/rtnetlink.c:6082 ... Uninit was created at:
    slab_post_alloc_hook+0x118/0xb00 mm/slab.h:742 slab_alloc_node mm/slub.c:3398
    __kmem_cache_alloc_node+0x4f2/0x930 mm/slub.c:3437 __do_kmalloc_node mm/slab_common.c:954
    __kmalloc_node_track_caller+0x117/0x3d0 mm/slab_common.c:975 kmalloc_reserve net/core/skbuff.c:437
    __alloc_skb+0x27a/0xab0 net/core/skbuff.c:509 alloc_skb ./include/linux/skbuff.h:1267 nlmsg_new     ./include/net/netlink.h:964 ip6addrlbl_get+0x490/0x10f0 net/ipv6/addrlabel.c:608     rtnetlink_rcv_msg+0xb33/0x1570 net/core/rtnetlink.c:6082 netlink_rcv_skb+0x299/0x550     net/netlink/af_netlink.c:2540 rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:6109 netlink_unicast_kernel     net/netlink/af_netlink.c:1319 netlink_unicast+0x9ab/0xf50 net/netlink/af_netlink.c:1345     netlink_sendmsg+0xebc/0x10f0 net/netlink/af_netlink.c:1921 ... This patch ensures that the reserved field     is always initialized. (CVE-2022-49865)

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

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1782155469 advisory.

  - A vulnerability classified as problematic has been found in Linux Kernel. Affected is the function     j1939_session_destroy of the file net/can/j1939/transport.c. The manipulation leads to memory leak. It is     recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211932.
    (CVE-2022-3633)

  - In the Linux kernel, the following vulnerability has been resolved: udf: Fix preallocation discarding at     indirect extent boundary When preallocation extent is the first one in the extent block, the code would     corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid     some code duplication. (CVE-2022-48946)

  - In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix error exit of     privcmd_ioctl_dm_op() The error exit of privcmd_ioctl_dm_op() is calling unlock_pages() potentially with     pages being NULL, leading to a NULL dereference. Additionally lock_pages() doesn't check for     pin_user_pages_fast() having been completely successful, resulting in potentially not locking all pages     into memory. This could result in sporadic failures when using the related memory in user mode. Fix all of     that by calling unlock_pages() always with the real number of pinned pages, which will be zero in case     pages being NULL, and by checking the number of pages pinned by pin_user_pages_fast() matching the     expected number of pages. (CVE-2022-49989)

  - In the Linux kernel, the following vulnerability has been resolved: net: USB: Fix wrong-direction WARNING     in plusb.c The syzbot fuzzer detected a bug in the plusb network driver: A zero-length control-OUT     transfer was treated as a read instead of a write. In modern kernels this error provokes a WARNING: usb     1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0 WARNING: CPU: 0 PID: 4645 at     drivers/usb/core/urb.c:411 usb_submit_urb+0x14a7/0x1880 drivers/usb/core/urb.c:411 Modules linked in: CPU:
    1 PID: 4645 Comm: dhcpcd Not tainted 6.2.0-rc6-syzkaller-00050-g9f266ccaa2f5 #0 Hardware name: Google     Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 RIP: 0010:usb_submit_urb+0x14a7/0x1880     drivers/usb/core/urb.c:411 ... Call Trace: <TASK> usb_start_wait_urb+0x101/0x4b0     drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline]     usb_control_msg+0x320/0x4a0 drivers/usb/core/message.c:153 __usbnet_read_cmd+0xb9/0x390     drivers/net/usb/usbnet.c:2010 usbnet_read_cmd+0x96/0xf0 drivers/net/usb/usbnet.c:2068 pl_vendor_req     drivers/net/usb/plusb.c:60 [inline] pl_set_QuickLink_features drivers/net/usb/plusb.c:75 [inline]     pl_reset+0x2f/0xf0 drivers/net/usb/plusb.c:85 usbnet_open+0xcc/0x5d0 drivers/net/usb/usbnet.c:889
    __dev_open+0x297/0x4d0 net/core/dev.c:1417 __dev_change_flags+0x587/0x750 net/core/dev.c:8530     dev_change_flags+0x97/0x170 net/core/dev.c:8602 devinet_ioctl+0x15a2/0x1d70 net/ipv4/devinet.c:1147     inet_ioctl+0x33f/0x380 net/ipv4/af_inet.c:979 sock_do_ioctl+0xcc/0x230 net/socket.c:1169     sock_ioctl+0x1f8/0x680 net/socket.c:1286 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870     [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856 do_syscall_x64     arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80     entry_SYSCALL_64_after_hwframe+0x63/0xcd The fix is to call usbnet_write_cmd() instead of     usbnet_read_cmd() and remove the USB_DIR_IN flag. (CVE-2023-52742)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Make sure trace_printk() can     output as soon as it can be used Currently trace_printk() can be used as soon as early_trace_init() is     called from start_kernel(). But if a crash happens, and ftrace_dump_on_oops is set on the kernel command     line, all you get will be: [ 0.456075] <idle>-0 0dN.2. 347519us : Unknown type 6 [ 0.456075] <idle>-0     0dN.2. 353141us : Unknown type 6 [ 0.456075] <idle>-0 0dN.2. 358684us : Unknown type 6 This is because the     trace_printk() event (type 6) hasn't been registered yet. That gets done via an early_initcall(), which     may be early, but not early enough. Instead of registering the trace_printk() event (and other ftrace     events, which are not trace events) via an early_initcall(), have them registered at the same time that     trace_printk() can be used. This way, if there is a crash before early_initcall(), then the     trace_printk()s will actually be useful. (CVE-2023-53007)

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

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1782155469 advisory.

  - A vulnerability classified as problematic has been found in Linux Kernel. Affected is the function     j1939_session_destroy of the file net/can/j1939/transport.c. The manipulation leads to memory leak. It is     recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211932.
    (CVE-2022-3633)

  - In the Linux kernel, the following vulnerability has been resolved: udf: Fix preallocation discarding at     indirect extent boundary When preallocation extent is the first one in the extent block, the code would     corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid     some code duplication. (CVE-2022-48946)

  - In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix error exit of     privcmd_ioctl_dm_op() The error exit of privcmd_ioctl_dm_op() is calling unlock_pages() potentially with     pages being NULL, leading to a NULL dereference. Additionally lock_pages() doesn't check for     pin_user_pages_fast() having been completely successful, resulting in potentially not locking all pages     into memory. This could result in sporadic failures when using the related memory in user mode. Fix all of     that by calling unlock_pages() always with the real number of pinned pages, which will be zero in case     pages being NULL, and by checking the number of pages pinned by pin_user_pages_fast() matching the     expected number of pages. (CVE-2022-49989)

  - In the Linux kernel, the following vulnerability has been resolved: net: USB: Fix wrong-direction WARNING     in plusb.c The syzbot fuzzer detected a bug in the plusb network driver: A zero-length control-OUT     transfer was treated as a read instead of a write. In modern kernels this error provokes a WARNING: usb     1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0 WARNING: CPU: 0 PID: 4645 at     drivers/usb/core/urb.c:411 usb_submit_urb+0x14a7/0x1880 drivers/usb/core/urb.c:411 Modules linked in: CPU:
    1 PID: 4645 Comm: dhcpcd Not tainted 6.2.0-rc6-syzkaller-00050-g9f266ccaa2f5 #0 Hardware name: Google     Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 RIP: 0010:usb_submit_urb+0x14a7/0x1880     drivers/usb/core/urb.c:411 ... Call Trace: <TASK> usb_start_wait_urb+0x101/0x4b0     drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline]     usb_control_msg+0x320/0x4a0 drivers/usb/core/message.c:153 __usbnet_read_cmd+0xb9/0x390     drivers/net/usb/usbnet.c:2010 usbnet_read_cmd+0x96/0xf0 drivers/net/usb/usbnet.c:2068 pl_vendor_req     drivers/net/usb/plusb.c:60 [inline] pl_set_QuickLink_features drivers/net/usb/plusb.c:75 [inline]     pl_reset+0x2f/0xf0 drivers/net/usb/plusb.c:85 usbnet_open+0xcc/0x5d0 drivers/net/usb/usbnet.c:889
    __dev_open+0x297/0x4d0 net/core/dev.c:1417 __dev_change_flags+0x587/0x750 net/core/dev.c:8530     dev_change_flags+0x97/0x170 net/core/dev.c:8602 devinet_ioctl+0x15a2/0x1d70 net/ipv4/devinet.c:1147     inet_ioctl+0x33f/0x380 net/ipv4/af_inet.c:979 sock_do_ioctl+0xcc/0x230 net/socket.c:1169     sock_ioctl+0x1f8/0x680 net/socket.c:1286 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870     [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856 do_syscall_x64     arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80     entry_SYSCALL_64_after_hwframe+0x63/0xcd The fix is to call usbnet_write_cmd() instead of     usbnet_read_cmd() and remove the USB_DIR_IN flag. (CVE-2023-52742)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Make sure trace_printk() can     output as soon as it can be used Currently trace_printk() can be used as soon as early_trace_init() is     called from start_kernel(). But if a crash happens, and ftrace_dump_on_oops is set on the kernel command     line, all you get will be: [ 0.456075] <idle>-0 0dN.2. 347519us : Unknown type 6 [ 0.456075] <idle>-0     0dN.2. 353141us : Unknown type 6 [ 0.456075] <idle>-0 0dN.2. 358684us : Unknown type 6 This is because the     trace_printk() event (type 6) hasn't been registered yet. That gets done via an early_initcall(), which     may be early, but not early enough. Instead of registering the trace_printk() event (and other ftrace     events, which are not trace events) via an early_initcall(), have them registered at the same time that     trace_printk() can be used. This way, if there is a crash before early_initcall(), then the     trace_printk()s will actually be useful. (CVE-2023-53007)

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

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1780516677 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix potential CAN frame     reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider     concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The     following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during     isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will     trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
    19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e     net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline]     skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline]     isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline]     can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665     can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
    __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data     structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes     the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: sdata can be NULL     during AMPDU start ieee80211_tx_ba_session_handle_start() may get NULL for sdata when a deauthentication     is ongoing. Here a trace triggering the race with the hostapd test multi_ap_fronthaul_on_ap: (gdb) list
    *drv_ampdu_action+0x46 0x8b16 is in drv_ampdu_action (net/mac80211/driver-ops.c:396). 391 int ret =
    -EOPNOTSUPP; 392 393 might_sleep(); 394 395 sdata = get_bss_sdata(sdata); 396 if     (!check_sdata_in_driver(sdata)) 397 return -EIO; 398 399 trace_drv_ampdu_action(local, sdata, params); 400     wlan0: moving STA 02:00:00:00:03:00 to state 3 wlan0: associated wlan0: deauthenticating from     02:00:00:00:03:00 by local choice (Reason: 3=DEAUTH_LEAVING) wlan3.sta1: Open BA session requested for     02:00:00:00:00:00 tid 0 wlan3.sta1: dropped frame to 02:00:00:00:00:00 (unauthorized port) wlan0: moving     STA 02:00:00:00:03:00 to state 2 wlan0: moving STA 02:00:00:00:03:00 to state 1 wlan0: Removed STA     02:00:00:00:03:00 wlan0: Destroyed STA 02:00:00:00:03:00 BUG: unable to handle page fault for address:
    fffffffffffffb48 PGD 11814067 P4D 11814067 PUD 11816067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID:
    133397 Comm: kworker/u16:1 Tainted: G W 6.1.0-rc8-wt+ #59 Hardware name: QEMU Standard PC (Q35 + ICH9,     2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Workqueue: phy3 ieee80211_ba_session_work     [mac80211] RIP: 0010:drv_ampdu_action+0x46/0x280 [mac80211] Code: 53 48 89 f3 be 89 01 00 00 e8 d6 43 bf     ef e8 21 46 81 f0 83 bb a0 1b 00 00 04 75 0e 48 8b 9b 28 0d 00 00 48 81 eb 10 0e 00 00 <8b> 93 58 09 00 00     f6 c2 20 0f 84 3b 01 00 00 8b 05 dd 1c 0f 00 85 RSP: 0018:ffffc900025ebd20 EFLAGS: 00010287 RAX:
    0000000000000000 RBX: fffffffffffff1f0 RCX: ffff888102228240 RDX: 0000000080000000 RSI: ffffffff918c5de0     RDI: ffff888102228b40 RBP: ffffc900025ebd40 R08: 0000000000000001 R09: 0000000000000001 R10:
    0000000000000001 R11: 0000000000000000 R12: ffff888118c18ec0 R13: 0000000000000000 R14: ffffc900025ebd60     R15: ffff888018b7efb8 FS: 0000000000000000(0000) GS:ffff88817a600000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffffffffffb48 CR3: 0000000105228006 CR4: 0000000000170ee0     Call Trace: <TASK> ieee80211_tx_ba_session_handle_start+0xd0/0x190 [mac80211]     ieee80211_ba_session_work+0xff/0x2e0 [mac80211] process_one_work+0x29f/0x620 worker_thread+0x4d/0x3d0 ?     process_one_work+0x620/0x620 kthread+0xfb/0x120 ? kthread_complete_and_exit+0x20/0x20     ret_from_fork+0x22/0x30 </TASK> (CVE-2022-48875)

  - In the Linux kernel, the following vulnerability has been resolved: udf: Fix preallocation discarding at     indirect extent boundary When preallocation extent is the first one in the extent block, the code would     corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid     some code duplication. (CVE-2022-48946)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix crash when replugging     CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice     causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125]     blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth     99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb     e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162]     ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171]     really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177]
    __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183]
    __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189]     bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0     [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205]     usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211]     usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ?     pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221]     driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ?     driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232]
    __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [     71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246]     usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255]     process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ?     rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ?     kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274]
    ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17     (CVE-2022-48982)

  - In the Linux kernel, the following vulnerability has been resolved: can: m_can: pci: add missing     m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of     m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated by     m_can_class_allocate_dev(), otherwise there will be memleak. (CVE-2022-49024)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-021545 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()

    The ACPI buffer memory (out.pointer) returned by wmi_evaluate_method()     is not freed after the call, so it leads to memory leak.

    The method results in ACPI buffer is not used, so just pass NULL to     wmi_evaluate_method() which fixes the memory leak.

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

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-010952 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()

    The ACPI buffer memory (out.pointer) returned by wmi_evaluate_method()     is not freed after the call, so it leads to memory leak.

    The method results in ACPI buffer is not used, so just pass NULL to     wmi_evaluate_method() which fixes the memory leak.

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

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-006913 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()

    The ACPI buffer memory (out.pointer) returned by wmi_evaluate_method()     is not freed after the call, so it leads to memory leak.

    The method results in ACPI buffer is not used, so just pass NULL to     wmi_evaluate_method() which fixes the memory leak.

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

Note that Nessus has not tested for this issue 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 :

    media: v4l2-mem2mem: add lock to protect parameter num_rdy(CVE-2023-53519)

    md: Replace snprintf with scnprintf(CVE-2022-50299)

    mm/vmscan: don't try to reclaim hwpoison folio(CVE-2025-37834)

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()(CVE-2023-53271)

    md/raid10: fix wrong setting of max_corr_read_errors(CVE-2023-53313)

    scsi: target: target_core_configfs: Add length check to avoid buffer overflow(CVE-2025-39998)

    loop: Avoid updating block size under exclusive owner(CVE-2025-38709)

    mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory(CVE-2025-39883)

    scsi: qla4xxx: Prevent a potential error pointer dereference(CVE-2025-39676)

    NFS: Fix a race when updating an existing write(CVE-2025-39697)

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses(CVE-2023-7324)

    efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare(CVE-2025-39817)

    dm raid: fix address sanitizer warning in raid_resume(CVE-2022-50085)

    usb-storage: alauda: Fix uninit-value in alauda_check_media()(CVE-2023-53847)

    mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list(CVE-2025-39725)

    md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request(CVE-2023-53380)

    md/raid10: check slab-out-of-bounds in md_bitmap_get_counter(CVE-2023-53357)

    net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode(CVE-2023-53733)

    fs: quota: create dedicated workqueue for quota_release_work(CVE-2025-40196)

    partitions: mac: fix handling of bogus partition table(CVE-2025-21772)

    HID: hidraw: fix memory leak in hidraw_release()(CVE-2022-49981)

    pid: Add a judgment for ns null in pid_nr_ns(CVE-2025-40178)

    libceph: fix potential use-after-free in have_mon_and_osd_map()(CVE-2025-68285)

    watchdog: Fix kmemleak in watchdog_cdev_register(CVE-2023-53234)

    drivers/md/md-bitmap: check the return value of md_bitmap_get_counter()(CVE-2022-50402)

    PNP: fix name memory leak in pnp_alloc_dev()(CVE-2022-50278)

    ipvs: Defer ip_vs_ftp unregister during netns cleanup(CVE-2025-40018)

    nbd: Fix hung when signal interrupts nbd_start_device_ioctl()(CVE-2022-50314)

    igb: Do not free q_vector unless new one was allocated(CVE-2022-50252)

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed(CVE-2023-53481)

    cacheinfo: Fix shared_cpu_map to handle shared caches at different levels(CVE-2023-53254)

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info()(CVE-2025-40115)

    scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()(CVE-2023-53676)

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid(CVE-2025-68349)

    net: hns: fix possible memory leak in hnae_ae_register()(CVE-2022-50352)

    md: call __md_stop_writes in md_stop(CVE-2022-49987)

    net/packet: fix a race in packet_set_ring() and packet_notifier()(CVE-2025-38617)

    regulator: of: Fix refcount leak bug in of_get_regulation_constraints()(CVE-2022-50191)

    ubi: Fix use-after-free when volume resizing failed(CVE-2023-53800)

    HID: multitouch: Correct devm device reference for hidinput input_dev name(CVE-2023-53454)

    ipv6: reject malicious packets in ipv6_gso_segment()(CVE-2025-38572)

    md/raid10: fix leak of 'r10bio-remaining' for recovery(CVE-2023-53299)

    scsi: qla2xxx: Wait for io return on terminate rport(CVE-2023-53322)

    udf: Detect system inodes linked into directory hierarchy(CVE-2023-53695)

    igb: Fix igb_down hung on surprise removal(CVE-2023-53148)

    cifs: Fix warning and UAF when destroy the MR list(CVE-2023-53427)

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()(CVE-2023-53803)

    ubi: ensure that VID header offset + VID header size = alloc, size(CVE-2023-53265)

    fs/proc: fix uaf in proc_readdir_de()(CVE-2025-40271)

    firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails(CVE-2022-50087)

    md-raid10: fix KASAN warning(CVE-2022-50211)

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses(CVE-2023-53675)

    mmc: core: Fix kernel panic when remove non-standard SDIO card(CVE-2022-50640)

    nfs: handle failure of nfs_get_lock_context in unlock path(CVE-2025-38023)

    udf: Do not update file length for failed writes to inline files(CVE-2023-53295)

    RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug(CVE-2025-38024)

    sctp: check send stream number after wait_for_sndbuf(CVE-2023-53296)

    net/sched: sch_qfq: Fix race condition on qfq_aggregate(CVE-2025-38477)

    RDMA/rxe: Fix 'kernel NULL pointer dereference' error(CVE-2022-50671)

    i40e: add validation for ring_len param(CVE-2025-39973)

    md/raid1: Fix stack memory use after return in raid1_reshape(CVE-2025-38445)

    Squashfs: check return result of sb_min_blocksize(CVE-2025-38415)

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock(CVE-2022-50405)

    ip6_vti: fix slab-use-after-free in decode_session6(CVE-2023-53821)

    af_unix: Fix data-races around user-unix_inflight.(CVE-2023-53204)

    RDMA/rxe: Fix error unwind in rxe_create_qp()(CVE-2022-50127)

    __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock(CVE-2025-38058)

    NFSD: Protect against send buffer overflow in NFSv2 READ(CVE-2022-50410)

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()(CVE-2022-50646)

    sctp: handle the error returned from sctp_auth_asoc_init_active_key(CVE-2022-50243)

    vsock: Do not allow binding to VMADDR_PORT_ANY(CVE-2025-38618)

    smb: client: Fix use-after-free in cifs_fill_dirent(CVE-2025-38051)

    scsi: libiscsi: Initialize iscsi_conn-dd_data only if memory is allocated(CVE-2025-38700)

    sctp: fix a potential overflow in sctp_ifwdtsn_skip(CVE-2023-53372)

    pstore/ram: Check start of empty przs during init(CVE-2023-53331)

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()(CVE-2022-50449)

    md/raid10: prevent soft lockup while flush writes(CVE-2023-53151)

    nfsd: call op_release, even when op_func returns an error(CVE-2023-53241)

    cifs: Release folio lock on fscache read hit.(CVE-2023-53593)

    net: bridge: fix soft lockup in br_multicast_query_expired()(CVE-2025-39773)

    cifs: fix small mempool leak in SMB2_negotiate()(CVE-2022-49938)

    dm raid: fix address sanitizer warning in raid_status(CVE-2022-50084)

    nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()(CVE-2025-38724)

    scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()(CVE-2023-54014)

    block: fix resource leak in blk_register_queue() error path(CVE-2025-37980)

    drm/client: Fix memory leak in drm_client_target_cloned(CVE-2023-54091)

    dm flakey: fix a crash with invalid table line(CVE-2023-53786)

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()(CVE-2023-53817)

    hwrng: virtio - Fix race on data_avail and actual data(CVE-2023-53998)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    ppp: associate skb with a device at tx(CVE-2022-50655)

    fbdev: bitblit: bound-check glyph index in bit_putcs*(CVE-2025-40322)

    acct: fix potential integer overflow in encode_comp_t()(CVE-2022-50749)

    udf: Avoid double brelse() in udf_rename()(CVE-2022-50755)

    tee: add overflow check in register_shm_helper()(CVE-2022-50080)

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer(CVE-2022-50884)

    crypto: api - Use work queue in crypto_destroy_instance(CVE-2023-53799)

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()(CVE-2023-53623)

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.

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

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info()(CVE-2025-40115)

    scsi: target: Fix WRITE_SAME No Data Buffer crash(CVE-2022-21546)

    NFSD: Fix crash in nfsd4_read_release()(CVE-2025-40324)

    scsi: qla4xxx: Prevent a potential error pointer dereference(CVE-2025-39676)

    loop: Avoid updating block size under exclusive owner(CVE-2025-38709)

     media: v4l2-mem2mem: add lock to protect parameter num_rdy(CVE-2023-53519)

    mmc: rtsx_usb_sdmmc: fix return value check of mmc_add_host()(CVE-2022-50347)

    net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb(CVE-2023-53548)

    platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()(CVE-2022-50521)

    tipc: fix an information leak in tipc_topsrv_kern_subscr(CVE-2022-50531)

    scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()(CVE-2023-54014)

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume()(CVE-2023-53271)

    dma-buf: insert memory barrier before updating num_fences(CVE-2025-38095)

    md/raid10: fix wrong setting of max_corr_read_errors(CVE-2023-53313)

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses(CVE-2023-7324)

    scsi: storvsc: Fix handling of virtual Fibre Channel timeouts(CVE-2023-53245)

    md/raid10: prevent soft lockup while flush writes(CVE-2023-53151)

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()(CVE-2022-50449)

    sctp: fix a potential overflow in sctp_ifwdtsn_skip(CVE-2023-53372)

    crypto: api - Use work queue in crypto_destroy_instance(CVE-2023-53799)

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer(CVE-2022-50884)

    dm raid: fix address sanitizer warning in raid_status(CVE-2022-50084)

    cifs: fix small mempool leak in SMB2_negotiate()(CVE-2022-49938)

    net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device(CVE-2023-54015)

    ipv6: reject malicious packets in ipv6_gso_segment()(CVE-2025-38572)

    fs/proc: fix uaf in proc_readdir_de()(CVE-2025-40271)

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()(CVE-2023-53803)

    macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse(CVE-2025-68367)

    ubi: Fix use-after-free when volume resizing failed(CVE-2023-53800)

    crypto: qat - fix DMA transfer direction(CVE-2022-50774)

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()(CVE-2022-50646)

    mmc: core: Fix kernel panic when remove non-standard SDIO card(CVE-2022-50640)

    usb: host: ohci-ppc-of: Fix refcount leak bug(CVE-2022-50033)

    PNP: fix name memory leak in pnp_alloc_dev()(CVE-2022-50278)

    media: dvb-frontends: fix leak of memory fw(CVE-2022-50664)

    fs: quota: create dedicated workqueue for quota_release_work(CVE-2025-40196)

    acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl(CVE-2024-56662)

    scsi: ses: Handle enclosure with just a primary component gracefully(CVE-2023-53431)

    pid: Add a judgment for ns null in pid_nr_ns(CVE-2025-40178)

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid(CVE-2025-68349)

    hwrng: virtio - Fix race on data_avail and actual data(CVE-2023-53998)

    usb-storage: alauda: Fix uninit-value in alauda_check_media()(CVE-2023-53847)

    netlink: do not hard code device address lenth in fdb dumps(CVE-2023-53863)

    drm/client: Fix memory leak in drm_client_target_cloned(CVE-2023-54091)

    ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe(CVE-2025-68241)

    md/raid10: fix null-ptr-deref in raid10_sync_request(CVE-2023-53832)

    iommu/amd: Fix pci device refcount leak in ppr_notifier()(CVE-2022-50505)

    net: read sk-sk_family once in sk_mc_loop()(CVE-2023-53831)

    fbdev: bitblit: bound-check glyph index in bit_putcs*(CVE-2025-40322)

    bpf: make sure skb-len != 0 when redirecting to a tunneling device(CVE-2022-50253)

    ppp: associate skb with a device at tx(CVE-2022-50655)

    ip6_vti: fix slab-use-after-free in decode_session6(CVE-2023-53821)

    hwrng: amd - Fix PCI device refcount leak(CVE-2022-50868)

    netlink: annotate accesses to nlk-cb_running(CVE-2023-53853)

    acct: fix potential integer overflow in encode_comp_t()(CVE-2022-50749)

    RDMA/rxe: Fix 'kernel NULL pointer dereference' error(CVE-2022-50671)

    udf: Avoid double brelse() in udf_rename()(CVE-2022-50755)

    dm flakey: fix a crash with invalid table line(CVE-2023-53786)

    libceph: fix potential use-after-free in have_mon_and_osd_map()(CVE-2025-68285)

    crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()(CVE-2023-53817)

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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4320-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50334: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (bsc#1249857).
    - CVE-2022-50490: bpf: Propagate error from htab_lock_bucket() to userspace (bsc#1251164).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53500: xfrm: fix slab-use-after-free in decode_session6 (bsc#1250816).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53574: wifi: rtw88: delete timer and free skb queue when unloading (bsc#1251222).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53673: Bluetooth: hci_event: call disconnect callback before deleting conn (bsc#1251763).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).
    - CVE-2025-38084: hugetlb: unshare some PMDs when splitting VMAs (bsc#1245498).
    - CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).
    - CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).
    - CVE-2025-39742: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (bsc#1249479).
    - CVE-2025-39797: xfrm: Duplicate SPI Handling (bsc#1249608).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).
    - CVE-2025-39981: Bluetooth: MGMT: Fix possible UAFs (bsc#1252060).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).

    The following non security issues were fixed:

    - NFS: remove revoked delegation from server's delegation list (bsc#1246211).
    - NFSv4: Allow FREE_STATEID to clean up delegations (bsc#1246211).
    - fbcon: Fix OOB access in font allocation (bsc#1252033)
    - kabi fix for NFSv4: Allow FREE_STATEID to clean up delegations (bsc#1246211).
    - kernel-subpackage-spec: Do not doubly-sign modules (bsc#1251930).
    - mm: avoid unnecessary page fault retires on shared memory types (bsc#1251823).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).
    - net: mana: Switch to page pool for jumbo frames (bsc#1248754).
    - net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency     (bsc#1248754).
    - netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).
    - rpm/check-for-config-changes: ignore CONFIG_SCHED_PROXY_EXEC, too (bsc#1250946)

Tenable has extracted the preceding description block directly from the SUSE 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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4111-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50334: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (bsc#1249857).
    - CVE-2022-50490: bpf: Propagate error from htab_lock_bucket() to userspace (bsc#1251164).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53500: xfrm: fix slab-use-after-free in decode_session6 (bsc#1250816).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53574: wifi: rtw88: delete timer and free skb queue when unloading (bsc#1251222).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53673: Bluetooth: hci_event: call disconnect callback before deleting conn (bsc#1251763).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2025-39742: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (bsc#1249479).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).
    - CVE-2025-40088: hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp() (bsc#1252904).
    - CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).

    The following non security issues were fixed:

    - fbcon: Fix OOB access in font allocation (bsc#1252033)
    - mm: avoid unnecessary page fault retires on shared memory types (bsc#1251823).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).

Tenable has extracted the preceding description block directly from the SUSE 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.

  - platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() The ACPI buffer memory (out.pointer)     returned by wmi_evaluate_method() is not freed after the call, so it leads to memory leak. The method     results in ACPI buffer is not used, so just pass NULL to wmi_evaluate_method() which fixes the memory     leak. (CVE-2022-50521)

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

An update of the linux package has been released.

ID	Name	Product	Family	Type	Severity
362062	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1778756832)	Nessus	CentOS Local Security Checks	Local	high
359694	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Rocky Linux Local Security Checks	Local	low
359640	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Alma Linux Local Security Checks	Local	low
351689	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1780516677)	Nessus	Alma Linux Local Security Checks	Local	high
315796	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-021545)	Nessus	Unity Linux Local Security Checks	Local	medium
308924	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-010952)	Nessus	Unity Linux Local Security Checks	Local	medium
308292	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-006913)	Nessus	Unity Linux Local Security Checks	Local	medium
302981	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)	Nessus	Huawei Local Security Checks	Local	high
302971	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2026-1629)	Nessus	Huawei Local Security Checks	Local	high
302543	EulerOS Virtualization 2.10.0 : kernel (EulerOS-SA-2026-1557)	Nessus	Huawei Local Security Checks	Local	high
302405	EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1313)	Nessus	Huawei Local Security Checks	Local	high
297598	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1212)	Nessus	Huawei Local Security Checks	Local	high
297592	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2026-1224)	Nessus	Huawei Local Security Checks	Local	high
280691	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:4320-1)	Nessus	SuSE Local Security Checks	Local	high
275594	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:4111-1)	Nessus	SuSE Local Security Checks	Local	high
270184	Linux Distros Unpatched Vulnerability : CVE-2022-50521	Nessus	Misc.	Local	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-50521

medium

Tenable Plugins

high

low

low

high

medium

medium

medium

high

high

high

high

high

high

high

high

medium

high