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

    kernel:SUNRPC: fix a memleak in gss_import_v2_context(CVE-2023-52653)

    apparmor: Fix null pointer deref when receiving skb during sock creation(CVE-2023-52889)

    protect the fetch of -fd[fd] in do_dup2() from mispredictions(CVE-2024-42265)

    tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc(CVE-2023-52880)

    padata: Fix possible divide-by-0 panic in padata_mt_helper()(CVE-2024-43889)

    dev/parport: fix the array out-of-bounds risk(CVE-2024-42301)

    netfilter: ctnetlink: use helper function to calculate expect ID(CVE-2024-44944)

    netns: Make get_net_ns() handle zero refcount net(CVE-2024-40958)

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

    kvm: s390: Reject memory region operations for ucontrol VMs(CVE-2024-43819)

    scsi: qla2xxx: validate nvme_local_port correctly(CVE-2024-42286)

    scsi: qla2xxx: During vport delete send async logout explicitly(CVE-2024-42289)

    gpio: prevent potential speculation leaks in gpio_device_get_desc()(CVE-2024-44931)

    ipv6: prevent possible NULL deref in fib6_nh_init()(CVE-2024-40961)

    cgroup/cpuset: Prevent UAF in proc_cpuset_show()(CVE-2024-43853)

    tracing: Fix overflow in get_free_elt()(CVE-2024-43890)

    exec: Fix ToCToU between perm check and set-uid/gid usage(CVE-2024-43882)

    drm/vmwgfx: Fix a deadlock in dma buf fence polling(CVE-2024-43863)

    io_uring: lock overflowing for IOPOLL(CVE-2023-52903)

    serial: core: check uartclk for zero to avoid divide by zero(CVE-2024-43893)

    sysctl: always initialize i_uid/i_gid(CVE-2024-42312)

    md/raid5: avoid BUG_ON() while continue reshape after reassembling(CVE-2024-43914)

    memcg: protect concurrent access to mem_cgroup_idr(CVE-2024-43892)

    scsi: qla2xxx: Fix for possible memory corruption(CVE-2024-42288)

    dmaengine: idxd: Prevent use after free on completion memory(CVE-2022-48867)

    x86/mtrr: Check if fixed MTRRs exist before saving them(CVE-2024-44948)

    dma: fix call order in dmam_free_coherent(CVE-2024-43856)

    block: initialize integrity buffer to zero before writing it to media(CVE-2024-43854)

    media: xc2028: avoid use-after-free in load_firmware_cb()(CVE-2024-43900)

    devres: Fix memory leakage caused by driver API devm_free_percpu()(CVE-2024-43871)

    lib: objagg: Fix general protection fault(CVE-2024-43846)

    xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration(CVE-2024-45006)

    kobject_uevent: Fix OOB access within zap_modalias_env()(CVE-2024-42292)

    drm/client: fix null pointer dereference in drm_client_modeset_probe(CVE-2024-43894)

    drm/qxl: Add check for drm_cvt_mode(CVE-2024-43829)

    userfaultfd: fix checks for huge PMDs(CVE-2024-46787)

    md: fix deadlock between mddev_suspend and flush bio(CVE-2024-43855)

    udf: Avoid excessive partition lengths(CVE-2024-46777)

    uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (CVE-2024-46739)

    In the Linux kernel, the following vulnerability has been resolved:memcg_write_event_control(): fix a     user-triggerable oops  we are *not* guaranteed that anything past the terminating NUL is mapped (let alone     initialized with anything sane).(CVE-2024-45021)

    scsi: aacraid: Fix double-free on probe failure(CVE-2024-46673)

    Squashfs: sanity check symbolic link size(CVE-2024-46744)

    apparmor: fix possible NULL pointer dereference(CVE-2024-46721)

    of/irq: Prevent device address out-of-bounds read in interrupt map walk(CVE-2024-46743)

    PCI: Add missing bridge lock to pci_bus_lock()(CVE-2024-46750)

    fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE(CVE-2024-45025)

    usb: typec: ucsi: Fix null pointer dereference in trace(CVE-2024-46719)

    thunderbolt: Mark XDomain as unplugged when router is removed(CVE-2024-46702)

    selinux,smack: don't bypass permissions check in inode_setsecctx hook(CVE-2024-46695)

    VMCI: Fix use-after-free when removing resource in vmci_resource_remove()(CVE-2024-46738)

    drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links(CVE-2024-46816)

    drm/amd/display: Check msg_id before processing transcation(CVE-2024-46814)

    sch/ netem: fix use after free in netem_dequeue(CVE-2024-46800)

    nvmet-tcp: fix kernel crash if commands allocation fails(CVE-2024-46737)

    drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[](CVE-2024-46815)

    ice: Add netif_device_attach/detach into PF reset flow(CVE-2024-46770)

    driver: iio: add missing checks on iio_info's callback access(CVE-2024-46715)

    pktgen: use cpus_read_lock() in pg_net_init()(CVE-2024-46681)

    drm/amd/display: Check link_index before accessing dc-links[](CVE-2024-46813)

    drm/amd/display: Assign linear_pitch_alignment even for VM(CVE-2024-46732)

    rtmutex: Drop rt_mutex::wait_lock before scheduling(CVE-2024-46829)

    perf/aux: Fix AUX buffer serialization(CVE-2024-46713)

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

    SUNRPC: lock against -sock changing during sysfs read(CVE-2022-48816)

    inet: inet_defrag: prevent sk release while still in use(CVE-2024-26921)

    rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation(CVE-2024-36017)

    xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING(CVE-2024-35976)

    netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get()(CVE-2024-35898)

    net: atlantic: eliminate double free in error handling logic(CVE-2023-52664)

    In the Linux kernel, the following vulnerability has been resolved:USB: usbtmc: prevent kernel-usb-     infoleak  The syzbot reported a kernel-usb-infoleak in usbtmc_write, we need to clear the structure before     filling fields.(CVE-2024-47671)

    ELF: fix kernel.randomize_va_space double read(CVE-2024-46826)

    vfs: Don't evict inode under the inode lru traversing context(CVE-2024-45003)

    perf/x86/intel: Limit the period on Haswell(CVE-2024-46848)

    platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses(CVE-2024-46859)

    arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry(CVE-2024-46822)

    ethtool: fail closed if we can't get max channel used in indirection tables(CVE-2024-46834)

    netem: fix return value if duplicate enqueue fails(CVE-2024-45016)

    ethtool: check device is present when getting link settings(CVE-2024-46679)

    In the Linux kernel, the following vulnerability has been resolved:iommu: Return right value in     iommu_sva_bind_device()  iommu_sva_bind_device() should return either a sva bond handle or an ERR_PTR     value in error cases. Existing drivers (idxd and uacce) only check the return value with IS_ERR(). This     could potentially lead to a kernel NULL pointer dereference issue if the function returns NULL instead of     an error pointer.  In reality, this doesn't cause any problems because iommu_sva_bind_device() only     returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA. In this case,     iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will return an error, and the device drivers won't call     iommu_sva_bind_device() at all.(CVE-2024-40945)

    xdp: fix invalid wait context of page_pool_destroy()(CVE-2024-43834)

    mlxsw: spectrum_acl_erp: Fix object nesting warning(CVE-2024-43880)

    virtio_net: Fix napi_skb_cache_put warning (CVE-2024-43835)

    tcp_bpf: fix return value of tcp_bpf_sendmsg()(CVE-2024-46783)

    drm/vmwgfx: Remove rcu locks from user resources(CVE-2022-48887)

    bonding: fix xfrm real_dev null pointer dereference(CVE-2024-44989)

    bonding: fix null pointer deref in bond_ipsec_offload_ok(CVE-2024-44990)

    net: core: reject skb_copy(_expand) for fraglist GSO skbs(CVE-2024-36929)

    block, bfq: fix possible UAF for bfqq-bic with merge chain(CVE-2024-47706)

    xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()(CVE-2024-40959)

    ipvlan: Dont Use skb-sk in ipvlan_process_v{4,6}_outbound(CVE-2024-33621)

    In the Linux kernel, the following vulnerability has been resolved:net: ena: Add validation for completion     descriptors consistency  Validate that `first` flag is set only for the first descriptor in multi-buffer     packets. In case of an invalid descriptor, a reset will occur. A new reset reason for RX data corruption     has been added.(CVE-2024-40999)

    net: hns3: fix kernel crash problem in concurrent scenario (CVE-2024-39507)

    net/mlx5: Fix bridge mode operations when there are no VFs(CVE-2024-46857)

    KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3(CVE-2024-46707)

    ipv6: prevent UAF in ip6_send_skb()(CVE-2024-44987)

    net: hns3: fix a deadlock problem when config TC during resetting(CVE-2024-44995)

    fsnotify: clear PARENT_WATCHED flags lazily(CVE-2024-47660)

    sctp: Fix null-ptr-deref in reuseport_add_sock()(CVE-2024-44935)

    bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()(CVE-2024-42067)

    In the Linux kernel, the following vulnerability has been resolved: bpf: Take return from set_memory_ro()     into account with bpf_prog_lock_ro() set_memory_ro() can fail, leaving memory unprotected. Check its     return and take it into account as an error.(CVE-2024-42068)

    fuse: Initialize beyond-EOF page contents before setting uptodate(CVE-2024-44947)

    i2c: core: Run atomic i2c xfer when !preemptible(CVE-2023-52791)

    nvme: avoid double free special payload(CVE-2024-41073)

    drm/amd/display: Fix index out of bounds in degamma hardware format translation(CVE-2024-49894)

    drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error(CVE-2024-47698)

    cifs: Fix buffer overflow when parsing NFS reparse points(CVE-2024-49996)

    netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()(CVE-2024-47685)

    net: do not delay dst_entries_add() in dst_release()(CVE-2024-50036)

    ppp: fix ppp_async_encode() illegal access(CVE-2024-50035)

    ACPI: sysfs: validate return type of _STR method(CVE-2024-49860)

    nbd: fix race between timeout and normal completion(CVE-2024-49855)

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

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

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

    Andy Nguyen discovered that the Bluetooth L2CAP implementation in the Linux kernel contained a type-     confusion error. A physically proximate remote attacker could use this to cause a denial of service     (system crash) or possibly execute arbitrary code. (CVE-2020-12351)

    Andy Nguyen discovered that the Bluetooth A2MP implementation in the Linux kernel did not properly     initialize memory in some situations. A physically proximate remote attacker could use this to expose     sensitive information (kernel memory). (CVE-2020-12352)

    Andy Nguyen discovered that the Bluetooth HCI event packet parser in the Linux kernel did not properly     handle event advertisements of certain sizes, leading to a heap-based buffer overflow. A physically     proximate remote attacker could use this to cause a denial of service (system crash) or possibly execute     arbitrary code. (CVE-2020-24490)

    It was discovered that the CIFS network file system implementation in the Linux kernel did not properly     validate certain SMB messages, leading to an out-of-bounds read vulnerability. An attacker could use this     to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2023-6610)

    Supraja Sridhara, Benedict Schlter, Mark Kuhne, Andrin Bertschi, and Shweta Shinde discovered that the     Confidential Computing framework in the Linux kernel for x86 platforms did not properly handle 32-bit     emulation on TDX and SEV. An attacker with access to the VMM could use this to cause a denial of service     (guest crash) or possibly execute arbitrary code. (CVE-2024-25744)

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

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Android drivers;

    - Serial ATA and Parallel ATA drivers;

    - ATM drivers;

    - Drivers core;

    - ATA over ethernet (AOE) driver;

    - Null block device driver;

    - TPM device driver;

    - Character device driver;

    - Clock framework and drivers;

    - Buffer Sharing and Synchronization framework;

    - ARM SCMI message protocol;

    - EFI core;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - ISDN/mISDN subsystem;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - STMicroelectronics network drivers;

    - Near Field Communication (NFC) drivers;

    - NTB driver;

    - Virtio pmem driver;

    - NVME drivers;

    - Device tree and open firmware driver;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Thermal drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - Userspace I/O drivers;

    - USB Device Class drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Type-C Port Controller Manager driver;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - 9P distributed file system;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - SMB network file system;

    - Bitmap API;

    - Network file system (NFS) superblock;

    - Objagg library;

    - Perf events;

    - Virtio network driver;

    - Bluetooth subsystem;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - Network traffic control;

    - Network sockets;

    - TCP network protocol;

    - BPF subsystem;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Kernel thread helper (kthread);

    - Locking primitives;

    - Padata parallel execution mechanism;

    - RCU subsystem;

    - Arbitrary resource management;

    - Scheduler infrastructure;

    - Static call mechanism;

    - Tracing infrastructure;

    - Radix Tree data structure library;

    - Kernel userspace event delivery library;

    - Memory management;

    - Amateur Radio drivers;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - Ethtool driver;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - Netlink;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - Wireless networking;

    - AppArmor security module;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - AudioScience HPI driver;

    - Amlogic Meson SoC drivers;

    - SoC audio core drivers;

    - USB sound devices; (CVE-2024-41091, CVE-2024-46800, CVE-2024-49924, CVE-2024-47659, CVE-2024-42295,     CVE-2024-42284, CVE-2024-38577, CVE-2024-49902, CVE-2024-45011, CVE-2024-47673, CVE-2024-38538,     CVE-2024-45008, CVE-2024-47667, CVE-2024-46832, CVE-2024-43879, CVE-2024-41059, CVE-2024-43853,     CVE-2024-44940, CVE-2024-44947, CVE-2024-43828, CVE-2024-41090, CVE-2024-44944, CVE-2024-43834,     CVE-2024-46777, CVE-2024-46689, CVE-2024-35965, CVE-2024-42276, CVE-2024-50264, CVE-2024-44965,     CVE-2024-49977, CVE-2024-42079, CVE-2024-46744, CVE-2024-42299, CVE-2024-43909, CVE-2024-41098,     CVE-2024-46731, CVE-2024-44946, CVE-2024-50024, CVE-2024-49858, CVE-2024-49892, CVE-2024-44989,     CVE-2024-47663, CVE-2024-49983, CVE-2024-42286, CVE-2024-42310, CVE-2024-44974, CVE-2024-43892,     CVE-2024-46840, CVE-2024-47695, CVE-2024-46780, CVE-2024-46757, CVE-2024-46707, CVE-2024-49894,     CVE-2024-50007, CVE-2024-47705, CVE-2024-49890, CVE-2024-46815, CVE-2024-36968, CVE-2024-40915,     CVE-2024-44995, CVE-2024-49871, CVE-2024-42265, CVE-2024-42283, CVE-2024-50000, CVE-2024-42309,     CVE-2024-47748, CVE-2024-35967, CVE-2023-52904, CVE-2024-46745, CVE-2024-41016, CVE-2024-49868,     CVE-2024-41011, CVE-2024-50186, CVE-2024-50033, CVE-2024-38545, CVE-2024-42267, CVE-2024-46852,     CVE-2024-44987, CVE-2024-46783, CVE-2024-47671, CVE-2024-46721, CVE-2024-46853, CVE-2024-43914,     CVE-2024-43907, CVE-2024-47734, CVE-2024-36484, CVE-2024-46781, CVE-2024-47693, CVE-2024-46791,     CVE-2024-49913, CVE-2024-49900, CVE-2024-50191, CVE-2024-43860, CVE-2024-45018, CVE-2024-46854,     CVE-2024-42246, CVE-2024-42156, CVE-2024-47660, CVE-2024-49878, CVE-2024-44982, CVE-2024-43867,     CVE-2024-49938, CVE-2024-47737, CVE-2024-46743, CVE-2024-42292, CVE-2024-50181, CVE-2024-41020,     CVE-2024-43863, CVE-2024-46817, CVE-2024-42281, CVE-2023-52621, CVE-2024-47749, CVE-2024-46804,     CVE-2024-47747, CVE-2024-50045, CVE-2024-41065, CVE-2023-52434, CVE-2024-50095, CVE-2024-45025,     CVE-2024-50179, CVE-2024-49946, CVE-2024-46782, CVE-2024-43839, CVE-2024-43904, CVE-2024-44958,     CVE-2024-44934, CVE-2024-45006, CVE-2024-49969, CVE-2024-44986, CVE-2024-46752, CVE-2024-35966,     CVE-2024-39463, CVE-2024-49883, CVE-2024-46805, CVE-2024-44935, CVE-2023-52532, CVE-2024-41071,     CVE-2024-46807, CVE-2024-43846, CVE-2024-50015, CVE-2024-26661, CVE-2024-43841, CVE-2024-46819,     CVE-2024-44931, CVE-2024-53057, CVE-2024-49982, CVE-2023-52757, CVE-2024-47735, CVE-2024-49866,     CVE-2024-46763, CVE-2024-45021, CVE-2024-46814, CVE-2024-46673, CVE-2024-43873, CVE-2024-49997,     CVE-2024-38602, CVE-2024-46795, CVE-2024-26822, CVE-2024-47670, CVE-2024-46755, CVE-2024-43902,     CVE-2024-46859, CVE-2024-43883, CVE-2024-49966, CVE-2024-42305, CVE-2024-49959, CVE-2024-42280,     CVE-2024-49965, CVE-2024-47674, CVE-2024-46723, CVE-2024-50031, CVE-2024-50184, CVE-2024-36893,     CVE-2024-43875, CVE-2023-52918, CVE-2024-49867, CVE-2024-49981, CVE-2024-43861, CVE-2024-49895,     CVE-2024-26669, CVE-2024-38544, CVE-2024-49973, CVE-2024-41015, CVE-2024-42296, CVE-2024-46722,     CVE-2024-42158, CVE-2024-49881, CVE-2024-27072, CVE-2024-47739, CVE-2024-46828, CVE-2024-46724,     CVE-2024-44999, CVE-2024-44971, CVE-2024-40973, CVE-2023-52572, CVE-2024-47709, CVE-2024-47742,     CVE-2024-46818, CVE-2024-50035, CVE-2024-50188, CVE-2024-47679, CVE-2024-38667, CVE-2024-41078,     CVE-2024-46844, CVE-2024-47672, CVE-2024-42306, CVE-2024-46758, CVE-2024-43869, CVE-2024-50062,     CVE-2024-49875, CVE-2024-41017, CVE-2024-41077, CVE-2024-50038, CVE-2024-50013, CVE-2024-46746,     CVE-2024-49962, CVE-2024-50049, CVE-2023-52751, CVE-2024-47684, CVE-2024-47701, CVE-2024-41070,     CVE-2024-44942, CVE-2024-35904, CVE-2024-26607, CVE-2024-50019, CVE-2024-46714, CVE-2024-46738,     CVE-2024-42312, CVE-2024-44948, CVE-2024-43890, CVE-2024-43893, CVE-2024-26800, CVE-2024-35963,     CVE-2024-49884, CVE-2024-49930, CVE-2024-46829, CVE-2024-50046, CVE-2024-49985, CVE-2024-41022,     CVE-2024-43894, CVE-2024-43830, CVE-2024-45009, CVE-2024-35951, CVE-2024-49889, CVE-2024-42301,     CVE-2024-38632, CVE-2024-42114, CVE-2024-42290, CVE-2024-43858, CVE-2024-50002, CVE-2024-41060,     CVE-2024-47696, CVE-2024-43870, CVE-2024-49948, CVE-2024-46759, CVE-2024-26947, CVE-2024-46713,     CVE-2024-47740, CVE-2024-44960, CVE-2024-46756, CVE-2024-46737, CVE-2024-41068, CVE-2024-46677,     CVE-2024-41063, CVE-2024-41019, CVE-2023-52917, CVE-2024-38611, CVE-2024-49852, CVE-2024-49863,     CVE-2024-46739, CVE-2024-43908, CVE-2024-47697, CVE-2024-46810, CVE-2024-41072, CVE-2024-42302,     CVE-2024-50003, CVE-2024-45026, CVE-2024-45028, CVE-2024-42259, CVE-2022-48666, CVE-2024-49995,     CVE-2024-50093, CVE-2024-46865, CVE-2024-49886, CVE-2024-43889, CVE-2024-42285, CVE-2024-50006,     CVE-2024-42271, CVE-2024-42274, CVE-2024-49957, CVE-2024-42289, CVE-2024-46719, CVE-2024-46858,     CVE-2024-49958, CVE-2024-50041, CVE-2024-46675, CVE-2024-41064, CVE-2024-39472, CVE-2024-42287,     CVE-2024-46822, CVE-2024-49877, CVE-2024-43849, CVE-2024-50040, CVE-2024-49879, CVE-2024-46798,     CVE-2024-46855, CVE-2024-49944, CVE-2024-46676, CVE-2024-26893, CVE-2024-43835, CVE-2024-47665,     CVE-2024-47669, CVE-2024-43882, CVE-2024-46740, CVE-2024-49851, CVE-2024-46849, CVE-2024-42311,     CVE-2024-44985, CVE-2024-47757, CVE-2024-50001, CVE-2024-46750, CVE-2024-47706, CVE-2024-50039,     CVE-2024-46702, CVE-2024-46725, CVE-2024-43817, CVE-2024-49907, CVE-2024-46695, CVE-2024-38553,     CVE-2024-42272, CVE-2024-49882, CVE-2024-42269, CVE-2024-44954, CVE-2024-42318, CVE-2024-42297,     CVE-2024-49975, CVE-2024-44988, CVE-2024-49963, CVE-2024-47692, CVE-2024-41042, CVE-2024-41081,     CVE-2024-43854, CVE-2024-46771, CVE-2024-46732, CVE-2024-47712, CVE-2024-47699, CVE-2024-49927,     CVE-2024-49860, CVE-2024-45003, CVE-2024-49954, CVE-2024-42304, CVE-2024-49933, CVE-2024-42277,     CVE-2024-49955, CVE-2024-47710, CVE-2024-43905, CVE-2024-49903, CVE-2024-43856, CVE-2024-50180,     CVE-2024-44966, CVE-2024-46685, CVE-2024-49935, CVE-2024-44990, CVE-2023-52889, CVE-2024-49896,     CVE-2024-44969, CVE-2024-50189, CVE-2024-50008, CVE-2024-47720, CVE-2024-42313, CVE-2024-44983,     CVE-2024-49949, CVE-2024-46761, CVE-2024-47690, CVE-2024-50059, CVE-2024-41073, CVE-2024-47723,     CVE-2024-46747, CVE-2024-49952, CVE-2024-50096, CVE-2024-42288, CVE-2024-43871, CVE-2024-42126,     CVE-2024-44998, CVE-2024-47685, CVE-2024-46679, CVE-2024-43884, CVE-2024-47668, CVE-2024-49936,     CVE-2024-43829, CVE-2024-47756, CVE-2024-43880, CVE-2024-45007, CVE-2024-40910, CVE-2024-50044,     CVE-2023-52639, CVE-2024-47698, CVE-2024-41012, CVE-2024-49856, CVE-2024-47713, CVE-2024-47718,     CVE-2024-49967)

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.

The remote SUSE Linux SLES15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:3195-1 advisory.

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

    The following security bugs were fixed:

    - CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
    - CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
    - CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
    - CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).
    - CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
    - CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
    - CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
    - CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
    - CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
    - CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
    - CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
    - CVE-2024-36881: Fix reset ptes when close() for wr-protected (bsc#1225718).
    - CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).
    - CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342).
    - CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496).
    - CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
    - CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505).
    - CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472).
    - CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
    - CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
    - CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
    - CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
    - CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
    - CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
    - CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
    - CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
    - CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
    - CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
    - CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
    - CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).
    - CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).
    - CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).
    - CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
    - CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).
    - CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).
    - CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)
    - CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).
    - CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)
    - CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)
    - CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
    - CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
    - CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).
    - CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252).
    - CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).
    - CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).
    - CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).
    - CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)
    - CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)
    - CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)
    - CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)
    - CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)
    - CVE-2024-42290: Handle runtime power management correctly (bsc#1229379).
    - CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).
    - CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).
    - CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).
    - CVE-2024-43850: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).
    - CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).
    - CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).
    - CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).
    - CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).
    - CVE-2024-26669: Fix chain template offload (bsc#1222350).
    - CVE-2024-26677: Blacklist e7870cf13d20 (' Fix delayed ACKs to not set the reference serial number')     (bsc#1222387)
    - CVE-2024-41050: Cyclic allocation of msg_id to avoid reuse (bsc#1228499).
    - CVE-2024-41051: Wait for ondemand_object_worker to finish when dropping object (bsc#1228468).
    - CVE-2024-41074: Set object to close if ondemand_id < 0 in copen (bsc#1228643).
    - CVE-2024-41075: Add consistency check for copen/cread (bsc#1228646).
    - CVE-2024-41012: Remove locks reliably when fcntl/close race is detected (bsc#1228247).
    - CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).
    - CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).
    - CVE-2024-42159: Fix sanitise num_phys (bsc#1228754).
    - CVE-2024-42241: Disable PMD-sized page cache if needed (bsc#1228986).
    - CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).
    - CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).
    - CVE-2024-26837: Race between creation of new group memberships and generation of the list of MDB events     to replay (bsc#1222973).
    - CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
    - CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
    - CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).
    - CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
    - CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).
    - CVE-2024-40938: Fix d_parent walk (bsc#1227840).
    - CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).
    - CVE-2024-41010: Fix too early release of tcx_entry (bsc#1228021).
    - CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).
    - CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).
    - CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).
    - CVE-2024-42138: Fix double memory deallocation in case of invalid INI file (bsc#1228500).
    - CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).
    - CVE-2024-42139: Fix improper extts handling (bsc#1228503).
    - CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).
    - CVE-2024-42113: Initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).
    - CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).
    - CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).
    - CVE-2024-42073: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).
    - CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).
    - CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).
    - CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).
    - CVE-2024-41000: Prefer different overflow check (bsc#1227867).
    - CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).
    - CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).
    - CVE-2024-41069: Fix route memory corruption (bsc#1228644).
    - CVE-2024-39506: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).
    - CVE-2024-42145: Implement a limit on UMAD receive List (bsc#1228743).
    - CVE-2024-40994: Fix integer overflow in max_vclocks_store (bsc#1227829).
    - CVE-2024-42124: Make qedf_execute_tmf() non-preemptible (bsc#1228705).
    - CVE-2024-42096: Stop playing stack games in profile_pc() (bsc#1228633).
    - CVE-2024-42224: Correct check for empty list (bsc#1228723).
    - CVE-2024-41048: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).
    - CVE-2024-40958: Make get_net_ns() handle zero refcount net (bsc#1227812).
    - CVE-2024-40939: Fix tainted pointer delete is case of region creation fail (bsc#1227799).
    - CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).
    - CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).
    - CVE-2024-41044: Reject claimed-as-LCP but actually malformed packets (bsc#1228530).
    - CVE-2024-41066: Add tx check to prevent skb leak (bsc#1228640).
    - CVE-2024-42093: Avoid explicit cpumask var allocation on stack (bsc#1228680).
    - CVE-2024-42122: Add NULL pointer check for kzalloc (bsc#1228591).
    - CVE-2024-41078: Fix quota root leak after quota disable failure (bsc#1228655).
    - CVE-2024-40989: Disassociate vcpus from redistributor region on teardown (bsc#1227823).
    - CVE-2024-41064: Avoid possible crash when edev->pdev changes (bsc#1228599).
    - CVE-2024-41036: Fix deadlock with the SPI chip variant (bsc#1228496).
    - CVE-2024-41040: Fix UAF when resolving a clash (bsc#1228518).
    - CVE-2024-35949: Make sure that WRITTEN is set on all metadata blocks (bsc#1224700).
    - CVE-2024-41081: Block BH in ila_output() (bsc#1228617).
    - CVE-2024-41076: Fix memory leak in nfs4_set_security_label (bsc#1228649).
    - CVE-2024-42079: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).
    - CVE-2024-41057: Fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).
    - CVE-2024-41058: Fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).
    - CVE-2024-41015: Add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).
    - CVE-2024-40956: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).
    - CVE-2024-27437: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).
    - CVE-2024-41032: Check if a hash-index is in cpu_possible_mask (bsc#1228460).
    - CVE-2024-40957: Fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors     (bsc#1227811).
    - CVE-2024-41041: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).
    - CVE-2024-40954: Do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)
    - CVE-2024-42070: Fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).
    - CVE-2024-41070: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).
    - CVE-2024-40959: Check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).
    - CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).
    - CVE-2024-40909: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).
    - CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).


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.

ID	Name	Product	Family	Published	Updated	Severity
212605	EulerOS 2.0 SP11 : kernel (EulerOS-SA-2024-2983)	Nessus	Huawei Local Security Checks	12/12/2024	12/12/2024	critical
212612	EulerOS 2.0 SP11 : kernel (EulerOS-SA-2024-2969)	Nessus	Huawei Local Security Checks	12/12/2024	12/12/2024	critical
213658	Ubuntu 20.04 LTS : Linux kernel (Azure) vulnerabilities (USN-7194-1)	Nessus	Ubuntu Local Security Checks	1/9/2025	1/6/2026	critical
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
206955	SUSE SLES15: cluster-md-kmp-rt / dlm-kmp-rt / gfs2-kmp-rt / kernel-devel-rt / etc (SUSE-SU-2024:3195-1)	Nessus	SuSE Local Security Checks	9/11/2024	6/26/2026	high
282947	MiracleLinux 9 : kernel-5.14.0-570.12.1.el9_6 (AXSA:2025-10392:38)	Nessus	Miracle Linux Local Security Checks	1/13/2026	1/20/2026	critical

Detections

Analytics

Plugins Search

critical

critical

critical

high

high

critical