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

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

    mm: swap: fix race between free_swap_and_cache() and swapoff()

    There was previously a theoretical window where swapoff() could run and     teardown a swap_info_struct while a call to free_swap_and_cache() was     running in another thread.  This could cause, amongst other bad     possibilities, swap_page_trans_huge_swapped() (called by     free_swap_and_cache()) to access the freed memory for swap_map.

    This is a theoretical problem and I haven't been able to provoke it from a     test case.  But there has been agreement based on code review that this is     possible (see link below).

    Fix it by using get_swap_device()/put_swap_device(), which will stall     swapoff().  There was an extra check in _swap_info_get() to confirm that     the swap entry was not free.  This isn't present in get_swap_device()     because it doesn't make sense in general due to the race between getting     the reference and swapoff.  So I've added an equivalent check directly in     free_swap_and_cache().

    Details of how to provoke one possible issue (thanks to David Hildenbrand     for deriving this):

    --8<-----

    __swap_entry_free() might be the last user and result in     count == SWAP_HAS_CACHE.

    swapoff->try_to_unuse() will stop as soon as soon as si->inuse_pages==0.

    So the question is: could someone reclaim the folio and turn     si->inuse_pages==0, before we completed swap_page_trans_huge_swapped().

    Imagine the following: 2 MiB folio in the swapcache. Only 2 subpages are     still references by swap entries.

    Process 1 still references subpage 0 via swap entry.
    Process 2 still references subpage 1 via swap entry.

    Process 1 quits. Calls free_swap_and_cache().
    -> count == SWAP_HAS_CACHE     [then, preempted in the hypervisor etc.]

    Process 2 quits. Calls free_swap_and_cache().
    -> count == SWAP_HAS_CACHE

    Process 2 goes ahead, passes swap_page_trans_huge_swapped(), and calls
    __try_to_reclaim_swap().

    __try_to_reclaim_swap()->folio_free_swap()->delete_from_swap_cache()->     put_swap_folio()->free_swap_slot()->swapcache_free_entries()->     swap_entry_free()->swap_range_free()->     ...
    WRITE_ONCE(si->inuse_pages, si->inuse_pages - nr_entries);

    What stops swapoff to succeed after process 2 reclaimed the swap cache     but before process1 finished its call to swap_page_trans_huge_swapped()?

    --8<-----

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 20.04 LTS / 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-6898-3 advisory.

    Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error     conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this     vulnerability to cause a denial of service. (CVE-2022-38096)

    Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition,     leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a     denial of service (system crash). (CVE-2024-23307)

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

    Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a     race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause     a denial of service (system crash). (CVE-2024-24861)

    Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did     not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this     to cause a denial of service (system crash). (CVE-2024-25739)

    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;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Accessibility subsystem;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - Netfilter;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - NFC subsystem;

    - Open vSwitch;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Unix domain sockets;

    - eXpress Data Path;

    - ALSA SH drivers;

    - KVM core; (CVE-2024-35955, CVE-2024-35805, CVE-2024-26814, CVE-2024-27008, CVE-2024-26970,     CVE-2024-35944, CVE-2024-27013, CVE-2024-35938, CVE-2024-35853, CVE-2024-35969, CVE-2024-26981,     CVE-2024-26929, CVE-2024-27020, CVE-2024-35885, CVE-2024-35973, CVE-2024-35958, CVE-2024-26961,     CVE-2024-35912, CVE-2024-35890, CVE-2024-35804, CVE-2024-35813, CVE-2024-27393, CVE-2024-26956,     CVE-2024-35915, CVE-2024-26642, CVE-2024-35847, CVE-2024-26960, CVE-2024-26923, CVE-2024-35935,     CVE-2024-36025, CVE-2024-35898, CVE-2024-26810, CVE-2024-35809, CVE-2024-26813, CVE-2024-36007,     CVE-2024-35817, CVE-2024-35849, CVE-2024-35819, CVE-2024-35884, CVE-2024-35922, CVE-2024-36008,     CVE-2024-27004, CVE-2024-35902, CVE-2024-26828, CVE-2024-35791, CVE-2024-35930, CVE-2024-26973,     CVE-2024-26984, CVE-2024-35806, CVE-2024-26629, CVE-2024-26955, CVE-2024-26937, CVE-2024-27059,     CVE-2024-35872, CVE-2024-35978, CVE-2024-26950, CVE-2024-27018, CVE-2024-35857, CVE-2024-35990,     CVE-2024-27437, CVE-2024-35822, CVE-2024-36020, CVE-2024-26931, CVE-2024-26977, CVE-2024-26654,     CVE-2024-26988, CVE-2024-36005, CVE-2024-26969, CVE-2024-35960, CVE-2024-27016, CVE-2024-36006,     CVE-2024-35936, CVE-2024-35982, CVE-2024-36029, CVE-2024-27395, CVE-2024-26999, CVE-2024-35871,     CVE-2024-35893, CVE-2024-26925, CVE-2024-26965, CVE-2024-35933, CVE-2024-35976, CVE-2024-35899,     CVE-2024-35852, CVE-2024-35918, CVE-2024-26951, CVE-2024-27001, CVE-2024-35905, CVE-2024-35907,     CVE-2024-26976, CVE-2024-27000, CVE-2024-35910, CVE-2024-35950, CVE-2024-26974, CVE-2024-35785,     CVE-2023-52488, CVE-2023-52880, CVE-2024-35877, CVE-2024-35888, CVE-2024-35807, CVE-2024-35796,     CVE-2024-35821, CVE-2024-35854, CVE-2024-27015, CVE-2024-35823, CVE-2024-35900, CVE-2024-35815,     CVE-2024-26966, CVE-2024-26817, CVE-2024-35896, CVE-2024-27396, CVE-2024-27009, CVE-2024-35940,     CVE-2024-26996, CVE-2024-35825, CVE-2024-35984, CVE-2024-35886, CVE-2024-27019, CVE-2024-26922,     CVE-2024-35989, CVE-2024-26926, CVE-2024-35988, CVE-2024-26957, CVE-2024-26812, CVE-2024-35925,     CVE-2024-35970, CVE-2024-26989, CVE-2024-26811, CVE-2024-35895, CVE-2024-26935, CVE-2024-26958,     CVE-2024-35855, CVE-2024-35879, CVE-2024-26993, CVE-2024-35934, CVE-2024-36004, CVE-2024-35997,     CVE-2024-26994, CVE-2023-52699, CVE-2024-35789, CVE-2024-26964, CVE-2024-26687, CVE-2024-35851,     CVE-2024-35897, CVE-2024-26934)

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.

An update of the linux package has been released.

The version of kernel installed on the remote host is prior to 5.10.215-203.850. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2024-068 advisory.

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

    block: add check that partition length needs to be aligned with block size

    Before calling add partition or resize partition, there is no checkon whether the length is aligned with     the logical block size.If the logical block size of the disk is larger than 512 bytes,then the partition     size maybe not the multiple of the logical block size,and when the last sector is read, bio_truncate()     will adjust the bio size,resulting in an IO error if the size of the read command is smaller thanthe     logical block size.If integrity data is supported, this will alsoresult in a null pointer dereference when     calling bio_integrity_free. (CVE-2023-52458)

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

    x86/srso: Add SRSO mitigation for Hygon processors (CVE-2023-52482)

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

    netfilter: nf_tables: disallow timeout for anonymous sets (CVE-2023-52620)

    create_empty_lvol in drivers/mtd/ubi/vtbl.c in the Linux kernel through 6.7.4 can attempt to allocate zero     bytes, and crash, because of a missing check for ubi->leb_size. (CVE-2024-25739)

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

    netfilter: nf_tables: disallow anonymous set with timeout flag (CVE-2024-26642)

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

    netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (CVE-2024-26643)

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

    vfio/pci: Lock external INTx masking ops (CVE-2024-26810)

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

    vfio/pci: Create persistent INTx handler (CVE-2024-26812)

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

    vfio/platform: Create persistent IRQ handlers (CVE-2024-26813)

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

    netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path

    The commit mutex should not be released during the critical sectionbetween nft_gc_seq_begin() and     nft_gc_seq_end(), otherwise, async GCworker could collect expired objects and get the released commit     lockwithin the same GC sequence.

    nf_tables_module_autoload() temporarily releases the mutex to loadmodule dependencies, then it goes back     to replay the transaction again.Move it at the end of the abort phase after nft_gc_seq_end() is called.
    (CVE-2024-26925)

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

    scsi: qla2xxx: Fix command flush on cable pull (CVE-2024-26931)

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

    USB: core: Fix deadlock in usb_deauthorize_interface() (CVE-2024-26934)

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

    scsi: core: Fix unremoved procfs host directory regression (CVE-2024-26935)

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

    drm/i915/gt: Reset queue_priority_hint on parking (CVE-2024-26937)

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

    wireguard: netlink: access device through ctx instead of peer (CVE-2024-26950)

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

    wireguard: netlink: check for dangling peer via is_dead instead of empty list (CVE-2024-26951)

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

    nilfs2: prevent kernel bug at submit_bh_wbc() (CVE-2024-26955)

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

    nilfs2: fix failure to detect DAT corruption in btree and direct mappings (CVE-2024-26956)

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

    nfs: fix UAF in direct writes (CVE-2024-26958)

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

    mm: swap: fix race between free_swap_and_cache() and swapoff() (CVE-2024-26960)

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

    mac802154: fix llsec key resources release in mac802154_llsec_key_del (CVE-2024-26961)

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

    fat: fix uninitialized field in nostale filehandles (CVE-2024-26973)

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

    KVM: Always flush async #PF workqueue when vCPU is being destroyed (CVE-2024-26976)

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

    USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command (CVE-2024-27059)

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

    vfio/pci: Disable auto-enable of exclusive INTx IRQ (CVE-2024-27437)

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

    KVM: SVM: Flush pages under kvm->lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)

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

    dm snapshot: fix lockup in dm_exception_table_exit (CVE-2024-35805)

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

    PCI/PM: Drain runtime-idle callbacks before driver removal (CVE-2024-35809)

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

    mmc: core: Avoid negative index with array access (CVE-2024-35813)

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

    fs/aio: Check IOCB_AIO_RW before the struct aio_kiocb conversion (CVE-2024-35815)

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

    vt: fix unicode buffer corruption when deleting characters (CVE-2024-35823)

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

    udp: do not accept non-tunnel GSO skbs landing in a tunnel (CVE-2024-35884)

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

    erspan: make sure erspan_base_hdr is present in skb->head (CVE-2024-35888)

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

    bpf, sockmap: Prevent lock inversion deadlock in map delete elem (CVE-2024-35895)

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

    netfilter: validate user input for expected length (CVE-2024-35896)

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

    netfilter: nf_tables: discard table flag update with pending basechain deletion (CVE-2024-35897)

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

    netfilter: nf_tables: flush pending destroy work before exit_net release (CVE-2024-35899)

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

    netfilter: nf_tables: reject new basechain after table flag update (CVE-2024-35900)

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

    net/rds: fix possible cp null dereference (CVE-2024-35902)

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

    tcp: properly terminate timers for kernel sockets (CVE-2024-35910)

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

    block: prevent division by zero in blk_rq_stat_sum() (CVE-2024-35925)

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

    scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (CVE-2024-35930)

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

    btrfs: send: handle path ref underflow in header iterate_inode_ref() (CVE-2024-35935)

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

    btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() (CVE-2024-35936)

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

    VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() (CVE-2024-35944)

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

    i40e: fix vf may be used uninitialized in this function warning (CVE-2024-36020)

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

    Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error     conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this     vulnerability to cause a denial of service. (CVE-2022-38096)

    Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition,     leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a     denial of service (system crash). (CVE-2024-23307)

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

    Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a     race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause     a denial of service (system crash). (CVE-2024-24861)

    Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did     not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this     to cause a denial of service (system crash). (CVE-2024-25739)

    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;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Accessibility subsystem;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - Netfilter;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - Networking core;

    - Distributed Switch Architecture;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - NFC subsystem;

    - Open vSwitch;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Unix domain sockets;

    - eXpress Data Path;

    - Key management;

    - ALSA SH drivers;

    - KVM core; (CVE-2024-26993, CVE-2024-26996, CVE-2024-35879, CVE-2024-26812, CVE-2024-26984,     CVE-2024-26817, CVE-2024-35950, CVE-2024-26960, CVE-2024-27437, CVE-2024-26964, CVE-2024-27059,     CVE-2024-35969, CVE-2024-35936, CVE-2024-35912, CVE-2024-35915, CVE-2024-35938, CVE-2024-27019,     CVE-2024-35822, CVE-2024-35997, CVE-2024-35855, CVE-2024-26925, CVE-2024-26654, CVE-2024-26923,     CVE-2024-36031, CVE-2024-36020, CVE-2024-35823, CVE-2024-35852, CVE-2024-35989, CVE-2024-27000,     CVE-2024-35853, CVE-2024-27013, CVE-2024-35854, CVE-2024-35922, CVE-2024-26937, CVE-2023-52880,     CVE-2024-26974, CVE-2024-26629, CVE-2024-35804, CVE-2024-35958, CVE-2024-26814, CVE-2024-35890,     CVE-2024-35940, CVE-2024-26999, CVE-2024-35847, CVE-2024-27015, CVE-2024-26687, CVE-2024-26970,     CVE-2024-35930, CVE-2024-26813, CVE-2024-26810, CVE-2024-26969, CVE-2024-26977, CVE-2024-26956,     CVE-2024-35901, CVE-2024-27020, CVE-2024-35905, CVE-2024-35785, CVE-2024-27009, CVE-2024-35877,     CVE-2024-35893, CVE-2024-26989, CVE-2024-26642, CVE-2024-35857, CVE-2024-35935, CVE-2024-26828,     CVE-2024-26965, CVE-2024-35888, CVE-2024-35900, CVE-2024-26951, CVE-2024-35809, CVE-2024-27008,     CVE-2024-26958, CVE-2024-35973, CVE-2024-26935, CVE-2024-26934, CVE-2024-35982, CVE-2023-52488,     CVE-2024-35884, CVE-2024-35907, CVE-2024-27018, CVE-2024-26929, CVE-2024-35984, CVE-2024-35899,     CVE-2024-26976, CVE-2024-26922, CVE-2024-35817, CVE-2024-26961, CVE-2024-35925, CVE-2024-35821,     CVE-2024-36005, CVE-2024-35988, CVE-2024-35970, CVE-2024-27001, CVE-2024-35960, CVE-2022-48808,     CVE-2024-35927, CVE-2024-35806, CVE-2024-27016, CVE-2024-35897, CVE-2024-26957, CVE-2024-36025,     CVE-2024-35872, CVE-2024-26988, CVE-2024-35819, CVE-2024-35896, CVE-2024-36007, CVE-2024-35944,     CVE-2024-35990, CVE-2024-36006, CVE-2024-36004, CVE-2024-35955, CVE-2024-35898, CVE-2024-26973,     CVE-2024-26950, CVE-2024-36008, CVE-2024-35805, CVE-2024-35807, CVE-2024-35934, CVE-2024-26926,     CVE-2024-35902, CVE-2024-35918, CVE-2024-35895, CVE-2024-35978, CVE-2024-35849, CVE-2024-35791,     CVE-2024-26931, CVE-2024-35886, CVE-2024-26981, CVE-2024-27395, CVE-2024-35815, CVE-2024-26994,     CVE-2024-35825, CVE-2024-35789, CVE-2024-35813, CVE-2024-35885, CVE-2024-35851, CVE-2024-35796,     CVE-2023-52699, CVE-2024-35871, CVE-2024-26811, CVE-2024-26966, CVE-2024-35976, CVE-2024-26955,     CVE-2024-36029, CVE-2024-27396, CVE-2024-27004, CVE-2024-27393, CVE-2024-35910, CVE-2024-35933)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: mm: swap: fix race between     free_swap_and_cache() and swapoff() There was previously a theoretical window where swapoff() could run     and teardown a swap_info_struct while a call to free_swap_and_cache() was running in another thread. This     could cause, amongst other bad possibilities, swap_page_trans_huge_swapped() (called by     free_swap_and_cache()) to access the freed memory for swap_map. This is a theoretical problem and I     haven't been able to provoke it from a test case. But there has been agreement based on code review that     this is possible (see link below). Fix it by using get_swap_device()/put_swap_device(), which will stall     swapoff(). There was an extra check in _swap_info_get() to confirm that the swap entry was not free. This     isn't present in get_swap_device() because it doesn't make sense in general due to the race between     getting the reference and swapoff. So I've added an equivalent check directly in free_swap_and_cache().
    Details of how to provoke one possible issue (thanks to David Hildenbrand for deriving this): --8<-----
    __swap_entry_free() might be the last user and result in count == SWAP_HAS_CACHE.
    swapoff->try_to_unuse() will stop as soon as soon as si->inuse_pages==0. So the question is: could someone     reclaim the folio and turn si->inuse_pages==0, before we completed swap_page_trans_huge_swapped(). Imagine     the following: 2 MiB folio in the swapcache. Only 2 subpages are still references by swap entries. Process     1 still references subpage 0 via swap entry. Process 2 still references subpage 1 via swap entry. Process     1 quits. Calls free_swap_and_cache(). -> count == SWAP_HAS_CACHE [then, preempted in the hypervisor etc.]     Process 2 quits. Calls free_swap_and_cache(). -> count == SWAP_HAS_CACHE Process 2 goes ahead, passes     swap_page_trans_huge_swapped(), and calls __try_to_reclaim_swap().
    __try_to_reclaim_swap()->folio_free_swap()->delete_from_swap_cache()->     put_swap_folio()->free_swap_slot()->swapcache_free_entries()-> swap_entry_free()->swap_range_free()-> ...
    WRITE_ONCE(si->inuse_pages, si->inuse_pages - nr_entries); What stops swapoff to succeed after process 2     reclaimed the swap cache but before process1 finished its call to swap_page_trans_huge_swapped()?
    --8<----- (CVE-2024-26960)

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

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

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

    The following security bugs were fixed:

    - CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).
    - CVE-2024-26764: Fixed IOCB_AIO_RW check in fs/aio before the struct aio_kiocb conversion (bsc#1222721).
    - CVE-2024-26862: Fixed packet annotate data-races around ignore_outgoing (bsc#1223111).
    - CVE-2024-26673: Fixed netfilter/nft_ct layer 3 and 4 protocol sanitization (bsc#1222368).
    - CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system     (bsc#1209657).
    - CVE-2024-26993: Fixed fs/sysfs reference leak in sysfs_break_active_protection() (bsc#1223693).
    - CVE-2024-27013: Fixed tun limit printing rate when illegal packet received by tun device (bsc#1223745).
    - CVE-2024-27014: Fixed net/mlx5e to prevent deadlock while disabling aRFS (bsc#1223735).
    - CVE-2024-26948: Fixed drm/amd/display by adding dc_state NULL check in dc_state_release (bsc#1223664).
    - CVE-2024-27056: Fixed wifi/iwlwifi/mvm to ensure offloading TID queue exists (bsc#1223822).
    - CVE-2024-26960: Fixed mm/swap race between free_swap_and_cache() and swapoff() (bsc#1223655).
    - CVE-2023-52652: Fixed NTB for possible name leak in ntb_register_device() (bsc#1223686).
    - CVE-2024-23848: Fixed media/cec for possible use-after-free in cec_queue_msg_fh (bsc#1219104).
    - CVE-2024-26982: Fixed Squashfs inode number check not to be an invalid value of zero (bsc#1223634).
    - CVE-2024-26878: Fixed quota for potential NULL pointer dereference (bsc#1223060).
    - CVE-2024-26901: Fixed do_sys_name_to_handle() to use kzalloc() to prevent kernel-infoleak (bsc#1223198).
    - CVE-2024-26671: Fixed blk-mq IO hang from sbitmap wakeup race (bsc#1222357).
    - CVE-2024-26772: Fixed ext4 to avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()     (bsc#1222613).
    - CVE-2024-26906: Disallowed vsyscall page read for copy_from_kernel_nofault() (bsc#1223202).
    - CVE-2024-26816: Ignore relocations in .notes section when building with CONFIG_XEN_PV=y (bsc#1222624).
    - CVE-2024-26783: Fixed mm/vmscan bug when calling wakeup_kswapd() with a wrong zone index (bsc#1222615).
    - CVE-2024-26883: Fixed bpf stackmap overflow check on 32-bit arches (bsc#1223035).
    - CVE-2024-26884: Fixed bpf hashtab overflow check on 32-bit arches (bsc#1223189).
    - CVE-2024-26885: Fixed bpf DEVMAP_HASH overflow check on 32-bit arches (bsc#1223190).
    - CVE-2024-26882: Fixed net/ip_tunnel to make sure to pull inner header in ip_tunnel_rcv() (bsc#1223034).
    - CVE-2023-52645: Fixed pmdomain/mediatek race conditions with genpd (bsc#1223033).
    - CVE-2024-26836: Fixed platform/x86/think-lmi password opcode ordering for workstations (bsc#1222968).
    - CVE-2024-26601: Fixed ext4 buddy bitmap corruption via fast commit replay (bsc#1220342).
    - CVE-2024-26773: Fixed ext4 block allocation from corrupted group in ext4_mb_try_best_found()     (bsc#1222618).
    - CVE-2024-26807: Fixed spi/cadence-qspi NULL pointer reference in runtime PM hooks (bsc#1222801).
    - CVE-2024-26737: Fixed selftests/bpf racing between bpf_timer_cancel_and_free and bpf_timer_cancel     (bsc#1222557).
    - CVE-2024-26733: Fixed an overflow in arp_req_get() in arp (bsc#1222585).
    - CVE-2024-26684: Fixed net/stmmac/xgmac handling of DPP safety error for DMA channels (bsc#1222445).
    - CVE-2024-26704: Fixed a double-free of blocks due to wrong extents moved_len in ext4 (bsc#1222422).
    - CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).
    - CVE-2023-52503: Fixed tee/amdtee use-after-free vulnerability in amdtee_close_session (bsc#1220915).
    - CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).
    - CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).
    - CVE-2024-25739: Fixed possible crash in create_empty_lvol() in drivers/mtd/ubi/vtbl.c (bsc#1219834).
    - CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).
    - CVE-2024-36030: Fix the double free in rvu_npc_freemem() (bsc#1225712)
    - CVE-2023-52698: Fix memory leak in netlbl_calipso_add_pass() (bsc#1224621)
    - CVE-2024-26860: Fix a memory leak when rechecking the data (bsc#1223077).
    - CVE-2023-52772: Fix use-after-free in unix_stream_read_actor() (bsc#1224989).
    - CVE-2024-27431: Zero-initialise xdp_rxq_info struct before running XDP program (bsc#1224718).
    - CVE-2024-35860: Support deferring bpf_link dealloc to after RCU grace period BPF link for some program     types (bsc#1224531).
    - CVE-2024-35964: Fix not validating setsockopt user input Check user input length before copying data     (bsc#1224581).
    - CVE-2023-0160: Prevent lock inversion deadlock in map delete elem  (bsc#1209657).
    - CVE-2024-35903: Fix IP after emitting call depth accounting Adjust the IP passed to `emit_patch` so it     calculates the correct offset for the CALL instruction if `x86_call_depth_emit_accounting` emits code     (bsc#1224493).
    - CVE-2024-35931: Skip do PCI error slot reset during RAS recovery (bsc#1224652).
    - CVE-2024-35877: Fix VM_PAT handling in COW mappings (bsc#1224525).
    - CVE-2024-35969: Fix race condition between ipv6_get_ifaddr and ipv6_del_addr (bsc#1224580)
    - CVE-2024-35852: Fix memory leak when canceling rehash work The rehash delayed work is rescheduled with a     delay if the number of credits at end of the work is not negative as supposedly it means that the     migration ended (bsc#1224502).
    - CVE-2024-36006: Fix incorrect list API usage (bsc#1224541).
    - CVE-2024-36007: Fix warning during rehash (bsc#1224543).
    - CVE-2024-35872: Fix GUP-fast succeeding on secretmem folios (bsc#1224530).
    - CVE-2024-35956: Fix qgroup prealloc rsv leak in subvolume operations (bsc#1224674)
    - CVE-2023-52771: Fix delete_endpoint() vs parent unregistration race  (bsc#1225007).
    - CVE-2024-27408: Add sync read before starting the  DMA transfer in remote setup (bsc#1224430).
    - CVE-2024-35943: Add a null pointer check to the omap_prm_domain_init devm_kasprintf()returns a pointer     to dynamically allocated memory which can be NULL upon failure (bsc#1224649).
    - CVE-2024-35921: Fix oops when HEVC init fails (bsc#1224477).
    - CVE-2023-52860: Use cpuhp_state_remove_instance_nocalls() for hisi_hns3_pmu uninit process     (bsc#1224936).
    - CVE-2024-35991: kABI workaround for struct idxd_evl (bsc#1224553).
    - CVE-2024-35854: Fix possible use-after-free during rehash (bsc#1224636).
    - CVE-2024-27418: Take ownership of skb in mctp_local_output (bsc#1224720)
    - CVE-2024-27417: Fix potential 'struct net' leak in inet6_rtm_getaddr() (bsc#1224721).
    - CVE-2024-35905: Protect against int overflow for stack access size (bsc#1224488).
    - CVE-2024-35917: Fix bpf_plt pointer arithmetic (bsc#1224481).
    - CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put() to nsure the value passed to     scarlett2_mixer_ctl_put() is between 0 and SCARLETT2_MIXER_MAX_VALUE so we don't attempt to access outside     scarlett2_mixer_values[] (bsc#1224727).
    - CVE-2023-52680: Add missing error checks to *_ctl_get() because the *_ctl_get() functions which call     scarlett2_update_*() were not checking the return value (bsc#1224608).
    - CVE-2023-52692: Add missing error check to scarlett2_usb_set_config() scarlett2_usb_set_config() calls     scarlett2_usb_get() but was not checking the result (bsc#1224628).
    - CVE-2024-35944: Fix memcpy() run-time warning in dg_dispatch_as_host() Syzkaller hit 'WARNING in     dg_dispatch_as_host' bug (bsc#1224648).
    - CVE-2024-26923: Suppress false-positive lockdep splat for spin_lock()  in __unix_gc() (bsc#1223384).
    - CVE-2023-52659: Ensure input to pfn_to_kaddr() is treated as a 64-bit type (bsc#1224442).
    - CVE-2024-21823: Hardware logic with insecure de-synchronization in Intel(R) DSA and Intel(R) IAA for     some Intel(R) 4th or 5th generation Xeon(R) processors may have allowed an authorized user to potentially     enable denial of service via local access (bsc#1223625).
    - CVE-2024-26828: Fix underflow in parse_server_interfaces() (bsc#1223084).
    - CVE-2024-27395: Fix Use-After-Free in ovs_ct_exit Since kfree_rcu (bsc#1224098).
    - CVE-2023-52483: Perform route lookups under a RCU read-side lock (bsc#1220738).
    - CVE-2024-27396: Fix Use-After-Free in gtp_dellink (bsc#1224096).
    - CVE-2024-26632: Fix iterating over an empty bio with  bio_for_each_folio_all (bsc#1221635).
    - CVE-2024-27401: Ensure that packet_buffer_get respects the user_length provided. (bsc#1224181).
    - CVE-2024-26775: Avoid potential deadlock at set_capacity (bsc#1222627).
    - CVE-2024-26958: Fix UAF in direct writes (bsc#1223653).
    - CVE-2024-26643: Mark set as dead when unbinding anonymous set with timeout While the rhashtable set gc     runs asynchronously, a race allowed it to collect elements from anonymous sets with timeouts while it is     being released from the commit path. (bsc#1221829).
    - CVE-2023-52618: Check for unlikely string overflow (bsc#1221615).
    - CVE-2023-6238: Only privileged user could specify a small meta buffer and let the device perform larger     Direct Memory Access (DMA) into the same buffer, overwriting unrelated kernel memory, causing random     kernel crashes and memory corruption (bsc#1217384).
    - CVE-2024-26946: Use copy_from_kernel_nofault() to read from unsafe address Read from an unsafe address     with copy_from_kernel_nofault() in arch_adjust_kprobe_addr() because this function is used before checking     the address is in text or not (bsc#1223669).
    - CVE-2024-26945: Fix nr_cpus nr_iaa case If nr_cpus nr_iaa, the calculated cpus_per_iaa will be 0, which     causes a divide-by-0 in rebalance_wq_table() (bsc#1223732).
    - CVE-2024-26679: Read sk->sk_family once in inet_recv_error() inet_recv_error() is called without holding     the socket lock. IPv6 socket could mutate to IPv4 with IPV6_ADDRFORM socket option and trigger a KCSAN     warning (bsc#1222385).
    - CVE-2024-26791: Properly validate device names (bsc#1222793)
    - CVE-2023-52641: Add NULL ptr dereference checking at the end of attr_allocate_frame() (bsc#1222303)
    - CVE-2024-26726: Do not drop extent_map for free space inode on write error (bsc#1222532)
    - CVE-2024-27022: Defer linking file vma until vma is fully initialized (bsc#1223774).
    - CVE-2024-26899: Fix deadlock between bd_link_disk_holder and partition scan (bsc#1223045).
    - CVE-2024-26638: Always initialize struct msghdr completely (bsc#1221649).
    - CVE-2024-26909: Fix drm bridge use-after-free A recent DRM series purporting to simplify support     (bsc#1223143).
    - CVE-2024-26674: Revert to _ASM_EXTABLE_UA() for {get,put}_user() fixups (bsc#1222378).
    - CVE-2024-26832: Fix missing folio cleanup in writeback race path (bsc#1223007).
    - CVE-2024-26844: Fix WARNING in _copy_from_iter (bsc#1223015).
    - CVE-2024-26774: Avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt     (bsc#1222622).
    - CVE-2024-26815: Properly check TCA_TAPRIO_TC_ENTRY_INDEX (bsc#1222635).
    - cve-2024-267600: Fix bio_put() for error case (bsc#1222596).
    - CVE-2024-26731: Fix NULL pointer dereference in sk_psock_verdict_data_ready() (bsc#1222371).
    - CVE-2024-26740: Use the backlog for mirred ingress (bsc#1222563).
    - CVE-2023-52640: Fix oob in ntfs_listxattr The length of name cannot exceed the space occupied by ea     (bsc#1222301).
    - CVE-2023-52631: Fix a NULL dereference bug (bsc#1222264).
    - CVE-2023-52458: Add check that partition length needs to be aligned  with block size (bsc#1220428).
    - CVE-2023-6270: Fix the potential use-after-free problem in aoecmd_cfg_pkts  (bsc#1218562).
    - CVE-2024-26805: Fix kernel-infoleak-after-free in __skb_datagram_iter (bsc#1222630).
    - CVE-2024-26991: Do not overflow lpage_info when checking attributes (bsc#1223695).

    - CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).
    - CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).
    - CVE-2024-26822: Set correct id, uid and cruid for multiuser  automounts (bsc#1223011).
    - CVE-2023-52434: Fixed potential OOBs in smb2_parse_contexts()  (bsc#1220148).
    - CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).
    - CVE-2024-35999: Fixed missing lock when picking channel (bsc#1224550).
    - CVE-2024-35861: Fixed potential UAF in  cifs_signal_cifsd_for_reconnect() (bsc#1224766).
    - CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted()  (bsc#1224764).
    - CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763).
    - CVE-2024-35865: Fixed potential UAF in smb2_is_valid_oplock_break()  (bsc#1224668).
    - CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break()  (bsc#1224765).
    - CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664).
    - CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678).
    - CVE-2024-35866: Fixed potential UAF in cifs_dump_full_key()  (bsc#1224667).
    - CVE-2024-35869: Guarantee refcounted children from parent session  (bsc#1224679).
    - CVE-2024-35870: Fixed UAF in smb2_reconnect_server() (bsc#1224672).
    - CVE-2024-26692: Fixed regression in writes when non-standard maximum write  size negotiated     (bsc#1222464).
    - CVE-2024-27036: Fixed writeback data corruption (bsc#1223810).


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

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

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

    The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with     extremely high determinism requirements.

    Security Fix(es):

    * kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)

    * kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)

    * kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)

    * kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)

    * kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)

    * kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)

    * kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)

    * kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)

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

    * kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by     untrusted application (CVE-2024-21823)

    * kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)

    * kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)

    * kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)

    * kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)

    * kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)

    * kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)

    * kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)

    * kernel: Revert net/mlx5: Block entering switchdev mode with ns inconsistency (CVE-2023-52658)

    * kernel: crash due to a missing check for leb_size (CVE-2024-25739)

    * kernel: tcp: make sure init the accept_queue's spinlocks once (CVE-2024-26614)

    * kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)

    * kernel: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (CVE-2024-26870)

    * kernel: nfs: fix UAF in direct writes (CVE-2024-26958)

    * kernel: SUNRPC: fix some memleaks in gssx_dec_option_array (CVE-2024-27388)

    * kernel: wifi: iwlwifi: mvm: don't set the MFP flag for the GTK (CVE-2024-27434)

    * kernel: of: Fix double free in of_parse_phandle_with_args_map (CVE-2023-52679)

    * kernel: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (CVE-2024-35930)

    * kernel: wifi: iwlwifi: mvm: rfi: fix potential response leaks (CVE-2024-35912)

    * kernel: block: prevent division by zero in blk_rq_stat_sum() (CVE-2024-35925)

    * kernel: wifi: ath11k: decrease MHI channel buffer length to 8KB (CVE-2024-35938)

    * kernel: wifi: cfg80211: check A-MSDU format more carefully (CVE-2024-35937)

    * kernel: wifi: rtw89: fix null pointer access when abort scan (CVE-2024-35946)

    * kernel: netfilter: nf_tables: honor table dormant flag from netdev release event path (CVE-2024-36005)

    * kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)

    * kernel: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage (CVE-2024-36006)

    * kernel: net: ieee802154: fix null deref in parse dev addr (CVE-2021-47257)

    * kernel: mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)

    * kernel: wifi: ath11k: fix gtk offload status event locking (CVE-2023-52777)

    * (CVE-2023-52832)
    * (CVE-2023-52803)
    * (CVE-2023-52756)
    * (CVE-2023-52834)
    * (CVE-2023-52791)
    * (CVE-2023-52764)
    * (CVE-2021-47468)
    * (CVE-2021-47284)
    * (CVE-2024-36025)
    * (CVE-2024-36941)
    * (CVE-2024-36940)
    * (CVE-2024-36904)
    * (CVE-2024-36896)
    * (CVE-2024-36954)
    * (CVE-2024-36950)
    * (CVE-2024-38575)
    * (CVE-2024-36917)
    * (CVE-2024-36016)
    * (CVE-2023-52762)
    * (CVE-2024-27025)
    * (CVE-2021-47548)
    * (CVE-2023-52619)

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

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

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

ID	Name	Product	Family	Published	Updated	Severity
306972	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-007259)	Nessus	Unity Linux Local Security Checks	4/17/2026	4/21/2026	medium
202689	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6898-3)	Nessus	Ubuntu Local Security Checks	7/19/2024	12/31/2024	high
204313	Photon OS 4.0: Linux PHSA-2024-4.0-0607	Nessus	PhotonOS Local Security Checks	7/24/2024	3/3/2026	high
205698	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2024-068)	Nessus	Amazon Linux Local Security Checks	8/17/2024	2/26/2026	high
204793	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6917-1)	Nessus	Ubuntu Local Security Checks	7/26/2024	6/3/2026	high
227879	Linux Distros Unpatched Vulnerability : CVE-2024-26960	Nessus	Misc.	3/5/2025	7/17/2026	medium
204159	Photon OS 5.0: Linux PHSA-2024-5.0-0274	Nessus	PhotonOS Local Security Checks	7/24/2024	7/22/2026	high
200853	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:2135-1)	Nessus	SuSE Local Security Checks	6/22/2024	9/24/2025	high
205212	RHEL 8 : kernel-rt (RHSA-2024:5102)	Nessus	Red Hat Local Security Checks	8/8/2024	9/24/2025	high
202513	EulerOS 2.0 SP9 : kernel (EulerOS-SA-2024-1937)	Nessus	Huawei Local Security Checks	7/16/2024	9/25/2025	high

Detections

Analytics

Plugins Search

medium

high

high

high

high

medium

high

high

high

high