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

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

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

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

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

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

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

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Android drivers;

    - Serial ATA and Parallel ATA drivers;

    - ATM drivers;

    - Drivers core;

    - ATA over ethernet (AOE) driver;

    - Null block device driver;

    - TPM device driver;

    - Character device driver;

    - Clock framework and drivers;

    - Buffer Sharing and Synchronization framework;

    - ARM SCMI message protocol;

    - EFI core;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - ISDN/mISDN subsystem;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - STMicroelectronics network drivers;

    - Near Field Communication (NFC) drivers;

    - NTB driver;

    - Virtio pmem driver;

    - NVME drivers;

    - Device tree and open firmware driver;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Thermal drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - Userspace I/O drivers;

    - USB Device Class drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Type-C Port Controller Manager driver;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - 9P distributed file system;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - SMB network file system;

    - Bitmap API;

    - Network file system (NFS) superblock;

    - Objagg library;

    - Perf events;

    - Virtio network driver;

    - Bluetooth subsystem;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - Network traffic control;

    - Network sockets;

    - TCP network protocol;

    - BPF subsystem;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Kernel thread helper (kthread);

    - Locking primitives;

    - Padata parallel execution mechanism;

    - RCU subsystem;

    - Arbitrary resource management;

    - Scheduler infrastructure;

    - Static call mechanism;

    - Tracing infrastructure;

    - Radix Tree data structure library;

    - Kernel userspace event delivery library;

    - Memory management;

    - Amateur Radio drivers;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - Ethtool driver;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - Netlink;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - Wireless networking;

    - AppArmor security module;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - AudioScience HPI driver;

    - Amlogic Meson SoC drivers;

    - SoC audio core drivers;

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

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

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

The 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: firmware: arm_scmi: Fix double free in     SMC transport cleanup path When the generic SCMI code tears down a channel, it calls the chan_free     callback function, defined by each transport. Since multiple protocols might share the same transport_info     member, chan_free() might want to clean up the same member multiple times within the given SCMI transport     implementation. In this case, it is SMC transport. This will lead to a NULL pointer dereference at the     second time: | scmi_protocol scmi_dev.1: Enabled polling mode TX channel - prot_id:16 | arm-scmi     firmware:scmi: SCMI Notifications - Core Enabled. | arm-scmi firmware:scmi: unable to communicate with     SCMI | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort     info: | ESR = 0x0000000096000004 | EC = 0x25: DABT (current EL), IL = 32 bits | SET = 0, FnV = 0 | EA = 0,     S1PTW = 0 | FSC = 0x04: level 0 translation fault | Data abort info: | ISV = 0, ISS = 0x00000004, ISS2 =     0x00000000 | CM = 0, WnR = 0, TnD = 0, TagAccess = 0 | GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 | user     pgtable: 4k pages, 48-bit VAs, pgdp=0000000881ef8000 | [0000000000000000] pgd=0000000000000000,     p4d=0000000000000000 | Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP | Modules linked in: | CPU:
    4 PID: 1 Comm: swapper/0 Not tainted 6.7.0-rc2-00124-g455ef3d016c9-dirty #793 | Hardware name: FVP Base     RevC (DT) | pstate: 61400009 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) | pc : smc_chan_free+0x3c/0x6c     | lr : smc_chan_free+0x3c/0x6c | Call trace: | smc_chan_free+0x3c/0x6c | idr_for_each+0x68/0xf8 |     scmi_cleanup_channels.isra.0+0x2c/0x58 | scmi_probe+0x434/0x734 | platform_probe+0x68/0xd8 |     really_probe+0x110/0x27c | __driver_probe_device+0x78/0x12c | driver_probe_device+0x3c/0x118 |
    __driver_attach+0x74/0x128 | bus_for_each_dev+0x78/0xe0 | driver_attach+0x24/0x30 |     bus_add_driver+0xe4/0x1e8 | driver_register+0x60/0x128 | __platform_driver_register+0x28/0x34 |     scmi_driver_init+0x84/0xc0 | do_one_initcall+0x78/0x33c | kernel_init_freeable+0x2b8/0x51c |     kernel_init+0x24/0x130 | ret_from_fork+0x10/0x20 | Code: f0004701 910a0021 aa1403e5 97b91c70 (b9400280) |
    ---[ end trace 0000000000000000 ]--- Simply check for the struct pointer being NULL before trying to     access its members, to avoid this situation. This was found when a transport doesn't really work (for     instance no SMC service), the probe routines then tries to clean up, and triggers a crash.
    (CVE-2024-26893)

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 AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1779434490 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in     configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem()     is executing link_group() or unlink_group(), it is possible that two processes add or delete list     concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --> B -->     C --> D A <-- B <-- C <-- D delete list_head *B | delete list_head *C
    --------------------------------|----------------------------------- configfs_unregister_subsystem |     configfs_unregister_subsystem unlink_group | unlink_group unlink_obj | unlink_obj list_del_init |     list_del_init __list_del_entry | __list_del_entry __list_del | __list_del // next == C | next->prev = prev     | | next->prev = prev prev->next = next | | // prev == B | prev->next = next Fix this by adding mutex when     calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So     I create a mutex configfs_subsystem_mutex. (CVE-2022-48931)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

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

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

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in     configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem()     is executing link_group() or unlink_group(), it is possible that two processes add or delete list     concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --> B -->     C --> D A <-- B <-- C <-- D delete list_head *B | delete list_head *C
    --------------------------------|----------------------------------- configfs_unregister_subsystem |     configfs_unregister_subsystem unlink_group | unlink_group unlink_obj | unlink_obj list_del_init |     list_del_init __list_del_entry | __list_del_entry __list_del | __list_del // next == C | next->prev = prev     | | next->prev = prev prev->next = next | | // prev == B | prev->next = next Fix this by adding mutex when     calling link_group() or unlink_group(), but parent configfs_subsystem is NULL when config_item is root. So     I create a mutex configfs_subsystem_mutex. (CVE-2022-48931)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

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

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

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

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
213658	Ubuntu 20.04 LTS : Linux kernel (Azure) vulnerabilities (USN-7194-1)	Nessus	Ubuntu Local Security Checks	2025/1/9	2026/1/6	critical
227755	Linux Distros Unpatched Vulnerability : CVE-2024-26893	Nessus	Misc.	2025/3/5	2026/11/12	medium
201889	Ubuntu 24.04 LTS : Linux kernel (Oracle) vulnerabilities (USN-6878-1)	Nessus	Ubuntu Local Security Checks	2024/7/4	2026/3/24	high
360724	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1779434490)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/2	high
360889	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1779434490)	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/2	high

偵測

搜尋 Plugin

critical

medium

high

high

high