In the Linux kernel, the following vulnerability has been resolved: skbuff: Account for tail adjustment during pull operations Extending the tail can have some unexpected side effects if a program uses a helper like BPF_FUNC_skb_pull_data to read partial content beyond the head skb headlen when all the skbs in the gso frag_list are linear with no head_frag - kernel BUG at net/core/skbuff.c:4219! pc : skb_segment+0xcf4/0xd2c lr : skb_segment+0x63c/0xd2c Call trace: skb_segment+0xcf4/0xd2c __udp_gso_segment+0xa4/0x544 udp4_ufo_fragment+0x184/0x1c0 inet_gso_segment+0x16c/0x3a4 skb_mac_gso_segment+0xd4/0x1b0 __skb_gso_segment+0xcc/0x12c udp_rcv_segment+0x54/0x16c udp_queue_rcv_skb+0x78/0x144 udp_unicast_rcv_skb+0x8c/0xa4 __udp4_lib_rcv+0x490/0x68c udp_rcv+0x20/0x30 ip_protocol_deliver_rcu+0x1b0/0x33c ip_local_deliver+0xd8/0x1f0 ip_rcv+0x98/0x1a4 deliver_ptype_list_skb+0x98/0x1ec __netif_receive_skb_core+0x978/0xc60 Fix this by marking these skbs as GSO_DODGY so segmentation can handle the tail updates accordingly.

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

  - In the Linux kernel, the following vulnerability has been resolved: samples/landlock: Fix path_list memory     leak Clang static analysis reports this error sandboxer.c:134:8: warning: Potential leak of memory pointed     to by 'path_list' ret = 0; ^ path_list is allocated in parse_path() but never freed. (CVE-2021-47654)

  - In the Linux kernel, the following vulnerability has been resolved: tty: synclink_gt: Fix null-pointer-     dereference in slgt_clean() When the driver fails at alloc_hdlcdev(), and then we remove the driver     module, we will get the following splat: [ 25.065966] general protection fault, probably for non-canonical     address 0xdffffc0000000182: 0000 [#1] PREEMPT SMP KASAN PTI [ 25.066914] KASAN: null-ptr-deref in range     [0x0000000000000c10-0x0000000000000c17] [ 25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0 [     25.077709] Call Trace: [ 25.077924] <TASK> [ 25.078108] unregister_hdlc_device+0x16/0x30 [ 25.078481]     slgt_cleanup+0x157/0x9f0 [synclink_gt] Fix this by checking whether the 'info->netdev' is a null pointer     first. (CVE-2022-49307)

  - In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in     ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing     the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid the potential memory leak.
    (CVE-2022-49627)

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak     problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 (tracing:
    fix double free) said, the double free problem reported by clang static analyzer is: > In     parse_var_defs() if there is a problem allocating > var_defs.expr, the earlier var_defs.name is freed. >     This free is duplicated by free_var_defs() which frees > the rest of the list. However, if there is a     problem allocating N-th var_defs.expr: + in parse_var_defs(), the freed 'earlier var_defs.name' is     actually the N-th var_defs.name; + then in free_var_defs(), the names from 0th to (N-1)-th are freed; IF     ALLOCATING PROBLEM HAPPENED HERE!!! -+ \ | 0th 1th (N-1)-th N-th V     +-------------+-------------+-----+-------------+----------- var_defs: | name | expr | name | expr | ... |     name | expr | name | /// +-------------+-------------+-----+-------------+----------- These two frees     don't act on same name, so there was no double free problem before. Conversely, after that commit, we     get a memory leak problem because the above N-th var_defs.name is not freed. If enable     CONFIG_DEBUG_KMEMLEAK and inject a fault at where the N-th var_defs.expr allocated, then execute on shell     like: $ echo 'hist:key=call_site:val=$v1,$v2:v1=bytes_req,v2=bytes_alloc' > \     /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger Then kmemleak reports: unreferenced object     0xffff8fb100ef3518 (size 8): comm bash, pid 196, jiffies 4295681690 (age 28.538s) hex dump (first 8     bytes): 76 31 00 00 b1 8f ff ff v1...... backtrace: [<0000000038fe4895>] kstrdup+0x2d/0x60     [<00000000c99c049a>] event_hist_trigger_parse+0x206f/0x20e0 [<00000000ae70d2cc>]     trigger_process_regex+0xc0/0x110 [<0000000066737a4c>] event_trigger_write+0x75/0xd0 [<000000007341e40c>]     vfs_write+0xbb/0x2a0 [<0000000087fde4c2>] ksys_write+0x59/0xd0 [<00000000581e9cdf>]     do_syscall_64+0x3a/0x80 [<00000000cf3b065c>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (CVE-2022-49648)

  - In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM     Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio == 0. CallTrace: Hardware name: H3C     R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack: ffffc90006714000 RIP:
    0010:backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: 0018:ffff880c10e83ec0 EFLAGS: 00010202 RAX:
    0000000000002710 RBX: ffff88096cd7f780 RCX: 0000000000000064 RDX: 0000000000000000 RSI: 0000000000000002     RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10:
    0000000000000000 R11: 0000000000000000 R12: 000000001d7c6c09 R13: ffff88096cd7f780 R14: ffff880b174fe800     R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880c10e80000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000a0965b00 CR3: 000000000200a003 CR4: 00000000007606e0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
    00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> ib_poll_handler+0x43/0x80     [ib_core] irq_poll_softirq+0xae/0x110 __do_softirq+0xd1/0x28c irq_exit+0xde/0xf0 do_IRQ+0x54/0xe0     common_interrupt+0x8f/0x8f </IRQ> ? cpuidle_enter_state+0xd9/0x2a0 ? cpuidle_enter_state+0xc7/0x2a0 ?     do_idle+0x170/0x1d0 ? cpu_startup_entry+0x6f/0x80 ? start_secondary+0x1b9/0x210 ?     secondary_startup_64+0xa5/0xb0 Code: 0f 87 e1 00 00 00 8b 4c 24 14 44 8b 43 14 89 c8 4d 63 c8 44 29 c0 99     31 d0 29 d0 31 d2 48 98 48 8d 04 80 48 8d 04 80 48 c1 e0 02 <49> f7 f1 48 83 f8 0a 0f 86 c1 00 00 00 44 39     c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0 (CVE-2022-49670)

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.

  - 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: 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)

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

  - 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: 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)

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

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

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove()(CVE-2023-53521)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    scsi: lpfc: Fix buffer free/clear order in deferred receive path(CVE-2025-39841)

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

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

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    udf: Do not bother merging very long extents(CVE-2023-53506)

    fbdev: fix potential buffer overflow in do_register_framebuffer()(CVE-2025-38702)

    mm/slub: avoid accessing metadata when pointer is invalid in object_err()(CVE-2025-39902)

    xhci: Remove device endpoints from bandwidth list when freeing the device(CVE-2022-50470)

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

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

    thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash(CVE-2022-50494)

    md: fix a crash in mempool_free(CVE-2022-50381)

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

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

    fs: dlm: fix invalid derefence of sb_lvbptr(CVE-2022-50516)

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

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

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

    udf: Fix uninitialized array access for some pathnames(CVE-2023-53165)

    ext4: avoid crash when inline data creation follows DIO write(CVE-2022-50435)

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

    scsi: qla2xxx: Pointer may be dereferenced(CVE-2023-53150)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    blk-mq: use quiesced elevator switch when reinitializing queues(CVE-2022-50552)

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

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    pnode: terminate at peers of source(CVE-2022-50280)

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

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

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

    usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info()(CVE-2022-50544)

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

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

    mtd: Fix device name leak when register device failed in add_mtd_device()(CVE-2022-50566)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/mipi-dsi: Detach devices when removing the host(CVE-2022-50489)

    ipv6: Fix out-of-bounds access in ipv6_find_tlv()(CVE-2023-53705)

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

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

    PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free(CVE-2023-53446)

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

    rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails(CVE-2023-53307)

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

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

    icmp6: Fix null-ptr-deref of ip6_null_entry-rt6i_idev in icmp6_dev().(CVE-2023-53343)

    calipso: Fix null-ptr-deref in calipso_req_{set,del}attr().(CVE-2025-38181)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region(CVE-2023-52989)

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

    dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path(CVE-2023-53604)

    qede: confirm skb is allocated before using(CVE-2022-49084)

    sctp: linearize cloned gso packets in sctp_rcv(CVE-2025-38718)

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

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

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

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

    cifs: fix oops during encryption(CVE-2022-50341)

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

    uio_hv_generic: Let userspace take care of interrupt mask(CVE-2025-40048)

    posix-timers: Ensure timer ID search-loop limit is valid(CVE-2023-53728)

    tipc: fix a null-ptr-deref in tipc_topsrv_accept(CVE-2022-50555)

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    x86/MCE: Always save CS register on AMD Zen IF Poison errors(CVE-2023-53438)

    xfrm: fix slab-use-after-free in decode_session6(CVE-2023-53500)

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

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

    firewire: net: fix use after free in fwnet_finish_incoming_packet()(CVE-2023-53432)

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

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

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

    crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg(CVE-2025-39964)

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

    skbuff: Account for tail adjustment during pull operations(CVE-2022-50365)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    skbuff: skb_segment, Call zero copy functions before using skbuff frags(CVE-2023-53354)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    net: fix skb leak in __skb_tstamp_tx()(CVE-2023-53716)

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    serial: arc_uart: fix of_iomap leak in `arc_serial_probe`(CVE-2023-53719)

    fs: udf: fix OOB read in lengthAllocDescs handling(CVE-2025-40044)

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

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

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

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

    iommu/vt-d: Clean up si_domain in the init_dmars() error path(CVE-2022-50482)

    VMCI: check context-notify_page after call to get_user_pages_fast() to avoid GPF(CVE-2023-53259)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    ip_vti: fix potential slab-use-after-free in decode_session6(CVE-2023-53559)

    netfilter: conntrack: Avoid nf_ct_helper_hash uses after free(CVE-2023-53619)

    Input: MT - limit max slots(CVE-2024-45008)

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992840 advisory.

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

    skbuff: Account for tail adjustment during pull operations

    Extending the tail can have some unexpected side effects if a program uses     a helper like BPF_FUNC_skb_pull_data to read partial content beyond the     head skb headlen when all the skbs in the gso frag_list are linear with no     head_frag -

      kernel BUG at net/core/skbuff.c:4219!       pc : skb_segment+0xcf4/0xd2c       lr : skb_segment+0x63c/0xd2c       Call trace:
       skb_segment+0xcf4/0xd2c
       __udp_gso_segment+0xa4/0x544        udp4_ufo_fragment+0x184/0x1c0        inet_gso_segment+0x16c/0x3a4        skb_mac_gso_segment+0xd4/0x1b0
       __skb_gso_segment+0xcc/0x12c        udp_rcv_segment+0x54/0x16c        udp_queue_rcv_skb+0x78/0x144        udp_unicast_rcv_skb+0x8c/0xa4
       __udp4_lib_rcv+0x490/0x68c        udp_rcv+0x20/0x30        ip_protocol_deliver_rcu+0x1b0/0x33c        ip_local_deliver+0xd8/0x1f0        ip_rcv+0x98/0x1a4        deliver_ptype_list_skb+0x98/0x1ec
       __netif_receive_skb_core+0x978/0xc60

    Fix this by marking these skbs as GSO_DODGY so segmentation can handle     the tail updates accordingly.

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-2025-992200 advisory.

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

    skbuff: Account for tail adjustment during pull operations

    Extending the tail can have some unexpected side effects if a program uses     a helper like BPF_FUNC_skb_pull_data to read partial content beyond the     head skb headlen when all the skbs in the gso frag_list are linear with no     head_frag -

      kernel BUG at net/core/skbuff.c:4219!       pc : skb_segment+0xcf4/0xd2c       lr : skb_segment+0x63c/0xd2c       Call trace:
       skb_segment+0xcf4/0xd2c
       __udp_gso_segment+0xa4/0x544        udp4_ufo_fragment+0x184/0x1c0        inet_gso_segment+0x16c/0x3a4        skb_mac_gso_segment+0xd4/0x1b0
       __skb_gso_segment+0xcc/0x12c        udp_rcv_segment+0x54/0x16c        udp_queue_rcv_skb+0x78/0x144        udp_unicast_rcv_skb+0x8c/0xa4
       __udp4_lib_rcv+0x490/0x68c        udp_rcv+0x20/0x30        ip_protocol_deliver_rcu+0x1b0/0x33c        ip_local_deliver+0xd8/0x1f0        ip_rcv+0x98/0x1a4        deliver_ptype_list_skb+0x98/0x1ec
       __netif_receive_skb_core+0x978/0xc60

    Fix this by marking these skbs as GSO_DODGY so segmentation can handle     the tail updates accordingly.

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-2025-992249 advisory.

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

    skbuff: Account for tail adjustment during pull operations

    Extending the tail can have some unexpected side effects if a program uses     a helper like BPF_FUNC_skb_pull_data to read partial content beyond the     head skb headlen when all the skbs in the gso frag_list are linear with no     head_frag -

      kernel BUG at net/core/skbuff.c:4219!       pc : skb_segment+0xcf4/0xd2c       lr : skb_segment+0x63c/0xd2c       Call trace:
       skb_segment+0xcf4/0xd2c
       __udp_gso_segment+0xa4/0x544        udp4_ufo_fragment+0x184/0x1c0        inet_gso_segment+0x16c/0x3a4        skb_mac_gso_segment+0xd4/0x1b0
       __skb_gso_segment+0xcc/0x12c        udp_rcv_segment+0x54/0x16c        udp_queue_rcv_skb+0x78/0x144        udp_unicast_rcv_skb+0x8c/0xa4
       __udp4_lib_rcv+0x490/0x68c        udp_rcv+0x20/0x30        ip_protocol_deliver_rcu+0x1b0/0x33c        ip_local_deliver+0xd8/0x1f0        ip_rcv+0x98/0x1a4        deliver_ptype_list_skb+0x98/0x1ec
       __netif_receive_skb_core+0x978/0xc60

    Fix this by marking these skbs as GSO_DODGY so segmentation can handle     the tail updates accordingly.

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

    The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} (bsc#1246968).
    - CVE-2022-50242: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() (bsc#1249696).
    - CVE-2022-50244: cxl: fix possible null-ptr-deref in cxl_pci_init_afu|adapter() (bsc#1249647).
    - CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).
    - CVE-2022-50258: wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds()     (bsc#1249947).
    - CVE-2022-50265: kcm: annotate data-races around kcm->rx_wait (bsc#1249744).
    - CVE-2022-50278: PNP: fix name memory leak in pnp_alloc_dev() (bsc#1249715).
    - CVE-2022-50285: mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages (bsc#1249803).
    - CVE-2022-50288: qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure (bsc#1249802).
    - CVE-2022-50291: kcm: annotate data-races around kcm->rx_psock (bsc#1249798).
    - CVE-2022-50294: wifi: libertas: fix memory leak in lbs_init_adapter() (bsc#1249799).
    - CVE-2022-50297: wifi: ath9k: verify the expected usb_endpoints are present (bsc#1250250).
    - CVE-2022-50304: mm: export bdi_unregister (bsc#1249725).
    - CVE-2022-50311: cxl: Fix refcount leak in cxl_calc_capp_routing (bsc#1249720).
    - CVE-2022-50312: drivers: serial: jsm: fix some leaks in probe (bsc#1249716).
    - CVE-2022-50321: wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit() (bsc#1249706).
    - CVE-2022-50330: crypto: cavium - prevent integer overflow loading firmware (bsc#1249700).
    - CVE-2022-50349: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (bsc#1249920).
    - CVE-2022-50352: net: hns: fix possible memory leak in hnae_ae_register() (bsc#1249922).
    - CVE-2022-50359: media: cx88: Fix a null-ptr-deref bug in buffer_prepare() (bsc#1250269).
    - CVE-2022-50365: skbuff: Account for tail adjustment during pull operations (bsc#1250084).
    - CVE-2022-50375: tty: serial: fsl_lpuart: disable dma rx/tx use flags in lpuart_dma_shutdown     (bsc#1250132).
    - CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free (bsc#1250301).
    - CVE-2022-50396: net: sched: fix memory leak in tcindex_set_parms (bsc#1250104).
    - CVE-2022-50402: drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() (bsc#1250363).
    - CVE-2022-50405: net/tunnel: wait until all sk_user_data reader finish before releasing the sock     (bsc#1250155).
    - CVE-2022-50406: iomap: iomap: fix memory corruption when recording errors during writeback     (bsc#1250165).
    - CVE-2022-50408: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() (bsc#1250391).
    - CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).
    - CVE-2022-50419: Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times (bsc#1250394).
    - CVE-2023-53148: igb: Do not bring the device up after non-fatal error (bsc#1249842).
    - CVE-2023-53153: wifi: cfg80211: Partial revert 'wifi: cfg80211: Fix use after free for wext'     (bsc#1249877).
    - CVE-2023-53176: serial: 8250: Fix oops for port->pm on uart_change_pm() (bsc#1249991).
    - CVE-2023-53178: mm: zswap: fix missing folio cleanup in writeback race path (bsc#1249827 git-fix).
    - CVE-2023-53199: wifi: ath9k: hif_usb: clean up skbs if ath9k_hif_usb_rx_stream() fails (bsc#1249683).
    - CVE-2023-53201: RDMA/bnxt_re: wraparound mbox producer index (bsc#1249687).
    - CVE-2023-53226: wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet (bsc#1249658).
    - CVE-2023-53248: drm/amdgpu: install stub fence into potential unused fence pointers (bsc#1249779).
    - CVE-2023-53254: drivers: base: cacheinfo: Fix shared_cpu_map changes in event of CPU hotplug     (bsc#1249871).
    - CVE-2023-53272: net: ena: fix shift-out-of-bounds in exponential backoff (bsc#1249917).
    - CVE-2023-53277: wifi: iwl3945: Add missing check for create_singlethread_workqueue (bsc#1249936).
    - CVE-2023-53288: drm/client: Fix memory leak in drm_client_modeset_probe (bsc#1250058).
    - CVE-2023-53298: nfc: fix memory leak of se_io context in nfc_genl_se_io (bsc#1249944).
    - CVE-2023-53302: wifi: iwl4965: Add missing check for create_singlethread_workqueue() (bsc#1249958).
    - CVE-2023-53305: Bluetooth: L2CAP: Fix use-after-free (bsc#1250049).
    - CVE-2023-53309: drm/radeon: Fix integer overflow in radeon_cs_parser_init (bsc#1250055).
    - CVE-2023-53317: ext4: fix WARNING in mb_find_extent (bsc#1250081).
    - CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).
    - CVE-2023-53335: RDMA/cxgb4: Fix potential null-ptr-deref in pass_establish() (bsc#1250072).
    - CVE-2023-53344: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write (bsc#1250023).
    - CVE-2023-53348: btrfs: fix deadlock when aborting transaction during relocation with scrub     (bsc#1250018).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53384: wifi: mwifiex: avoid possible NULL skb pointer dereference (bsc#1250127).
    - CVE-2023-53393: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device (bsc#1250114).
    - CVE-2023-53395: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer (bsc#1250358).
    - CVE-2023-53397: modpost: fix off by one in is_executable_section() (bsc#1250125).
    - CVE-2023-53400: ALSA: hda: Fix Oops by 9.1 surround channel names (bsc#1250328).
    - CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).
    - CVE-2023-53441: bpf: cpumap: Fix memory leak in cpu_map_update_elem (bsc#1250150).
    - CVE-2024-53194: PCI: Fix use-after-free of slot->bus on hot remove (bsc#1235459).
    - CVE-2024-58240: tls: separate no-async decryption request handling from async (bsc#1248847).
    - CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).
    - CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).
    - CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree     (bsc#1248255).
    - CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).
    - CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).
    - CVE-2025-38602: wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (bsc#1248341).
    - CVE-2025-38604: wifi: rtl818x: Kill URBs before clearing tx status queue (bsc#1248333).
    - CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).
    - CVE-2025-38624: PCI: pnv_php: Clean up allocated IRQs on unplug (bsc#1248617).
    - CVE-2025-38632: pinmux: fix race causing mux_owner NULL with active mux_usecount (bsc#1248669).
    - CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).
    - CVE-2025-38665: can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode     (bsc#1248648).
    - CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).
    - CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).
    - CVE-2025-38702: fbdev: fix potential buffer overflow in do_register_framebuffer() (bsc#1249254).
    - CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).
    - CVE-2025-38712: hfsplus: do not use BUG_ON() in hfsplus_create_attributes_file() (bsc#1249194).
    - CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).
    - CVE-2025-38729: ALSA: usb-audio: Validate UAC3 power domain descriptors, too (bsc#1249164).
    - CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).
    - CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).
    - CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).
    - CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).
    - CVE-2025-39706: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq (bsc#1249413).
    - CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).
    - CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).
    - CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).
    - CVE-2025-39757: ALSA: usb-audio: Fix size validation in convert_chmap_v3() (bsc#1249515).
    - CVE-2025-39760: usb: core: config: Prevent OOB read in SS endpoint companion parsing (bsc#1249598).
    - CVE-2025-39763: ACPICA: Fix error code path in acpi_ds_call_control_method() (bsc#1249615).
    - CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).
    - CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).
    - CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).
    - CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).
    - CVE-2025-39800: btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (bsc#1250177).
    - CVE-2025-39808: HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (bsc#1250088).
    - CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).
    - CVE-2025-39833: mISDN: hfcpci: Fix warning when deleting uninitialized timer (bsc#1250028).
    - CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).
    - CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).
    - CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).
    - CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).
    - CVE-2025-39863: wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work     (bsc#1250281).
    - CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).
    - CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).
    - CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).
    - CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).


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.

  - In the Linux kernel, the following vulnerability has been resolved: skbuff: Account for tail adjustment     during pull operations Extending the tail can have some unexpected side effects if a program uses a helper     like BPF_FUNC_skb_pull_data to read partial content beyond the head skb headlen when all the skbs in the     gso frag_list are linear with no head_frag - kernel BUG at net/core/skbuff.c:4219! pc :
    skb_segment+0xcf4/0xd2c lr : skb_segment+0x63c/0xd2c Call trace: skb_segment+0xcf4/0xd2c
    __udp_gso_segment+0xa4/0x544 udp4_ufo_fragment+0x184/0x1c0 inet_gso_segment+0x16c/0x3a4     skb_mac_gso_segment+0xd4/0x1b0 __skb_gso_segment+0xcc/0x12c udp_rcv_segment+0x54/0x16c     udp_queue_rcv_skb+0x78/0x144 udp_unicast_rcv_skb+0x8c/0xa4 __udp4_lib_rcv+0x490/0x68c udp_rcv+0x20/0x30     ip_protocol_deliver_rcu+0x1b0/0x33c ip_local_deliver+0xd8/0x1f0 ip_rcv+0x98/0x1a4     deliver_ptype_list_skb+0x98/0x1ec __netif_receive_skb_core+0x978/0xc60 Fix this by marking these skbs as     GSO_DODGY so segmentation can handle the tail updates accordingly. (CVE-2022-50365)

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

The version of kernel installed on the remote host is prior to 4.14.304-226.531. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2023-1932 advisory.

    Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC     interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It     appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol     headers are all contained within the linear section of the SKB and some NICs behave badly if this is not     the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x)     though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with     split headers, netback will forward those violating above mentioned assumption to the networking core,     resulting in said misbehavior. (CVE-2022-3643)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42328)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42329)

    An issue was discovered in the Linux kernel through 6.0.10. l2cap_config_req in net/bluetooth/l2cap_core.c     has an integer wraparound via L2CAP_CONF_REQ packets. (CVE-2022-45934)

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    udf: Fix preallocation discarding at indirect extent boundary (CVE-2022-48946)

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

    Bluetooth: L2CAP: Fix u8 overflow (CVE-2022-48947)

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

    igb: Initialize mailbox message for VF reset (CVE-2022-48949)

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

    ipv6: avoid use-after-free in ip6_fragment() (CVE-2022-48956)

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

    mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (CVE-2022-48972)

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

    HID: core: fix shift-out-of-bounds in hid_report_raw_event (CVE-2022-48978)

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

    media: v4l2-dv-timings.c: fix too strict blanking sanity checks (CVE-2022-48987)

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

    memcg: fix possible use-after-free in memcg_write_event_control() (CVE-2022-48988)

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

    mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (CVE-2022-48991)

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

    mmc: vub300: fix return value check of mmc_add_host() (CVE-2022-50251)

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

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

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

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

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

    drm/radeon: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50275)

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

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

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    rapidio: fix possible name leaks when rio_add_device() fails (CVE-2022-50343)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

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

    misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (CVE-2022-50349)

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

    skbuff: Account for tail adjustment during pull operations (CVE-2022-50365)

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

    md: fix a crash in mempool_free (CVE-2022-50381)

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

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50389)

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

    nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure (CVE-2022-50401)

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

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

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

    ACPICA: Fix error code path in acpi_ds_call_control_method() (CVE-2022-50411)

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

    scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails (CVE-2022-50414)

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

    ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (CVE-2022-50423)

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

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING (CVE-2022-50430)

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

    blk-mq: fix possible memleak when register 'hctx' failed (CVE-2022-50434)

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

    MIPS: vpe-mt: fix possible memory leak while module exiting (CVE-2022-50462)

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

    macintosh: fix possible memory leak in macio_add_one_device() (CVE-2022-50474)

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

    nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() (CVE-2022-50478)

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

    dm cache: Fix UAF in destroy() (CVE-2022-50496)

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

    binfmt_misc: fix shift-out-of-bounds in check_special_flags (CVE-2022-50497)

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

    mtd: lpddr2_nvm: Fix possible null-ptr-deref (CVE-2022-50503)

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

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

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

    drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios() (CVE-2022-50520)

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

    mcb: mcb-parse: fix error handing in chameleon_parse_gdd() (CVE-2022-50522)

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

    dm thin: Use last transaction's pmd->root when commit failed (CVE-2022-50534)

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

    dm thin: Fix UAF in run_timer_softirq() (CVE-2022-50563)

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

    mtd: Fix device name leak when register device failed in add_mtd_device() (CVE-2022-50566)

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

    fs: jfs: fix shift-out-of-bounds in dbAllocAG (CVE-2022-50567)

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

    class: fix possible memory leak in __class_register() (CVE-2022-50578)

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

    hfs: fix OOB Read in __hfs_brec_find (CVE-2022-50581)

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

    serial: amba-pl011: avoid SBSA UART accessing DMACR register (CVE-2022-50625)

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

    PCI: Fix pci_device_is_present() for VFs by checking PF (CVE-2022-50636)

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

    ext4: fix bug_on in __es_tree_search caused by bad boot loader inode (CVE-2022-50638)

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

    uio: uio_dmem_genirq: Fix missing unlock in irq configuration (CVE-2022-50652)

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

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

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

    mrp: introduce active flags to prevent UAF when applicant uninit (CVE-2022-50697)

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

    md/raid1: stop mdx_raid1 thread when raid1 array run failed (CVE-2022-50715)

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

    hfs: Fix OOB Write in hfs_asc2mac (CVE-2022-50747)

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

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

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

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

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

    x86/xen: Fix memory leak in xen_init_lock_cpu() (CVE-2022-50761)

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

    tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50824)

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

    net: stream: purge sk_error_queue in sk_stream_kill_queues() (CVE-2022-50838)

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

    ext4: fix inode leak in ext4_xattr_inode_create() on an error path (CVE-2022-50845)

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

    mmc: via-sdmmc: fix return value check of mmc_add_host() (CVE-2022-50846)

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

    pstore: Avoid kcore oops by vmap()ing with VM_IOREMAP (CVE-2022-50849)

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

    scsi: ipr: Fix WARNING in ipr_init() (CVE-2022-50850)

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

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

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

    RDMA/rxe: Fix NULL-ptr-deref in rxe_qp_do_cleanup() when socket create failed (CVE-2022-50885)

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

    mmc: toshsd: fix return value check of mmc_add_host() (CVE-2022-50886)

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

    regulator: core: fix unbalanced of node refcount in regulator_dev_lookup() (CVE-2022-50887)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    nilfs2: fix general protection fault in nilfs_btree_insert() (CVE-2023-52900)

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

    usb: xhci: Check endpoint is valid before dereferencing it (CVE-2023-52901)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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

    usb: rndis_host: Secure rndis_query check against int overflow (CVE-2023-54110)

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

ID	Name	Product	Family	Type	Severity
361258	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1778266904)	Nessus	Alma Linux Local Security Checks	Local	high
359694	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Rocky Linux Local Security Checks	Local	high
359640	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Alma Linux Local Security Checks	Local	high
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
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
297384	EulerOS Virtualization 2.10.0 : kernel (EulerOS-SA-2026-1172)	Nessus	Huawei Local Security Checks	Local	high
284758	EulerOS 2.0 SP10 : kernel (EulerOS-SA-2026-1029)	Nessus	Huawei Local Security Checks	Local	high
280889	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-992840)	Nessus	Unity Linux Local Security Checks	Local	medium
280317	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992200)	Nessus	Unity Linux Local Security Checks	Local	medium
280188	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992249)	Nessus	Unity Linux Local Security Checks	Local	medium
270831	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:03614-1)	Nessus	SuSE Local Security Checks	Local	high
265594	Linux Distros Unpatched Vulnerability : CVE-2022-50365	Nessus	Misc.	Local	medium
171848	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-042 (ALASKERNEL-5.4-2023-042)	Nessus	Amazon Linux Local Security Checks	Local	high
171229	Amazon Linux 2 : kernel, --advisory ALAS2-2023-1932 (ALAS-2023-1932)	Nessus	Amazon Linux Local Security Checks	Local	high
171216	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-026 (ALASKERNEL-5.10-2023-026)	Nessus	Amazon Linux Local Security Checks	Local	high
170458	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-012 (ALASKERNEL-5.15-2023-012)	Nessus	Amazon Linux Local Security Checks	Local	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-50365

medium

Tenable Plugins

high

high

high

high

high

high

high

high

high

medium

medium

medium

high

medium

high

high

high

high

high