In the Linux kernel, the following vulnerability has been resolved: x86/efistub: Call mixed mode boot services on the firmware's stack Normally, the EFI stub calls into the EFI boot services using the stack that was live when the stub was entered. According to the UEFI spec, this stack needs to be at least 128k in size - this might seem large but all asynchronous processing and event handling in EFI runs from the same stack and so quite a lot of space may be used in practice. In mixed mode, the situation is a bit different: the bootloader calls the 32-bit EFI stub entry point, which calls the decompressor's 32-bit entry point, where the boot stack is set up, using a fixed allocation of 16k. This stack is still in use when the EFI stub is started in 64-bit mode, and so all calls back into the EFI firmware will be using the decompressor's limited boot stack. Due to the placement of the boot stack right after the boot heap, any stack overruns have gone unnoticed. However, commit 5c4feadb0011983b ("x86/decompressor: Move global symbol references to C code") moved the definition of the boot heap into C code, and now the boot stack is placed right at the base of BSS, where any overruns will corrupt the end of the .data section. While it would be possible to work around this by increasing the size of the boot stack, doing so would affect all x86 systems, and mixed mode systems are a tiny (and shrinking) fraction of the x86 installed base. So instead, record the firmware stack pointer value when entering from the 32-bit firmware, and switch to this stack every time a EFI boot service call is made.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

An update of the linux package has been released.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Red Hat Enterprise Linux - kernel: x86/efistub: Call mixed mode boot services on the firmware's stack     Ubuntu Linux - x86/efistub: Call mixed mode boot services on the firmware's stack Normally, the EFI stub     calls into the EFI boot services using the stack that was live when the stub was entered. According to the     UEFI spec, this stack needs to be at least 128k in size - this might seem large but all asynchronous     processing and event handling in EFI runs from the same stack and so quite a lot of space may be used in     practice. In mixed mode, the situation is a bit different: the bootloader calls the 32-bit EFI stub entry     point, which calls the decompressor's 32-bit entry point, where the boot stack is set up, using a fixed     allocation of 16k. This stack is still in use when the EFI stub is started in 64-bit mode, and so all     calls back into the EFI firmware will be using the decompressor's limited boot stack. Due to the placement     of the boot stack right after the boot heap, any stack overruns have gone unnoticed. However, commit     5c4feadb0011983b (x86/decompressor: Move global symbol references to C code) moved the definition of the     boot heap into C code, and now the boot stack is placed right at the base of BSS, where any overruns will     corrupt the end of the .data section. While it would be possible to work around this by increasing the     size of the boot stack, doing so would affect all x86 systems, and mixed mode systems are a tiny (and     shrinking) fraction of the x86 installed base. So instead, record the firmware stack pointer value when     entering from the 32-bit firmware, and switch to this stack every time a EFI boot service call is made.
    (CVE-2024-35803)

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

The remote Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-6878-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)

    Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition     during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could     possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    It was discovered that the Intel Data Streaming and Intel Analytics Accelerator drivers in the Linux     kernel allowed direct access to the devices for unprivileged users and virtual machines. A local attacker     could use this to cause a denial of service. (CVE-2024-21823)

    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)

    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:

    - ARM32 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Cryptographic API;

    - DPLL subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - GPU drivers;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - MMC subsystem;

    - Network drivers;

    - NTB driver;

    - NVME drivers;

    - PCI subsystem;

    - Powercap sysfs driver;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Backlight driver;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - debug file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - Network file system client;

    - NILFS2 file system;

    - Overlay file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Packet sockets;

    - Network traffic control;

    - Sun RPC protocol;

    - ALSA SH drivers;

    - SOF drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-27032, CVE-2024-26868, CVE-2024-26879, CVE-2024-27033, CVE-2024-26943,     CVE-2024-27040, CVE-2024-26950, CVE-2023-52650, CVE-2023-52649, CVE-2023-52644, CVE-2024-26899,     CVE-2024-27432, CVE-2024-35806, CVE-2024-26871, CVE-2024-35845, CVE-2024-35799, CVE-2024-26945,     CVE-2024-35805, CVE-2024-27041, CVE-2024-26860, CVE-2024-26930, CVE-2024-26941, CVE-2024-26960,     CVE-2024-27034, CVE-2024-26891, CVE-2024-35793, CVE-2024-26963, CVE-2024-27029, CVE-2024-26890,     CVE-2024-27074, CVE-2024-27079, CVE-2024-27053, CVE-2024-27070, CVE-2024-35821, CVE-2024-27067,     CVE-2024-27051, CVE-2024-27026, CVE-2024-26961, CVE-2024-27050, CVE-2024-26939, CVE-2024-26897,     CVE-2024-26878, CVE-2024-27433, CVE-2024-26885, CVE-2024-35810, CVE-2024-35829, CVE-2024-26965,     CVE-2024-26875, CVE-2024-26966, CVE-2024-27078, CVE-2024-35874, CVE-2023-52661, CVE-2024-35794,     CVE-2024-35787, CVE-2024-26874, CVE-2024-27054, CVE-2024-26940, CVE-2024-26859, CVE-2024-27044,     CVE-2024-26948, CVE-2024-26882, CVE-2023-52653, CVE-2024-27071, CVE-2024-27065, CVE-2024-26877,     CVE-2024-26929, CVE-2024-27064, CVE-2024-35803, CVE-2024-27066, CVE-2024-27028, CVE-2024-27072,     CVE-2024-26876, CVE-2024-27039, CVE-2024-27435, CVE-2024-27434, CVE-2024-26812, CVE-2024-27030,     CVE-2024-26816, CVE-2024-26873, CVE-2024-35808, CVE-2024-27389, CVE-2024-27075, CVE-2024-27038,     CVE-2024-35828, CVE-2024-26946, CVE-2024-26655, CVE-2023-52662, CVE-2024-27077, CVE-2024-27076,     CVE-2024-35795, CVE-2024-26933, CVE-2024-35789, CVE-2024-26972, CVE-2023-52663, CVE-2024-27031,     CVE-2024-27069, CVE-2024-26813, CVE-2023-52659, CVE-2024-26862, CVE-2024-26962, CVE-2024-26654,     CVE-2024-26815, CVE-2024-26978, CVE-2024-26976, CVE-2024-26893, CVE-2024-35809, CVE-2024-27027,     CVE-2024-26864, CVE-2024-27048, CVE-2024-27046, CVE-2024-26869, CVE-2024-35827, CVE-2024-26951,     CVE-2024-26942, CVE-2024-26870, CVE-2024-27437, CVE-2024-26931, CVE-2024-27036, CVE-2022-48669,     CVE-2024-26898, CVE-2024-26970, CVE-2024-26886, CVE-2024-26944, CVE-2024-26865, CVE-2024-26896,     CVE-2024-26895, CVE-2024-26947, CVE-2024-26880, CVE-2024-35811, CVE-2024-26975, CVE-2024-27391,     CVE-2024-35796, CVE-2024-27043, CVE-2024-26949, CVE-2024-26653, CVE-2024-35814, CVE-2024-26964,     CVE-2023-52652, CVE-2024-27047, CVE-2024-35830, CVE-2024-26900, CVE-2024-26810, CVE-2024-26956,     CVE-2024-35817, CVE-2024-26887, CVE-2024-26809, CVE-2024-27045, CVE-2024-26656, CVE-2024-26971,     CVE-2024-26866, CVE-2024-26861, CVE-2024-26968, CVE-2024-26881, CVE-2024-27063, CVE-2024-35807,     CVE-2024-35797, CVE-2024-35822, CVE-2024-35813, CVE-2024-27073, CVE-2024-26954, CVE-2024-26888,     CVE-2024-26955, CVE-2024-26894, CVE-2024-35844, CVE-2024-26958, CVE-2024-26952, CVE-2024-35798,     CVE-2024-26969, CVE-2024-26967, CVE-2024-35800, CVE-2024-35819, CVE-2024-26937, CVE-2024-26927,     CVE-2024-26883, CVE-2024-26934, CVE-2024-27392, CVE-2024-27068, CVE-2024-26889, CVE-2024-26892,     CVE-2024-27390, CVE-2024-26657, CVE-2024-27388, CVE-2024-27049, CVE-2024-26935, CVE-2024-35831,     CVE-2024-26884, CVE-2024-26938, CVE-2024-27037, CVE-2024-26977, CVE-2024-26953, CVE-2024-26973,     CVE-2024-26932, CVE-2024-26901, CVE-2024-35843, CVE-2024-26872, CVE-2024-26959, CVE-2024-27035,     CVE-2024-35826, CVE-2024-27436, CVE-2024-26651, CVE-2024-26957, CVE-2024-26863, CVE-2024-27042,     CVE-2024-26814, CVE-2023-52647, CVE-2024-27080, CVE-2024-27052, CVE-2024-27058, CVE-2024-35801,     CVE-2023-52648)

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

    Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition     during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could     possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    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)

    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)

    It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race     condition when stopping the device. A local attacker could possibly use this to cause a denial of service     (device unavailability). (CVE-2024-27432)

    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;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Cryptographic API;

    - DPLL subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - GPU drivers;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - MMC subsystem;

    - Network drivers;

    - NTB driver;

    - NVME drivers;

    - PCI subsystem;

    - Powercap sysfs driver;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Backlight driver;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - debug file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - Network file system client;

    - NILFS2 file system;

    - Overlay file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - Memory management;

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Packet sockets;

    - Network traffic control;

    - Sun RPC protocol;

    - ALSA SH drivers;

    - SOF drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-26859, CVE-2024-26944, CVE-2024-27049, CVE-2024-26868, CVE-2024-26932,     CVE-2024-35843, CVE-2024-35814, CVE-2024-26866, CVE-2024-26941, CVE-2024-27080, CVE-2024-26938,     CVE-2024-26889, CVE-2024-27075, CVE-2024-27077, CVE-2024-26864, CVE-2024-35787, CVE-2024-27071,     CVE-2024-26880, CVE-2024-26961, CVE-2024-26945, CVE-2024-26863, CVE-2024-35795, CVE-2024-27045,     CVE-2024-27066, CVE-2024-27046, CVE-2024-26816, CVE-2024-27069, CVE-2024-26861, CVE-2024-26968,     CVE-2024-26963, CVE-2024-26878, CVE-2024-27073, CVE-2024-35806, CVE-2024-26951, CVE-2024-26954,     CVE-2024-27026, CVE-2024-26956, CVE-2024-35811, CVE-2024-35803, CVE-2024-26964, CVE-2024-26848,     CVE-2024-27434, CVE-2024-35844, CVE-2024-26977, CVE-2024-27031, CVE-2024-35813, CVE-2024-26960,     CVE-2024-27067, CVE-2024-26937, CVE-2024-26884, CVE-2024-26656, CVE-2024-27068, CVE-2024-26871,     CVE-2023-52653, CVE-2024-26939, CVE-2024-26967, CVE-2024-26966, CVE-2024-27043, CVE-2024-26814,     CVE-2024-35829, CVE-2024-26973, CVE-2024-35810, CVE-2024-26877, CVE-2024-27392, CVE-2024-35805,     CVE-2024-26875, CVE-2024-26970, CVE-2024-26657, CVE-2024-26874, CVE-2024-26971, CVE-2024-26872,     CVE-2024-35798, CVE-2024-26931, CVE-2024-26948, CVE-2024-26883, CVE-2024-26955, CVE-2024-27039,     CVE-2024-27038, CVE-2024-27065, CVE-2024-26899, CVE-2024-27048, CVE-2024-35874, CVE-2024-35845,     CVE-2024-35799, CVE-2024-35827, CVE-2024-26935, CVE-2024-27079, CVE-2024-35821, CVE-2024-26950,     CVE-2024-26879, CVE-2024-26940, CVE-2024-35788, CVE-2024-26891, CVE-2024-27063, CVE-2024-27433,     CVE-2024-27036, CVE-2024-35819, CVE-2024-26969, CVE-2024-27044, CVE-2024-27028, CVE-2024-27070,     CVE-2023-52649, CVE-2024-27435, CVE-2024-35830, CVE-2024-26929, CVE-2024-26653, CVE-2024-26887,     CVE-2024-26869, CVE-2024-26942, CVE-2024-35822, CVE-2024-26979, CVE-2024-26881, CVE-2024-26655,     CVE-2024-26975, CVE-2023-52650, CVE-2024-26651, CVE-2024-35828, CVE-2024-26965, CVE-2024-27437,     CVE-2024-35794, CVE-2024-26962, CVE-2024-27058, CVE-2024-27076, CVE-2024-27035, CVE-2024-27074,     CVE-2024-27027, CVE-2024-26860, CVE-2024-27042, CVE-2024-27390, CVE-2024-26815, CVE-2023-52662,     CVE-2024-27051, CVE-2024-35796, CVE-2024-27047, CVE-2024-26930, CVE-2024-26865, CVE-2024-27064,     CVE-2024-35826, CVE-2024-26885, CVE-2024-26873, CVE-2024-26943, CVE-2024-26893, CVE-2024-27030,     CVE-2024-26976, CVE-2024-35793, CVE-2024-26952, CVE-2023-52644, CVE-2024-35797, CVE-2024-27029,     CVE-2024-26927, CVE-2024-26812, CVE-2024-27432, CVE-2024-26897, CVE-2024-26890, CVE-2024-26972,     CVE-2024-35800, CVE-2024-27032, CVE-2024-27052, CVE-2023-52647, CVE-2024-26898, CVE-2023-52652,     CVE-2024-35808, CVE-2024-26876, CVE-2024-26933, CVE-2024-26862, CVE-2024-27033, CVE-2023-52663,     CVE-2024-27041, CVE-2023-52648, CVE-2024-26888, CVE-2024-26957, CVE-2024-26953, CVE-2023-52659,     CVE-2024-27436, CVE-2024-27040, CVE-2024-27054, CVE-2024-27050, CVE-2024-26886, CVE-2023-52661,     CVE-2024-35831, CVE-2024-26946, CVE-2024-26949, CVE-2024-26809, CVE-2024-26892, CVE-2024-26654,     CVE-2024-26901, CVE-2024-27053, CVE-2024-26882, CVE-2024-35809, CVE-2024-26978, CVE-2024-27037,     CVE-2024-27391, CVE-2024-27034, CVE-2024-26895, CVE-2024-35817, CVE-2024-26900, CVE-2024-26896,     CVE-2024-26958, CVE-2024-35801, CVE-2024-27388, CVE-2024-26934, CVE-2024-27078, CVE-2024-35789,     CVE-2024-26894, CVE-2024-27389, CVE-2024-35807, CVE-2024-27072, CVE-2024-26947, CVE-2024-26870,     CVE-2024-26813, CVE-2022-48669, CVE-2024-26959, CVE-2024-26810)

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 Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-6817-2 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)

    Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition     during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could     possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    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)

    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)

    It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race     condition when stopping the device. A local attacker could possibly use this to cause a denial of service     (device unavailability). (CVE-2024-27432)

    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;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Cryptographic API;

    - DPLL subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - GPU drivers;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - MMC subsystem;

    - Network drivers;

    - NTB driver;

    - NVME drivers;

    - PCI subsystem;

    - Powercap sysfs driver;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Backlight driver;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - debug file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - Network file system client;

    - NILFS2 file system;

    - Overlay file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - Memory management;

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Packet sockets;

    - Network traffic control;

    - Sun RPC protocol;

    - ALSA SH drivers;

    - SOF drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-26859, CVE-2024-26944, CVE-2024-27049, CVE-2024-26868, CVE-2024-26932,     CVE-2024-35843, CVE-2024-35814, CVE-2024-26866, CVE-2024-26941, CVE-2024-27080, CVE-2024-26938,     CVE-2024-26889, CVE-2024-27075, CVE-2024-27077, CVE-2024-26864, CVE-2024-35787, CVE-2024-27071,     CVE-2024-26880, CVE-2024-26961, CVE-2024-26945, CVE-2024-26863, CVE-2024-35795, CVE-2024-27045,     CVE-2024-27066, CVE-2024-27046, CVE-2024-26816, CVE-2024-27069, CVE-2024-26861, CVE-2024-26968,     CVE-2024-26963, CVE-2024-26878, CVE-2024-27073, CVE-2024-35806, CVE-2024-26951, CVE-2024-26954,     CVE-2024-27026, CVE-2024-26956, CVE-2024-35811, CVE-2024-35803, CVE-2024-26964, CVE-2024-26848,     CVE-2024-27434, CVE-2024-35844, CVE-2024-26977, CVE-2024-27031, CVE-2024-35813, CVE-2024-26960,     CVE-2024-27067, CVE-2024-26937, CVE-2024-26884, CVE-2024-26656, CVE-2024-27068, CVE-2024-26871,     CVE-2023-52653, CVE-2024-26939, CVE-2024-26967, CVE-2024-26966, CVE-2024-27043, CVE-2024-26814,     CVE-2024-35829, CVE-2024-26973, CVE-2024-35810, CVE-2024-26877, CVE-2024-27392, CVE-2024-35805,     CVE-2024-26875, CVE-2024-26970, CVE-2024-26657, CVE-2024-26874, CVE-2024-26971, CVE-2024-26872,     CVE-2024-35798, CVE-2024-26931, CVE-2024-26948, CVE-2024-26883, CVE-2024-26955, CVE-2024-27039,     CVE-2024-27038, CVE-2024-27065, CVE-2024-26899, CVE-2024-27048, CVE-2024-35874, CVE-2024-35845,     CVE-2024-35799, CVE-2024-35827, CVE-2024-26935, CVE-2024-27079, CVE-2024-35821, CVE-2024-26950,     CVE-2024-26879, CVE-2024-26940, CVE-2024-35788, CVE-2024-26891, CVE-2024-27063, CVE-2024-27433,     CVE-2024-27036, CVE-2024-35819, CVE-2024-26969, CVE-2024-27044, CVE-2024-27028, CVE-2024-27070,     CVE-2023-52649, CVE-2024-27435, CVE-2024-35830, CVE-2024-26929, CVE-2024-26653, CVE-2024-26887,     CVE-2024-26869, CVE-2024-26942, CVE-2024-35822, CVE-2024-26979, CVE-2024-26881, CVE-2024-26655,     CVE-2024-26975, CVE-2023-52650, CVE-2024-26651, CVE-2024-35828, CVE-2024-26965, CVE-2024-27437,     CVE-2024-35794, CVE-2024-26962, CVE-2024-27058, CVE-2024-27076, CVE-2024-27035, CVE-2024-27074,     CVE-2024-27027, CVE-2024-26860, CVE-2024-27042, CVE-2024-27390, CVE-2024-26815, CVE-2023-52662,     CVE-2024-27051, CVE-2024-35796, CVE-2024-27047, CVE-2024-26930, CVE-2024-26865, CVE-2024-27064,     CVE-2024-35826, CVE-2024-26885, CVE-2024-26873, CVE-2024-26943, CVE-2024-26893, CVE-2024-27030,     CVE-2024-26976, CVE-2024-35793, CVE-2024-26952, CVE-2023-52644, CVE-2024-35797, CVE-2024-27029,     CVE-2024-26927, CVE-2024-26812, CVE-2024-27432, CVE-2024-26897, CVE-2024-26890, CVE-2024-26972,     CVE-2024-35800, CVE-2024-27032, CVE-2024-27052, CVE-2023-52647, CVE-2024-26898, CVE-2023-52652,     CVE-2024-35808, CVE-2024-26876, CVE-2024-26933, CVE-2024-26862, CVE-2024-27033, CVE-2023-52663,     CVE-2024-27041, CVE-2023-52648, CVE-2024-26888, CVE-2024-26957, CVE-2024-26953, CVE-2023-52659,     CVE-2024-27436, CVE-2024-27040, CVE-2024-27054, CVE-2024-27050, CVE-2024-26886, CVE-2023-52661,     CVE-2024-35831, CVE-2024-26946, CVE-2024-26949, CVE-2024-26809, CVE-2024-26892, CVE-2024-26654,     CVE-2024-26901, CVE-2024-27053, CVE-2024-26882, CVE-2024-35809, CVE-2024-26978, CVE-2024-27037,     CVE-2024-27391, CVE-2024-27034, CVE-2024-26895, CVE-2024-35817, CVE-2024-26900, CVE-2024-26896,     CVE-2024-26958, CVE-2024-35801, CVE-2024-27388, CVE-2024-26934, CVE-2024-27078, CVE-2024-35789,     CVE-2024-26894, CVE-2024-27389, CVE-2024-35807, CVE-2024-27072, CVE-2024-26947, CVE-2024-26870,     CVE-2024-26813, CVE-2022-48669, CVE-2024-26959, CVE-2024-26810)

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

    Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition     during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could     possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    It was discovered that the Intel Data Streaming and Intel Analytics Accelerator drivers in the Linux     kernel allowed direct access to the devices for unprivileged users and virtual machines. A local attacker     could use this to cause a denial of service. (CVE-2024-21823)

    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)

    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)

    It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race     condition when stopping the device. A local attacker could possibly use this to cause a denial of service     (device unavailability). (CVE-2024-27432)

    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;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Cryptographic API;

    - DPLL subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - GPU drivers;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - MMC subsystem;

    - Network drivers;

    - NTB driver;

    - NVME drivers;

    - PCI subsystem;

    - Powercap sysfs driver;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Backlight driver;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - debug file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - Network file system client;

    - NILFS2 file system;

    - Overlay file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - Memory management;

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Packet sockets;

    - Network traffic control;

    - Sun RPC protocol;

    - ALSA SH drivers;

    - SOF drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-35822, CVE-2024-26859, CVE-2024-26967, CVE-2024-27053, CVE-2024-27064,     CVE-2024-27437, CVE-2024-26931, CVE-2024-26870, CVE-2024-26927, CVE-2024-26880, CVE-2024-35789,     CVE-2024-26929, CVE-2024-27034, CVE-2024-26816, CVE-2024-26896, CVE-2024-26975, CVE-2024-26972,     CVE-2024-26937, CVE-2024-27032, CVE-2024-26871, CVE-2024-26655, CVE-2024-35829, CVE-2024-26886,     CVE-2023-52653, CVE-2024-27028, CVE-2024-26877, CVE-2024-26898, CVE-2024-35796, CVE-2024-27065,     CVE-2024-35807, CVE-2024-26966, CVE-2024-35826, CVE-2024-27067, CVE-2024-27039, CVE-2024-35811,     CVE-2024-26895, CVE-2024-26814, CVE-2024-26893, CVE-2023-52649, CVE-2024-35801, CVE-2023-52648,     CVE-2024-27048, CVE-2024-26934, CVE-2024-27049, CVE-2024-26890, CVE-2024-26874, CVE-2022-48669,     CVE-2023-52661, CVE-2024-27436, CVE-2024-27058, CVE-2024-26935, CVE-2024-26956, CVE-2024-26960,     CVE-2024-26976, CVE-2024-27041, CVE-2024-26873, CVE-2024-26946, CVE-2024-27080, CVE-2024-27432,     CVE-2023-52650, CVE-2024-26879, CVE-2023-52647, CVE-2024-27435, CVE-2024-27038, CVE-2024-26951,     CVE-2024-27390, CVE-2024-26863, CVE-2024-26959, CVE-2024-35794, CVE-2024-26889, CVE-2024-35845,     CVE-2024-27433, CVE-2024-26961, CVE-2024-35803, CVE-2024-26653, CVE-2024-26939, CVE-2024-26872,     CVE-2024-26979, CVE-2024-26973, CVE-2024-27029, CVE-2024-35831, CVE-2024-26892, CVE-2024-26888,     CVE-2024-27074, CVE-2024-35844, CVE-2024-26938, CVE-2024-26953, CVE-2024-27391, CVE-2024-35843,     CVE-2024-27040, CVE-2024-26875, CVE-2024-27026, CVE-2024-26978, CVE-2024-26882, CVE-2023-52652,     CVE-2023-52662, CVE-2024-26963, CVE-2024-26962, CVE-2024-27051, CVE-2024-27068, CVE-2024-26881,     CVE-2024-35800, CVE-2024-26964, CVE-2024-27389, CVE-2024-27043, CVE-2024-26901, CVE-2024-26941,     CVE-2024-35798, CVE-2024-35799, CVE-2024-26952, CVE-2024-26654, CVE-2024-27046, CVE-2024-35810,     CVE-2024-27050, CVE-2024-27063, CVE-2024-26954, CVE-2024-26884, CVE-2024-27047, CVE-2024-26932,     CVE-2024-26883, CVE-2024-26943, CVE-2024-26651, CVE-2024-26815, CVE-2024-26948, CVE-2024-27066,     CVE-2024-27037, CVE-2024-35806, CVE-2024-26869, CVE-2024-26878, CVE-2024-26810, CVE-2024-35797,     CVE-2024-27073, CVE-2024-26812, CVE-2024-26933, CVE-2024-26809, CVE-2024-26894, CVE-2024-35813,     CVE-2024-27033, CVE-2024-26876, CVE-2024-27076, CVE-2024-27045, CVE-2024-27079, CVE-2024-26861,     CVE-2024-26957, CVE-2024-26864, CVE-2024-26866, CVE-2024-35814, CVE-2024-26813, CVE-2024-27388,     CVE-2024-27042, CVE-2024-26862, CVE-2024-26968, CVE-2024-26940, CVE-2024-27027, CVE-2024-35793,     CVE-2024-35874, CVE-2024-27035, CVE-2024-26958, CVE-2024-26887, CVE-2024-35809, CVE-2024-26930,     CVE-2024-35819, CVE-2024-27392, CVE-2024-35808, CVE-2023-52644, CVE-2024-35828, CVE-2024-26657,     CVE-2024-26969, CVE-2024-27434, CVE-2024-35821, CVE-2023-52663, CVE-2024-27078, CVE-2024-35787,     CVE-2024-27044, CVE-2024-26848, CVE-2024-26955, CVE-2024-26899, CVE-2024-27077, CVE-2024-26897,     CVE-2024-26945, CVE-2024-26885, CVE-2024-27069, CVE-2024-27070, CVE-2024-27054, CVE-2024-35795,     CVE-2024-35817, CVE-2024-35827, CVE-2024-26656, CVE-2024-26860, CVE-2024-26942, CVE-2023-52659,     CVE-2024-26865, CVE-2024-26868, CVE-2024-26947, CVE-2024-35788, CVE-2024-26950, CVE-2024-27030,     CVE-2024-26949, CVE-2024-26900, CVE-2024-26971, CVE-2024-35805, CVE-2024-26977, CVE-2024-26944,     CVE-2024-27036, CVE-2024-26965, CVE-2024-26891, CVE-2024-27071, CVE-2024-27075, CVE-2024-27072,     CVE-2024-35830, CVE-2024-27052, CVE-2024-26970, CVE-2024-27031)

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

    Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition     during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could     possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    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)

    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)

    It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race     condition when stopping the device. A local attacker could possibly use this to cause a denial of service     (device unavailability). (CVE-2024-27432)

    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;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Cryptographic API;

    - DPLL subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - GPU drivers;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - MMC subsystem;

    - Network drivers;

    - NTB driver;

    - NVME drivers;

    - PCI subsystem;

    - Powercap sysfs driver;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Backlight driver;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - debug file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - Network file system client;

    - NILFS2 file system;

    - Overlay file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - Memory management;

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Packet sockets;

    - Network traffic control;

    - Sun RPC protocol;

    - ALSA SH drivers;

    - SOF drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-26859, CVE-2024-26944, CVE-2024-27049, CVE-2024-26868, CVE-2024-26932,     CVE-2024-35843, CVE-2024-35814, CVE-2024-26866, CVE-2024-26941, CVE-2024-27080, CVE-2024-26938,     CVE-2024-26889, CVE-2024-27075, CVE-2024-27077, CVE-2024-26864, CVE-2024-35787, CVE-2024-27071,     CVE-2024-26880, CVE-2024-26961, CVE-2024-26945, CVE-2024-26863, CVE-2024-35795, CVE-2024-27045,     CVE-2024-27066, CVE-2024-27046, CVE-2024-26816, CVE-2024-27069, CVE-2024-26861, CVE-2024-26968,     CVE-2024-26963, CVE-2024-26878, CVE-2024-27073, CVE-2024-35806, CVE-2024-26951, CVE-2024-26954,     CVE-2024-27026, CVE-2024-26956, CVE-2024-35811, CVE-2024-35803, CVE-2024-26964, CVE-2024-26848,     CVE-2024-27434, CVE-2024-35844, CVE-2024-26977, CVE-2024-27031, CVE-2024-35813, CVE-2024-26960,     CVE-2024-27067, CVE-2024-26937, CVE-2024-26884, CVE-2024-26656, CVE-2024-27068, CVE-2024-26871,     CVE-2023-52653, CVE-2024-26939, CVE-2024-26967, CVE-2024-26966, CVE-2024-27043, CVE-2024-26814,     CVE-2024-35829, CVE-2024-26973, CVE-2024-35810, CVE-2024-26877, CVE-2024-27392, CVE-2024-35805,     CVE-2024-26875, CVE-2024-26970, CVE-2024-26657, CVE-2024-26874, CVE-2024-26971, CVE-2024-26872,     CVE-2024-35798, CVE-2024-26931, CVE-2024-26948, CVE-2024-26883, CVE-2024-26955, CVE-2024-27039,     CVE-2024-27038, CVE-2024-27065, CVE-2024-26899, CVE-2024-27048, CVE-2024-35874, CVE-2024-35845,     CVE-2024-35799, CVE-2024-35827, CVE-2024-26935, CVE-2024-27079, CVE-2024-35821, CVE-2024-26950,     CVE-2024-26879, CVE-2024-26940, CVE-2024-35788, CVE-2024-26891, CVE-2024-27063, CVE-2024-27433,     CVE-2024-27036, CVE-2024-35819, CVE-2024-26969, CVE-2024-27044, CVE-2024-27028, CVE-2024-27070,     CVE-2023-52649, CVE-2024-27435, CVE-2024-35830, CVE-2024-26929, CVE-2024-26653, CVE-2024-26887,     CVE-2024-26869, CVE-2024-26942, CVE-2024-35822, CVE-2024-26979, CVE-2024-26881, CVE-2024-26655,     CVE-2024-26975, CVE-2023-52650, CVE-2024-26651, CVE-2024-35828, CVE-2024-26965, CVE-2024-27437,     CVE-2024-35794, CVE-2024-26962, CVE-2024-27058, CVE-2024-27076, CVE-2024-27035, CVE-2024-27074,     CVE-2024-27027, CVE-2024-26860, CVE-2024-27042, CVE-2024-27390, CVE-2024-26815, CVE-2023-52662,     CVE-2024-27051, CVE-2024-35796, CVE-2024-27047, CVE-2024-26930, CVE-2024-26865, CVE-2024-27064,     CVE-2024-35826, CVE-2024-26885, CVE-2024-26873, CVE-2024-26943, CVE-2024-26893, CVE-2024-27030,     CVE-2024-26976, CVE-2024-35793, CVE-2024-26952, CVE-2023-52644, CVE-2024-35797, CVE-2024-27029,     CVE-2024-26927, CVE-2024-26812, CVE-2024-27432, CVE-2024-26897, CVE-2024-26890, CVE-2024-26972,     CVE-2024-35800, CVE-2024-27032, CVE-2024-27052, CVE-2023-52647, CVE-2024-26898, CVE-2023-52652,     CVE-2024-35808, CVE-2024-26876, CVE-2024-26933, CVE-2024-26862, CVE-2024-27033, CVE-2023-52663,     CVE-2024-27041, CVE-2023-52648, CVE-2024-26888, CVE-2024-26957, CVE-2024-26953, CVE-2023-52659,     CVE-2024-27436, CVE-2024-27040, CVE-2024-27054, CVE-2024-27050, CVE-2024-26886, CVE-2023-52661,     CVE-2024-35831, CVE-2024-26946, CVE-2024-26949, CVE-2024-26809, CVE-2024-26892, CVE-2024-26654,     CVE-2024-26901, CVE-2024-27053, CVE-2024-26882, CVE-2024-35809, CVE-2024-26978, CVE-2024-27037,     CVE-2024-27391, CVE-2024-27034, CVE-2024-26895, CVE-2024-35817, CVE-2024-26900, CVE-2024-26896,     CVE-2024-26958, CVE-2024-35801, CVE-2024-27388, CVE-2024-26934, CVE-2024-27078, CVE-2024-35789,     CVE-2024-26894, CVE-2024-27389, CVE-2024-35807, CVE-2024-27072, CVE-2024-26947, CVE-2024-26870,     CVE-2024-26813, CVE-2022-48669, CVE-2024-26959, CVE-2024-26810)

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.

ID	Name	Product	Family	Type	Severity
359694	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Rocky Linux Local Security Checks	Local	high
359640	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Alma Linux Local Security Checks	Local	high
332184	Photon OS 5.0: Linux PHSA-2024-5.0-91-0274	Nessus	PhotonOS Local Security Checks	Local	high
239342	TencentOS Server 4: kernel (TSSA-2024:0981)	Nessus	Tencent Local Security Checks	Local	high
228589	Linux Distros Unpatched Vulnerability : CVE-2024-35803	Nessus	Misc.	Local	high
206008	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:2973-1)	Nessus	SuSE Local Security Checks	Local	high
204159	Photon OS 5.0: Linux PHSA-2024-5.0-0274	Nessus	PhotonOS Local Security Checks	Local	high
201889	Ubuntu 24.04 LTS : Linux kernel (Oracle) vulnerabilities (USN-6878-1)	Nessus	Ubuntu Local Security Checks	Local	high
200853	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:2135-1)	Nessus	SuSE Local Security Checks	Local	high
200633	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6817-3)	Nessus	Ubuntu Local Security Checks	Local	high
200275	Ubuntu 24.04 LTS : Linux kernel (OEM) vulnerabilities (USN-6817-2)	Nessus	Ubuntu Local Security Checks	Local	high
200227	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6816-1)	Nessus	Ubuntu Local Security Checks	Local	high
200226	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6817-1)	Nessus	Ubuntu Local Security Checks	Local	high

Detections

Analytics

CVE-2024-35803

medium

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high