The version of kernel installed on the remote host is prior to 5.4.290-205.397. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2025-094 advisory.

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

    ipv6: fix possible UAF in ip6_finish_output2() (CVE-2024-44986)

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

    ipv6: avoid possible NULL deref in rt6_uncached_list_flush_dev() (CVE-2024-47707)

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

    ext4: fix slab-use-after-free in ext4_split_extent_at() (CVE-2024-49884)

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

    net/xen-netback: prevent UAF in xenvif_flush_hash() (CVE-2024-49936)

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

    ext4: fix timer use-after-free on failed mount (CVE-2024-49960)

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

    driver core: bus: Fix double free in driver API bus_register() (CVE-2024-50055)

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

    uprobe: avoid out-of-bounds memory access of fetching args (CVE-2024-50067)

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

    net: fix data-races around sk->sk_forward_alloc (CVE-2024-53124)

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

    net: sched: fix ordering of qlen adjustment (CVE-2024-53164)

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

    nilfs2: prevent use of deleted inode (CVE-2024-53690)

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

    netfilter: nft_set_hash: unaligned atomic read on struct nft_set_ext (CVE-2024-54031)

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

    Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (CVE-2024-55916)

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

    scsi: sg: Fix slab-use-after-free read in sg_release() (CVE-2024-56631)

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

    net: defer final 'struct net' free in netns dismantle (CVE-2024-56658)

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

    scsi: megaraid_sas: Fix for a potential deadlock (CVE-2024-57807)

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

    mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (CVE-2024-57884)

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

    RDMA/uverbs: Prevent integer overflow issue (CVE-2024-57890)

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

    ila: serialize calls to nf_register_net_hooks() (CVE-2024-57900)

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

    af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)

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

    af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)

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

    dm array: fix releasing a faulty array block twice in dm_array_cursor_end (CVE-2024-57929)

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

    selinux: ignore unknown extended permissions (CVE-2024-57931)

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

    net/sctp: Prevent autoclose integer overflow in sctp_association_init() (CVE-2024-57938)

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

    virtio-blk: don't keep queue frozen during system suspend (CVE-2024-57946)

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

    hrtimers: Handle CPU state correctly on hotplug (CVE-2024-57951)

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

    sctp: sysctl: auth_enable: avoid using current->nsproxy (CVE-2025-21638)

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

    sctp: sysctl: rto_min/max: avoid using current->nsproxy (CVE-2025-21639)

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

    sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy (CVE-2025-21640)

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

    net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute (CVE-2025-21653)

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

    dm thin: make get_first_thin use rcu-safe list first function (CVE-2025-21664)

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

    gtp: Destroy device along with udp socket's netns dismantle. (CVE-2025-21678)

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

    vfio/platform: check the bounds of read/write syscalls (CVE-2025-21687)

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

    USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() (CVE-2025-21689)

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

    fs/proc: fix softlockup in __read_vmcore (part 2) (CVE-2025-21694)

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

    gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (CVE-2025-21699)

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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2025-809 advisory.

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

    IORING_OP_READ did not correctly consume the provided buffer list when (CVE-2023-52926)

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

    fs/ntfs3: Fixed overflow check in mi_enum_attr() (CVE-2024-27407)

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

    btrfs: qgroup: fix qgroup prealloc rsv leak in subvolume operations (CVE-2024-35956)

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

    xfs: add bounds checking to xlog_recover_process_data (CVE-2024-41014)

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

    closures: Change BUG_ON() to WARN_ON() (CVE-2024-42252)

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

    i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock (CVE-2024-43098)

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

    i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request (CVE-2024-45828)

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

    btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() (CVE-2024-46841)

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

    mm: call the security_mmap_file() LSM hook in remap_file_pages() (CVE-2024-47745)

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

    bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again (CVE-2024-48881)

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

    bpf: Fix helper writes to read-only maps (CVE-2024-49861)

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

    rcu-tasks: Fix access non-existent percpu rtpcp variable in rcu_tasks_need_gpcb() (CVE-2024-49926)

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

    fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name (CVE-2024-49934)

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

    driver core: bus: Fix double free in driver API bus_register() (CVE-2024-50055)

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

    nfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net (CVE-2024-50121)

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

    net/mlx5e: Don't call cleanup on profile rollback failure (CVE-2024-50146)

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

    ntfs3: Add bounds checking to mi_enum_attr() (CVE-2024-50248)

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

    net: fix crash when config small gso_max_size/gso_ipv4_max_size (CVE-2024-50258)

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

    arm64/sve: Discard stale CPU state when handling SVE traps (CVE-2024-50275)

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

    igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)

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

    bpf: Check validity of link->type in bpf_link_show_fdinfo() (CVE-2024-53099)

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

    mm: page_alloc: move mlocked flag clearance into free_pages_prepare() (CVE-2024-53105)

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

    bpf: sync_linked_regs() must preserve subreg_def (CVE-2024-53125)

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

    netfilter: ipset: add missing range check in bitmap_ip_uadt (CVE-2024-53141)

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

    initramfs: avoid filename buffer overrun (CVE-2024-53142)

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

    NFSD: Prevent a potential integer overflow (CVE-2024-53146)

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

    firmware: arm_scpi: Check the DVFS OPP count returned by the firmware (CVE-2024-53157)

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

    net: sched: fix ordering of qlen adjustment (CVE-2024-53164)

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

    NFSv4.0: Fix a use-after-free problem in the asynchronous open() (CVE-2024-53173)

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

    SUNRPC: make sure cache entry active before cache_show (CVE-2024-53174)

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

    ipc: fix memleak if msg_init_ns failed in create_ipc_ns (CVE-2024-53175)

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

    PCI: Fix use-after-free of slot->bus on hot remove (CVE-2024-53194)

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

    KVM: arm64: Don't retire aborted MMIO instruction (CVE-2024-53196)

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

    xen: Fix the issue of resource not being properly released in xenbus_dev_probe() (CVE-2024-53198)

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

    tcp: Fix use-after-free of nreq in reqsk_timer_handler(). (CVE-2024-53206)

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

    s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() (CVE-2024-53210)

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

    vfio/pci: Properly hide first-in-list PCIe extended capability (CVE-2024-53214)

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

    NFSD: Prevent NULL dereference in nfsd4_process_cb_update() (CVE-2024-53217)

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

    unicode: Fix utf8_load() error path (CVE-2024-53233)

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

    xen/netfront: fix crash when removing device (CVE-2024-53240)

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

    ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)

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

    KVM: x86: Play nice with protected guests in complete_hypercall_exit() (CVE-2024-55881)

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

    Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet (CVE-2024-55916)

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

    drm/modes: Avoid divide by zero harder in drm_mode_vrefresh() (CVE-2024-56369)

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

    nfsd: make sure exp active before svc_export_show (CVE-2024-56558)

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

    i3c: master: Fix miss free init_dyn_addr at i3c_master_put_i3c_addrs() (CVE-2024-56562)

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

    iommu/arm-smmu: Defer probe of clients after smmu device bound (CVE-2024-56568)

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

    ftrace: Fix regression with module command in stack_trace_filter (CVE-2024-56569)

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

    ovl: Filter invalid inodes with missing lookup function (CVE-2024-56570)

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

    btrfs: ref-verify: fix use-after-free after invalid ref action (CVE-2024-56581)

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

    btrfs: fix use-after-free in btrfs_encoded_read_endio() (CVE-2024-56582)

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

    io_uring/tctx: work around xa_store() allocation error issue (CVE-2024-56584)

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

    leds: class: Protect brightness_show() with led_cdev->led_access mutex (CVE-2024-56587)

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

    net: inet6: do not leave a dangling sk pointer in inet6_create() (CVE-2024-56600)

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

    net: inet: do not leave a dangling sk pointer in inet_create() (CVE-2024-56601)

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

    net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)

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

    af_packet: avoid erroring out after sock_init_data() in packet_create() (CVE-2024-56606)

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

    kcsan: Turn report_filterlist_lock into a raw_spinlock (CVE-2024-56610)

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

    xsk: fix OOB map writes when deleting elements (CVE-2024-56614)

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

    bpf: fix OOB devmap writes when deleting elements (CVE-2024-56615)

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

    drm/dp_mst: Fix MST sideband message body length check (CVE-2024-56616)

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

    can: dev: can_set_termination(): allow sleeping GPIOs (CVE-2024-56625)

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

    tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg (CVE-2024-56633)

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

    gpio: grgpio: Add NULL check in grgpio_probe (CVE-2024-56634)

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

    geneve: do not assume mac header is set in geneve_xmit_skb() (CVE-2024-56636)

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

    netfilter: ipset: Hold module reference while requesting a module (CVE-2024-56637)

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

    tipc: Fix use-after-free of kernel socket in cleanup_bearer(). (CVE-2024-56642)

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

    net/ipv6: release expired exception dst cached in socket (CVE-2024-56644)

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

    can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)

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

    net: hsr: avoid potential out-of-bound access in fill_frame_info() (CVE-2024-56648)

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

    net: defer final 'struct net' free in netns dismantle (CVE-2024-56658)

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

    net/mlx5: DR, prevent potential error pointer dereference (CVE-2024-56660)

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

    bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog (CVE-2024-56665)

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

    blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)

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

    bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)

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

    usb: musb: Fix hardware lockup on first Rx endpoint request (CVE-2024-56687)

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

    sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport (CVE-2024-56688)

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

    crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)

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

    brd: defer automatic disk creation until module initialization succeeds (CVE-2024-56693)

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

    bpf: fix recursive lock when verdict program return SK_PASS (CVE-2024-56694)

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

    io_uring: check if iowq is killed before queuing (CVE-2024-56709)

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

    netdevsim: prevent bad user input in nsim_dev_health_break_write() (CVE-2024-56716)

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

    bpf, sockmap: Several fixes to bpf_msg_pop_data (CVE-2024-56720)

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

    rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)

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

    PCI: Fix reset_method_store() memory leak (CVE-2024-56745)

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

    ipv6: release nexthop on device removal

    The CI is hitting some aperiodic hangup at device removal time in thepmtu.sh self-test:

    unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6ref_tracker:
    veth_A-R1@ffff888013df15d8 has 1/5 users atdst_init+0x84/0x4a0dst_alloc+0x97/0x150ip6_dst_alloc+0x23/0x90i     p6_rt_pcpu_alloc+0x1e6/0x520ip6_pol_route+0x56f/0x840fib6_rule_lookup+0x334/0x630ip6_route_output_flags+0x     259/0x480ip6_dst_lookup_tail.constprop.0+0x5c2/0x940ip6_dst_lookup_flow+0x88/0x190udp_tunnel6_dst_lookup+0     x2a7/0x4c0vxlan_xmit_one+0xbde/0x4a50 [vxlan]vxlan_xmit+0x9ad/0xf20 [vxlan]dev_hard_start_xmit+0x10e/0x360
    __dev_queue_xmit+0xf95/0x18c0arp_solicit+0x4a2/0xe00neigh_probe+0xaa/0xf0

    While the first suspect is the dst_cache, explicitly tracking the dstowing the last device reference via     probes proved such dst is held bythe nexthop in the originating fib6_info.

    Similar to commit f5b51fe804ec (ipv6: route: purge exception onremoval), we need to explicitly release     the originating fib info whendisconnecting a to-be-removed device from a live ipv6 dst: move thefib6_info     cleanup into ip6_dst_ifdown().

    Tested running:

    ./pmtu.sh cleanup_ipv6_exception

    in a tight loop for more than 400 iterations with no spat, running anunpatched kernel  I observed a splat     every ~10 iterations. (CVE-2024-56751)

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

    netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING (CVE-2024-56755)

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

    nvme-pci: fix freeing of the HMB descriptor table (CVE-2024-56756)

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

    btrfs: fix use-after-free when COWing tree bock and tracing is enabled (CVE-2024-56759)

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

    tracing: Prevent bad count for tracing_cpumask_write (CVE-2024-56763)

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

    net/sched: netem: account for backlog updates from child qdisc (CVE-2024-56770)

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

    btrfs: add a sanity check for btrfs root in btrfs_search_slot() (CVE-2024-56774)

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

    nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur (CVE-2024-56779)

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

    quota: flush quota_release_work upon quota writeback (CVE-2024-56780)

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

    netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level (CVE-2024-56783)

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

    drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() (CVE-2024-57798)

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

    net: fix memory leak in tcp_conn_request() (CVE-2024-57841)

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

    arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL (CVE-2024-57874)

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

    drm/dp_mst: Fix resetting msg rx state after topology removal (CVE-2024-57876)

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

    mptcp: fix TCP options overflow. (CVE-2024-57882)

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

    mm: vmscan: account for free pages to prevent infinite Loop in throttle_direct_reclaim() (CVE-2024-57884)

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

    RDMA/uverbs: Prevent integer overflow issue (CVE-2024-57890)

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

    btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount (CVE-2024-57896)

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

    ila: serialize calls to nf_register_net_hooks() (CVE-2024-57900)

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

    af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)

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

    af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)

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

    net: restrict SO_REUSEPORT to inet sockets (CVE-2024-57903)

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

    selinux: ignore unknown extended permissions (CVE-2024-57931)

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

    net/sctp: Prevent autoclose integer overflow in sctp_association_init() (CVE-2024-57938)

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

    virtio-blk: don't keep queue frozen during system suspend (CVE-2024-57946)

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

    net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets (CVE-2025-21629)

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.

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

    Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free     vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly     execute arbitrary code. (CVE-2024-23848)

    Attila Szsz discovered that the HFS+ file system implementation in the Linux Kernel contained a heap     overflow vulnerability. An attacker could use a specially crafted file system image that, when mounted,     could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2025-0927)

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

    - PowerPC architecture;

    - S390 architecture;

    - SuperH RISC architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Cryptographic API;

    - Virtio block driver;

    - Data acquisition framework and drivers;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - EDAC drivers;

    - ARM SCPI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Microsoft Hyper-V drivers;

    - I3C subsystem;

    - IIO ADC drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - MMC subsystem;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - NVME drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SuperH / SH-Mobile drivers;

    - QCOM SoC drivers;

    - SPI subsystem;

    - USB Gadget drivers;

    - USB Serial drivers;

    - USB Type-C Port Controller Manager driver;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - Timer subsystem;

    - VLANs driver;

    - LAPB network protocol;

    - Network namespace;

    - Kernel init infrastructure;

    - BPF subsystem;

    - Kernel CPU control infrastructure;

    - Tracing infrastructure;

    - Memory management;

    - 9P file system network protocol;

    - Bluetooth subsystem;

    - CAN network layer;

    - Networking core;

    - DCCP (Datagram Congestion Control Protocol);

    - IEEE802154.4 network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Netlink;

    - NET/ROM layer;

    - Packet sockets;

    - Network traffic control;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - eXpress Data Path;

    - SELinux security module;

    - USB sound devices; (CVE-2024-56586, CVE-2024-52332, CVE-2024-56570, CVE-2024-49936, CVE-2024-56595,     CVE-2024-56769, CVE-2025-21653, CVE-2024-56781, CVE-2024-49996, CVE-2024-26915, CVE-2024-56574,     CVE-2024-57929, CVE-2024-57807, CVE-2025-21700, CVE-2024-53121, CVE-2024-56633, CVE-2024-56631,     CVE-2024-56600, CVE-2024-53150, CVE-2024-56614, CVE-2024-53131, CVE-2024-57938, CVE-2024-53171,     CVE-2024-53157, CVE-2024-56572, CVE-2024-53165, CVE-2024-53198, CVE-2024-57850, CVE-2024-57922,     CVE-2022-49034, CVE-2024-57910, CVE-2024-57912, CVE-2024-56645, CVE-2025-21638, CVE-2024-57902,     CVE-2024-56691, CVE-2024-56681, CVE-2024-53181, CVE-2024-46826, CVE-2024-55916, CVE-2024-56767,     CVE-2025-21639, CVE-2024-56659, CVE-2024-53183, CVE-2024-56723, CVE-2024-56644, CVE-2024-56779,     CVE-2024-57913, CVE-2024-53145, CVE-2024-53135, CVE-2024-35864, CVE-2024-56651, CVE-2024-38588,     CVE-2024-53140, CVE-2024-56605, CVE-2024-57890, CVE-2024-53172, CVE-2024-56724, CVE-2024-56602,     CVE-2024-56629, CVE-2024-57911, CVE-2024-57931, CVE-2024-53174, CVE-2024-44938, CVE-2024-57906,     CVE-2024-53161, CVE-2021-47219, CVE-2024-53138, CVE-2024-56634, CVE-2024-53214, CVE-2024-56670,     CVE-2025-21702, CVE-2024-56562, CVE-2024-43098, CVE-2024-26928, CVE-2024-56581, CVE-2024-56694,     CVE-2024-57901, CVE-2024-56532, CVE-2024-48881, CVE-2024-53237, CVE-2021-47119, CVE-2024-57904,     CVE-2024-49884, CVE-2024-56606, CVE-2024-57946, CVE-2024-56650, CVE-2024-56594, CVE-2025-21699,     CVE-2024-56597, CVE-2024-56704, CVE-2024-56615, CVE-2024-56598, CVE-2024-53227, CVE-2024-56531,     CVE-2024-56700, CVE-2024-56688, CVE-2024-53148, CVE-2025-21640, CVE-2024-56643, CVE-2024-53690,     CVE-2024-50256, CVE-2024-56593, CVE-2024-35958, CVE-2024-53112, CVE-2024-53239, CVE-2024-56603,     CVE-2024-53217, CVE-2024-56567, CVE-2024-56637, CVE-2024-53680, CVE-2024-53194, CVE-2024-43900,     CVE-2024-57892, CVE-2024-56780, CVE-2024-57849, CVE-2024-53156, CVE-2024-57889, CVE-2024-53130,     CVE-2024-56690, CVE-2024-53173, CVE-2024-56601, CVE-2024-56770, CVE-2024-57951, CVE-2024-56756,     CVE-2024-53197, CVE-2024-56539, CVE-2024-56558, CVE-2024-47707, CVE-2025-21689, CVE-2024-56642,     CVE-2024-56658, CVE-2024-56619, CVE-2024-50051, CVE-2024-53146, CVE-2024-56720, CVE-2025-21664,     CVE-2024-57884, CVE-2024-56569, CVE-2024-49925, CVE-2024-56746, CVE-2024-53142, CVE-2024-56596,     CVE-2024-56587, CVE-2024-57802, CVE-2024-53158, CVE-2025-21678, CVE-2024-57908, CVE-2024-53127,     CVE-2024-53136, CVE-2025-21694, CVE-2024-53124, CVE-2024-49974, CVE-2024-56747, CVE-2024-57948,     CVE-2025-21687, CVE-2024-53155, CVE-2024-56548, CVE-2024-53184, CVE-2024-56630, CVE-2024-56748,     CVE-2024-56576, CVE-2025-21697, CVE-2024-56739, CVE-2024-57900)

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

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

The version of kernel installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-55916 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: util: Avoid accessing a     ringbuffer not initialized yet If the KVP (or VSS) daemon starts before the VMBus channel's ringbuffer is     fully initialized, we can hit the panic below: hv_utils: Registering HyperV Utility Driver hv_vmbus:
    registering driver hv_utils ... BUG: kernel NULL pointer dereference, address: 0000000000000000 CPU: 44     UID: 0 PID: 2552 Comm: hv_kvp_daemon Tainted: G E 6.11.0-rc3+ #1 RIP: 0010:hv_pkt_iter_first+0x12/0xd0     Call Trace: ... vmbus_recvpacket hv_kvp_onchannelcallback vmbus_on_event tasklet_action_common     tasklet_action handle_softirqs irq_exit_rcu sysvec_hyperv_stimer0 </IRQ> <TASK> asm_sysvec_hyperv_stimer0     ... kvp_register_done hvt_op_read vfs_read ksys_read __x64_sys_read This can happen because the KVP/VSS     channel callback can be invoked even before the channel is fully opened: 1) as soon as hv_kvp_init() ->     hvutil_transport_init() creates /dev/vmbus/hv_kvp, the kvp daemon can open the device file immediately and     register itself to the driver by writing a message KVP_OP_REGISTER1 to the file (which is handled by     kvp_on_msg() ->kvp_handle_handshake()) and reading the file for the driver's response, which is handled by     hvt_op_read(), which calls hvt->on_read(), i.e. kvp_register_done(). 2) the problem with     kvp_register_done() is that it can cause the channel callback to be called even before the channel is     fully opened, and when the channel callback is starting to run, util_probe()-> vmbus_open() May have not     initialized the ringbuffer yet, so the callback can hit the panic of NULL pointer dereference. To     reproduce the panic consistently, we can add a ssleep(10) for KVP in __vmbus_open(), just before the     first hv_ringbuffer_init(), and then we unload and reload the driver hv_utils, and run the daemon manually     within the 10 seconds. Fix the panic by reordering the steps in util_probe() so the char dev entry used by     the KVP or VSS daemon is not created until after vmbus_open() has completed. This reordering prevents the     race condition from happening. (CVE-2024-55916)

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

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


    The following security bugs were fixed:

    - CVE-2024-36898: gpiolib: cdev: fix uninitialised kfifo (bsc#1225736).
    - CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).
    - CVE-2024-50142: xfrm: validate new SA's prefixlen using SA family when sel.family is unset     (bsc#1233028).
    - CVE-2024-50151: smb: client: fix OOBs when building SMB2_IOCTL request (bsc#1233055).
    - CVE-2024-50199: mm/swapfile: skip HugeTLB pages for unuse_vma (bsc#1233112).
    - CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb() (bsc#1233488).
    - CVE-2024-53104: media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_format     (bsc#1234025).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-53166: block, bfq: fix bfqq uaf in bfq_limit_depth() (bsc#1234884).
    - CVE-2024-53177: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896).
    - CVE-2024-53209: bnxt_en: Fix receive ring space parameters when XDP is active (bsc#1235002).
    - CVE-2024-53227: scsi: bfa: Fix use-after-free in bfad_im_module_exit() (bsc#1235011).
    - CVE-2024-56588: scsi: hisi_sas: Create all dump files during debugfs initialization (bsc#1235123).
    - CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create() (bsc#1235217).
    - CVE-2024-56601: net: inet: do not leave a dangling sk pointer in inet_create() (bsc#1235230).
    - CVE-2024-56602: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create()     (bsc#1235521).
    - CVE-2024-56623: scsi: qla2xxx: Fix use after free on unload (bsc#1235466).
    - CVE-2024-56631: scsi: sg: Fix slab-use-after-free read in sg_release() (bsc#1235480).
    - CVE-2024-56642: tipc: Fix use-after-free of kernel socket in cleanup_bearer() (bsc#1235433).
    - CVE-2024-56645: can: j1939: j1939_session_new(): fix skb reference counting (bsc#1235134).
    - CVE-2024-56648: net: hsr: avoid potential out-of-bound access in fill_frame_info() (bsc#1235451).
    - CVE-2024-56650: netfilter: x_tables: fix LED ID check in led_tg_check() (bsc#1235430).
    - CVE-2024-56658: net: defer final 'struct net' free in netns dismantle (bsc#1235441).
    - CVE-2024-56664: bpf, sockmap: Fix race between element replace and close() (bsc#1235249).
    - CVE-2024-56704: 9p/xen: fix release of IRQ (bsc#1235584).
    - CVE-2024-56747: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() (bsc#1234934).
    - CVE-2024-56759: btrfs: fix use-after-free when COWing tree bock and tracing is enabled (bsc#1235645).
    - CVE-2024-57791: net/smc: check return value of sock_recvmsg when draining clc data (bsc#1235759).
    - CVE-2024-57792: power: supply: gpio-charger: Fix set charge current limits (bsc#1235764).
    - CVE-2024-57793: virt: tdx-guest: Just leak decrypted memory on unrecoverable errors (bsc#1235768).
    - CVE-2024-57798: drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req()     (bsc#1235818).
    - CVE-2024-57849: s390/cpum_sf: Handle CPU hotplug remove during sampling (bsc#1235814).
    - CVE-2024-57876: drm/dp_mst: Fix resetting msg rx state after topology removal (bsc#1235806).
    - CVE-2024-57893: ALSA: seq: oss: Fix races at processing SysEx messages (bsc#1235920).
    - CVE-2024-57897: drm/amdkfd: Correct the migration DMA map direction (bsc#1235969).


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

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

    Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet

    If the KVP (or VSS) daemon starts before the VMBus channel's ringbuffer is     fully initialized, we can hit the panic below:

    hv_utils: Registering HyperV Utility Driver     hv_vmbus: registering driver hv_utils     ...
    BUG: kernel NULL pointer dereference, address: 0000000000000000     CPU: 44 UID: 0 PID: 2552 Comm: hv_kvp_daemon Tainted: G E 6.11.0-rc3+ #1     RIP: 0010:hv_pkt_iter_first+0x12/0xd0     Call Trace:
    ...
     vmbus_recvpacket      hv_kvp_onchannelcallback      vmbus_on_event      tasklet_action_common      tasklet_action      handle_softirqs      irq_exit_rcu      sysvec_hyperv_stimer0      </IRQ>      <TASK>      asm_sysvec_hyperv_stimer0     ...
     kvp_register_done      hvt_op_read      vfs_read      ksys_read
     __x64_sys_read

    This can happen because the KVP/VSS channel callback can be invoked     even before the channel is fully opened:
    1) as soon as hv_kvp_init() -> hvutil_transport_init() creates     /dev/vmbus/hv_kvp, the kvp daemon can open the device file immediately and     register itself to the driver by writing a message KVP_OP_REGISTER1 to the     file (which is handled by kvp_on_msg() ->kvp_handle_handshake()) and     reading the file for the driver's response, which is handled by     hvt_op_read(), which calls hvt->on_read(), i.e. kvp_register_done().

    2) the problem with kvp_register_done() is that it can cause the     channel callback to be called even before the channel is fully opened,     and when the channel callback is starting to run, util_probe()->     vmbus_open() may have not initialized the ringbuffer yet, so the     callback can hit the panic of NULL pointer dereference.

    To reproduce the panic consistently, we can add a ssleep(10) for KVP in
    __vmbus_open(), just before the first hv_ringbuffer_init(), and then we     unload and reload the driver hv_utils, and run the daemon manually within     the 10 seconds.

    Fix the panic by reordering the steps in util_probe() so the char dev     entry used by the KVP or VSS daemon is not created until after     vmbus_open() has completed. This reordering prevents the race condition     from happening.

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 Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7523-1 advisory.

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

    - ARM64 architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - SuperH RISC architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - RAM backed block device driver;

    - Ublk userspace block driver;

    - Virtio block driver;

    - Compressed RAM block device driver;

    - Bluetooth drivers;

    - TPM device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - DAX dirext access to differentiated memory framework;

    - DMA engine subsystem;

    - EDAC drivers;

    - ARM SCMI message protocol;

    - ARM SCPI message protocol;

    - EFI core;

    - iSCSI Boot Firmware Table Attributes driver;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Microsoft Hyper-V drivers;

    - Hardware monitoring drivers;

    - I3C subsystem;

    - IIO ADC drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - Microchip PCI driver;

    - MMC subsystem;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - NTB driver;

    - Virtio pmem driver;

    - NVME drivers;

    - Parport drivers;

    - PCI subsystem;

    - PHY drivers;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - i.MX PM domains;

    - Power supply drivers;

    - Voltage and Current Regulator drivers;

    - StarFive reset controller drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SuperH / SH-Mobile drivers;

    - i.MX SoC drivers;

    - QCOM SoC drivers;

    - Xilinx SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Media staging drivers;

    - TCM subsystem;

    - Thermal drivers;

    - TTY drivers;

    - UFS subsystem;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Dual Role (OTG-ready) Controller drivers;

    - USB Serial drivers;

    - USB Type-C support driver;

    - USB Type-C Port Controller Manager driver;

    - TI TPS6598x USB Power Delivery controller driver;

    - USB Type-C Connector System Software Interface driver;

    - vDPA drivers;

    - VFIO drivers;

    - Framebuffer layer;

    - TDX Guest driver;

    - Xen hypervisor drivers;

    - AFS file system;

    - BTRFS file system;

    - File systems infrastructure;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - JFFS2 file system;

    - JFS file system;

    - Network file systems library;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - NTFS3 file system;

    - Overlay file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - DRM display driver;

    - BPF subsystem;

    - VLANs driver;

    - Kernel Samepage Merging mechanism;

    - Memory management;

    - Network file system (NFS) superblock;

    - Kernel stack handling interfaces;

    - StackDepot library;

    - Task handling mechanism;

    - userfaultfd() syscall;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - LAPB network protocol;

    - Network namespace;

    - Netfilter;

    - Network traffic control;

    - Network sockets;

    - Tracing infrastructure;

    - User-space API (UAPI);

    - Kernel init infrastructure;

    - io_uring subsystem;

    - IPC subsystem;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Kernel fork() syscall;

    - KCSAN framework;

    - Kernel thread helper (kthread);

    - RCU subsystem;

    - Arbitrary resource management;

    - Scheduler infrastructure;

    - Signal handling mechanism;

    - Timer subsystem;

    - Workqueue subsystem;

    - Vector I/O iterator library;

    - KUnit library;

    - Maple Tree data structure library;

    - 9P file system network protocol;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - DCCP (Datagram Congestion Control Protocol);

    - Ethtool driver;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netlink;

    - NET/ROM layer;

    - Packet sockets;

    - RDS protocol;

    - RxRPC session sockets;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - Key management;

    - SELinux security module;

    - ALSA framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - MediaTek ASoC drivers;

    - QCOM ASoC drivers;

    - SoC audio core drivers;

    - STMicroelectronics SoC drivers;

    - USB sound devices; (CVE-2024-56566, CVE-2024-56631, CVE-2025-21756, CVE-2024-57841, CVE-2024-50270,     CVE-2024-50104, CVE-2024-50143, CVE-2024-56756, CVE-2024-50295, CVE-2024-48873, CVE-2024-53229,     CVE-2024-50051, CVE-2024-50125, CVE-2024-56761, CVE-2024-50223, CVE-2024-53687, CVE-2024-53094,     CVE-2024-53131, CVE-2024-57933, CVE-2024-57884, CVE-2024-57917, CVE-2024-53210, CVE-2024-50245,     CVE-2024-56679, CVE-2024-50258, CVE-2024-57902, CVE-2024-50236, CVE-2024-56607, CVE-2024-50209,     CVE-2024-50184, CVE-2024-50127, CVE-2024-50010, CVE-2024-50185, CVE-2024-57900, CVE-2024-56739,     CVE-2024-56643, CVE-2024-56675, CVE-2024-56689, CVE-2024-50135, CVE-2024-56688, CVE-2024-50153,     CVE-2025-21635, CVE-2025-21632, CVE-2024-50072, CVE-2025-21646, CVE-2024-56727, CVE-2024-53058,     CVE-2024-53107, CVE-2024-53166, CVE-2024-50019, CVE-2024-50242, CVE-2024-56755, CVE-2024-50301,     CVE-2024-57801, CVE-2024-56716, CVE-2024-50023, CVE-2024-50288, CVE-2024-50078, CVE-2024-56572,     CVE-2024-53158, CVE-2024-50075, CVE-2024-57912, CVE-2024-56759, CVE-2024-53155, CVE-2024-56584,     CVE-2024-56672, CVE-2024-56590, CVE-2024-56658, CVE-2024-50235, CVE-2024-53160, CVE-2024-56622,     CVE-2024-50130, CVE-2024-50265, CVE-2024-56579, CVE-2024-50292, CVE-2024-56728, CVE-2024-56543,     CVE-2024-56722, CVE-2024-53197, CVE-2025-21645, CVE-2024-50138, CVE-2024-45828, CVE-2024-50208,     CVE-2024-56724, CVE-2024-50304, CVE-2024-50195, CVE-2024-49571, CVE-2024-50263, CVE-2024-55881,     CVE-2024-50220, CVE-2024-50044, CVE-2024-53237, CVE-2024-50278, CVE-2024-56557, CVE-2024-50068,     CVE-2024-56574, CVE-2024-50180, CVE-2024-50065, CVE-2025-21642, CVE-2024-56565, CVE-2024-50189,     CVE-2024-53228, CVE-2024-56752, CVE-2024-50169, CVE-2024-53198, CVE-2024-56532, CVE-2025-21659,     CVE-2024-53223, CVE-2024-50084, CVE-2024-56582, CVE-2024-56632, CVE-2024-56709, CVE-2024-50134,     CVE-2024-57945, CVE-2024-56546, CVE-2024-50056, CVE-2024-53059, CVE-2024-53171, CVE-2024-50080,     CVE-2024-49899, CVE-2024-50090, CVE-2024-53184, CVE-2024-50131, CVE-2024-57926, CVE-2024-50225,     CVE-2024-47809, CVE-2024-53180, CVE-2024-56372, CVE-2024-50137, CVE-2024-50192, CVE-2024-56642,     CVE-2025-21637, CVE-2024-53219, CVE-2024-56650, CVE-2024-53090, CVE-2024-53148, CVE-2024-56785,     CVE-2024-50230, CVE-2024-50275, CVE-2024-47141, CVE-2024-50022, CVE-2024-53142, CVE-2024-50059,     CVE-2024-56765, CVE-2024-53046, CVE-2024-58087, CVE-2025-21664, CVE-2025-21658, CVE-2024-56569,     CVE-2024-50110, CVE-2024-53161, CVE-2024-53150, CVE-2024-53140, CVE-2024-50069, CVE-2024-56594,     CVE-2024-53181, CVE-2024-53178, CVE-2024-56652, CVE-2024-56708, CVE-2024-53174, CVE-2024-53072,     CVE-2024-50290, CVE-2024-53162, CVE-2024-50029, CVE-2024-53179, CVE-2024-53079, CVE-2024-57906,     CVE-2024-50035, CVE-2024-50224, CVE-2025-21649, CVE-2024-50163, CVE-2024-57882, CVE-2024-50024,     CVE-2024-56550, CVE-2024-53690, CVE-2024-50203, CVE-2024-53195, CVE-2024-50118, CVE-2024-53175,     CVE-2024-57908, CVE-2025-21701, CVE-2024-47736, CVE-2024-53067, CVE-2024-53200, CVE-2024-50032,     CVE-2024-50282, CVE-2024-50162, CVE-2024-53118, CVE-2024-56636, CVE-2024-56629, CVE-2024-50030,     CVE-2024-56595, CVE-2024-56601, CVE-2024-57904, CVE-2024-53115, CVE-2024-50077, CVE-2024-56654,     CVE-2024-50199, CVE-2024-56782, CVE-2024-50151, CVE-2024-50182, CVE-2024-53052, CVE-2024-53151,     CVE-2024-57938, CVE-2024-53084, CVE-2024-50296, CVE-2024-53217, CVE-2024-57892, CVE-2024-50287,     CVE-2024-53110, CVE-2024-56763, CVE-2024-50027, CVE-2024-50261, CVE-2024-50112, CVE-2024-56533,     CVE-2024-56704, CVE-2024-47726, CVE-2024-50238, CVE-2024-57876, CVE-2024-50207, CVE-2024-50116,     CVE-2024-50155, CVE-2024-53086, CVE-2024-50291, CVE-2025-21631, CVE-2024-56538, CVE-2024-56720,     CVE-2024-53123, CVE-2024-58099, CVE-2024-56597, CVE-2024-53168, CVE-2024-57879, CVE-2022-49034,     CVE-2024-56549, CVE-2024-41014, CVE-2024-53091, CVE-2024-56677, CVE-2024-53156, CVE-2024-50158,     CVE-2024-50251, CVE-2024-56641, CVE-2024-56718, CVE-2024-57901, CVE-2024-56606, CVE-2024-50268,     CVE-2024-48875, CVE-2024-50167, CVE-2024-50028, CVE-2024-50256, CVE-2024-50283, CVE-2024-53133,     CVE-2024-50302, CVE-2024-56721, CVE-2024-53177, CVE-2024-57798, CVE-2024-53126, CVE-2024-56638,     CVE-2024-50285, CVE-2024-53076, CVE-2024-53146, CVE-2024-56698, CVE-2025-21700, CVE-2024-56619,     CVE-2024-50115, CVE-2024-53190, CVE-2024-54460, CVE-2024-50073, CVE-2024-56771, CVE-2024-56637,     CVE-2024-50061, CVE-2024-55639, CVE-2024-56651, CVE-2024-50064, CVE-2024-53044, CVE-2024-53096,     CVE-2024-56613, CVE-2024-56769, CVE-2024-57910, CVE-2024-41013, CVE-2024-50186, CVE-2024-50159,     CVE-2024-56600, CVE-2024-56787, CVE-2024-57929, CVE-2024-56640, CVE-2025-21662, CVE-2024-53099,     CVE-2024-56570, CVE-2024-53100, CVE-2024-50101, CVE-2024-50160, CVE-2024-50273, CVE-2024-47711,     CVE-2024-50191, CVE-2024-56786, CVE-2024-50107, CVE-2024-53236, CVE-2024-56548, CVE-2024-56562,     CVE-2024-50229, CVE-2024-56647, CVE-2024-53139, CVE-2024-48876, CVE-2024-57872, CVE-2024-53063,     CVE-2024-53226, CVE-2024-56758, CVE-2024-50086, CVE-2024-53209, CVE-2024-50096, CVE-2024-56660,     CVE-2024-57893, CVE-2024-53083, CVE-2024-57916, CVE-2024-50205, CVE-2024-50200, CVE-2024-53108,     CVE-2024-50033, CVE-2024-50276, CVE-2024-56621, CVE-2024-56725, CVE-2024-56558, CVE-2024-57931,     CVE-2024-50145, CVE-2024-56616, CVE-2024-53685, CVE-2024-53129, CVE-2025-21650, CVE-2025-21654,     CVE-2024-50171, CVE-2024-56599, CVE-2024-50046, CVE-2024-56701, CVE-2024-47408, CVE-2025-21636,     CVE-2024-50231, CVE-2024-50152, CVE-2024-50206, CVE-2024-50009, CVE-2024-53130, CVE-2024-57793,     CVE-2024-57791, CVE-2024-50262, CVE-2024-56586, CVE-2024-57895, CVE-2024-57899, CVE-2024-56608,     CVE-2024-50197, CVE-2024-56774, CVE-2024-53224, CVE-2024-53231, CVE-2024-50237, CVE-2024-50139,     CVE-2024-50222, CVE-2024-50039, CVE-2024-53101, CVE-2024-56776, CVE-2024-56625, CVE-2024-53188,     CVE-2024-50269, CVE-2024-50055, CVE-2024-50216, CVE-2024-56615, CVE-2024-56648, CVE-2024-50048,     CVE-2024-57925, CVE-2024-50193, CVE-2024-56754, CVE-2025-21647, CVE-2024-50105, CVE-2024-49893,     CVE-2024-53128, CVE-2024-49568, CVE-2024-56539, CVE-2024-50117, CVE-2024-53081, CVE-2024-50148,     CVE-2024-56685, CVE-2024-50226, CVE-2024-56576, CVE-2024-56627, CVE-2024-50289, CVE-2025-21653,     CVE-2024-53082, CVE-2024-56581, CVE-2024-53227, CVE-2024-56691, CVE-2024-56780, CVE-2024-50095,     CVE-2024-50136, CVE-2024-50201, CVE-2024-55916, CVE-2024-56583, CVE-2024-53135, CVE-2024-53106,     CVE-2024-57887, CVE-2024-57792, CVE-2024-48881, CVE-2024-56645, CVE-2024-53157, CVE-2024-53045,     CVE-2024-53170, CVE-2024-50082, CVE-2024-56531, CVE-2024-53183, CVE-2024-53191, CVE-2024-53163,     CVE-2025-21656, CVE-2024-50274, CVE-2025-21639, CVE-2025-21663, CVE-2024-50183, CVE-2024-50020,     CVE-2024-56568, CVE-2024-56781, CVE-2024-50057, CVE-2024-56681, CVE-2024-50299, CVE-2024-53233,     CVE-2024-53121, CVE-2024-53214, CVE-2024-56700, CVE-2024-50247, CVE-2024-56778, CVE-2024-50067,     CVE-2024-56662, CVE-2024-56635, CVE-2024-53112, CVE-2024-56729, CVE-2024-56589, CVE-2024-53093,     CVE-2024-50248, CVE-2024-53220, CVE-2025-21971, CVE-2024-52332, CVE-2024-38608, CVE-2024-50062,     CVE-2024-53218, CVE-2024-56630, CVE-2024-49569, CVE-2024-56745, CVE-2024-56715, CVE-2024-56633,     CVE-2024-53208, CVE-2024-56770, CVE-2024-50154, CVE-2024-56705, CVE-2024-50120, CVE-2024-57939,     CVE-2024-57843, CVE-2024-56609, CVE-2024-56772, CVE-2024-50211, CVE-2024-57804, CVE-2024-57889,     CVE-2024-56603, CVE-2024-53087, CVE-2024-53125, CVE-2024-53061, CVE-2025-21652, CVE-2024-50255,     CVE-2024-56690, CVE-2025-21702, CVE-2024-53169, CVE-2024-50240, CVE-2024-56683, CVE-2024-49972,     CVE-2025-21655, CVE-2024-57874, CVE-2024-53120, CVE-2024-57907, CVE-2024-56626, CVE-2024-56726,     CVE-2024-56773, CVE-2024-49914, CVE-2024-42122, CVE-2024-53194, CVE-2024-49920, CVE-2024-56545,     CVE-2024-56575, CVE-2024-56775, CVE-2024-53134, CVE-2024-56717, CVE-2024-53105, CVE-2024-57897,     CVE-2024-50124, CVE-2024-50239, CVE-2024-50036, CVE-2024-50234, CVE-2025-21651, CVE-2024-56767,     CVE-2024-53165, CVE-2024-53680, CVE-2024-41935, CVE-2024-50150, CVE-2024-53043, CVE-2024-56659,     CVE-2024-50243, CVE-2024-56567, CVE-2024-50141, CVE-2024-50049, CVE-2024-53222, CVE-2024-53122,     CVE-2024-50257, CVE-2024-50147, CVE-2024-53176, CVE-2024-53234, CVE-2024-53187, CVE-2024-50280,     CVE-2024-50140, CVE-2024-57911, CVE-2024-50060, CVE-2024-56598, CVE-2024-50246, CVE-2024-53047,     CVE-2024-56577, CVE-2024-57802, CVE-2024-53050, CVE-2024-50088, CVE-2024-56751, CVE-2024-56611,     CVE-2024-53068, CVE-2025-21643, CVE-2024-50038, CVE-2024-36476, CVE-2024-56707, CVE-2024-50040,     CVE-2024-53088, CVE-2024-50284, CVE-2024-53127, CVE-2024-50298, CVE-2024-56593, CVE-2024-57898,     CVE-2024-57903, CVE-2024-56703, CVE-2024-56746, CVE-2024-56663, CVE-2024-53138, CVE-2024-56744,     CVE-2024-50042, CVE-2024-57940, CVE-2024-56747, CVE-2024-56623, CVE-2024-56777, CVE-2024-41932,     CVE-2024-47143, CVE-2024-50098, CVE-2024-53147, CVE-2024-53173, CVE-2024-50249, CVE-2024-49921,     CVE-2024-56783, CVE-2024-50294, CVE-2024-53062, CVE-2024-57946, CVE-2024-56710, CVE-2025-21640,     CVE-2024-53042, CVE-2024-56649, CVE-2024-50233, CVE-2024-50121, CVE-2024-53051, CVE-2024-57932,     CVE-2025-21634, CVE-2024-56580, CVE-2024-56687, CVE-2024-53239, CVE-2024-56634, CVE-2024-56653,     CVE-2024-53196, CVE-2024-56596, CVE-2024-50133, CVE-2024-50142, CVE-2024-50045, CVE-2024-53119,     CVE-2024-56694, CVE-2024-50188, CVE-2024-50218, CVE-2024-50259, CVE-2024-56605, CVE-2024-53232,     CVE-2024-57885, CVE-2024-50198, CVE-2024-56764, CVE-2025-21648, CVE-2024-50108, CVE-2024-56644,     CVE-2024-50156, CVE-2024-53215, CVE-2024-50221, CVE-2024-56678, CVE-2024-50103, CVE-2024-53230,     CVE-2024-50047, CVE-2024-50202, CVE-2024-56588, CVE-2024-53117, CVE-2024-53048, CVE-2025-21660,     CVE-2024-53154, CVE-2024-50187, CVE-2024-50066, CVE-2024-50170, CVE-2024-56667, CVE-2024-56540,     CVE-2024-53113, CVE-2024-44955, CVE-2024-53172, CVE-2024-49865, CVE-2024-56604, CVE-2025-21638,     CVE-2024-50093, CVE-2024-50128, CVE-2024-50279, CVE-2024-50286, CVE-2024-50083, CVE-2024-56657,     CVE-2024-53085, CVE-2024-50303, CVE-2024-57838, CVE-2024-56551, CVE-2024-54193, CVE-2024-57888,     CVE-2024-50070, CVE-2024-50172, CVE-2024-57890, CVE-2024-56578, CVE-2025-21938, CVE-2024-53066,     CVE-2024-54683, CVE-2024-50196, CVE-2024-49968, CVE-2024-56692, CVE-2024-50074, CVE-2024-53053,     CVE-2024-50031, CVE-2024-54455, CVE-2024-57807, CVE-2024-56742, CVE-2024-57883, CVE-2024-50099,     CVE-2024-50025, CVE-2024-57850, CVE-2024-57896, CVE-2024-56587, CVE-2024-50087, CVE-2024-57806,     CVE-2024-53203, CVE-2024-50272, CVE-2024-50300, CVE-2024-50058, CVE-2024-50232, CVE-2024-50111,     CVE-2024-50063, CVE-2024-50297, CVE-2024-50252, CVE-2024-53221, CVE-2024-50250, CVE-2024-50146,     CVE-2024-53114, CVE-2024-50215, CVE-2024-50244, CVE-2024-56369, CVE-2024-53055, CVE-2024-49906,     CVE-2024-43098, CVE-2024-58237, CVE-2024-57913, CVE-2024-50085, CVE-2024-53109, CVE-2024-56693,     CVE-2025-21993, CVE-2024-53213, CVE-2024-50026, CVE-2024-53095, CVE-2024-56664, CVE-2024-53111,     CVE-2024-50041, CVE-2024-50021, CVE-2024-39282, CVE-2024-56592, CVE-2024-56748, CVE-2024-47794,     CVE-2024-50271, CVE-2024-56614, CVE-2024-50166, CVE-2024-57849, CVE-2024-56573, CVE-2024-56620,     CVE-2024-50194, CVE-2024-56723, CVE-2024-50267, CVE-2024-56779, CVE-2024-56656, CVE-2024-50164,     CVE-2024-50076, CVE-2024-50126, CVE-2025-21831, CVE-2024-56610, CVE-2024-56670, CVE-2024-53145,     CVE-2024-56760, CVE-2024-56602, CVE-2024-53202)

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

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

The remote NewStart CGSL host, running version MAIN 7.02, has kernel packages installed that are affected by multiple vulnerabilities:

  - In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect     labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects     to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets     are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to     write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack     in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule     'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a     program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener     at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data     in both directions. * Collect network traffic of this connection. All packets in both directions are     labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized,     and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This     behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no     explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the     Smack documentation claims. (CVE-2024-47659)

  - In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: Fix kernel crash     on receiver USB disconnect hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU) races     when it races with itself. hidpp_connect_event() primarily runs from a workqueue but it also runs on     probe() and if a device-connected packet is received by the hw when the thread running     hidpp_connect_event() from probe() is waiting on the hw, then a second thread running     hidpp_connect_event() will be started from the workqueue. This opens the following races (note the below     code is simplified): 1. Retrieving + printing the protocol (harmless race): if (!hidpp->protocol_major) {     hidpp_root_get_protocol_version() hidpp->protocol_major = response.rap.params[0]; } We can actually see     this race hit in the dmesg in the abrt output attached to rhbz#2227968: [ 3064.624215] logitech-hidpp-     device 0003:046D:4071.0049: HID++ 4.5 device connected. [ 3064.658184] logitech-hidpp-device     0003:046D:4071.0049: HID++ 4.5 device connected. Testing with extra logging added has shown that after     this the 2 threads take turn grabbing the hw access mutex (send_mutex) so they ping-pong through all the     other TOCTOU cases managing to hit all of them: 2. Updating the name to the HIDPP name (harmless race): if     (hidpp->name == hdev->name) { ... hidpp->name = new_name; } 3. Initializing the power_supply class for the     battery (problematic!): hidpp_initialize_battery() { if (hidpp->battery.ps) return 0; probe_battery(); /*     Blocks, threads take turns executing this */ hidpp->battery.desc.properties = devm_kmemdup(dev,     hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps =     devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); } 4. Creating delayed     input_device (potentially problematic): if (hidpp->delayed_input) return; hidpp->delayed_input =     hidpp_allocate_input(hdev); The really big problem here is 3. Hitting the race leads to the following     sequence: hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
    hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); ...
    hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
    hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); So now we     have registered 2 power supplies for the same battery, which looks a bit weird from userspace's pov but     this is not even the really big problem. Notice how: 1. This is all devm-maganaged 2. The     hidpp->battery.desc struct is shared between the 2 power supplies 3. hidpp->battery.desc.properties points     to the result from the second devm_kmemdup() This causes a use after free scenario on USB disconnect of     the receiver: 1. The last registered power supply class device gets unregistered 2. The memory from the     last devm_kmemdup() call gets freed, hidpp->battery.desc.properties now points to freed memory 3. The     first registered power supply class device gets unregistered, this involves sending a remove uevent to     userspace which invokes power_supply_uevent() to fill the uevent data 4. power_supply_uevent() uses     hidpp->battery.desc.properties which now points to freed memory leading to backtraces like this one: Sep     22 20:01:35 eric kernel: BUG: unable to handle page fault for address: ffffb2140e017f08 ... Sep 22     20:01:35 eric kernel: Workqueue: usb_hub_wq hub_event Sep 22 20:01:35 eric kernel: RIP:
    0010:power_supply_uevent+0xee/0x1d0 ... Sep 22 20:01:35 eric kernel: ? asm_exc_page_fault+0x26/0x30 Sep 22     20:01:35 eric kernel: ? power_supply_uevent+0xee/0x1d0 Sep 22 20:01:35 eric kernel: ?     power_supply_uevent+0x10d/0x1d0 Sep 22 20:01:35 eric kernel: dev_uevent+0x10f/0x2d0 Sep 22 20:01:35 eric     kernel: kobject_uevent_env+0x291/0x680 Sep 22 20:01:35 eric kernel: ---truncated--- (CVE-2023-52478)

  - In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX     during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast     majority of cases, now and then it causes instability. This leads to system crashes and other undefined     behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can't     observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.
    (CVE-2023-52882)

  - In the Linux kernel, the following vulnerability has been resolved: net: can: j1939: enhanced error     handling for tightly received RTS messages in xtp_rx_rts_session_new This patch enhances error handling in     scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative     WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows     for the early termination of problematic sessions. Previously, sessions were only released at the end of     j1939_xtp_rx_rts(). Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 &     while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0     18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done (CVE-2023-52887)

  - In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Only free     buffer VA that is not NULL In the MediaTek vcodec driver, while mtk_vcodec_mem_free() is mostly called     only when the buffer to free exists, there are some instances that didn't do the check and triggered     warnings in practice. We believe those checks were forgotten unintentionally. Add the checks back to fix     the warnings. (CVE-2023-52888)

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

ID	Name	Product	Family	Published	Updated	Severity
216788	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2025-094)	Nessus	Amazon Linux Local Security Checks	2/26/2025	2/26/2026	high
214608	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-809)	Nessus	Amazon Linux Local Security Checks	1/24/2025	2/24/2026	high
234824	Ubuntu 18.04 LTS : Linux kernel (IBM) vulnerabilities (USN-7463-1)	Nessus	Ubuntu Local Security Checks	4/25/2025	1/6/2026	high
232516	CBL Mariner 2.0 Security Update: kernel (CVE-2024-55916)	Nessus	MarinerOS Local Security Checks	3/10/2025	3/20/2025	medium
232640	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:0577-2)	Nessus	SuSE Local Security Checks	3/12/2025	9/24/2025	high
267177	Unity Linux 20.1050a / 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-433453)	Nessus	Unity Linux Local Security Checks	10/7/2025	10/15/2025	medium
236988	Ubuntu 24.04 LTS : Linux kernel (Raspberry Pi Real-time) vulnerabilities (USN-7523-1)	Nessus	Ubuntu Local Security Checks	5/20/2025	1/6/2026	high
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	7/25/2025	1/6/2026	high

Detections

Analytics

Plugins Search

high

high

high

medium

high

medium

high

high