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

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

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

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

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

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

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

    Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the     device to be enabled before writing. A local attacker could possibly use this to cause a denial of     service. (CVE-2024-25741)

    Benedict Schlter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde discovered that an untrusted     hypervisor could inject malicious #VC interrupts and compromise the security guarantees of AMD SEV-SNP.
    This flaw is known as WeSee. A local attacker in control of the hypervisor could use this to expose     sensitive information or possibly execute arbitrary code in the trusted execution environment.
    (CVE-2024-25742)

    It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing     xattr debug information. A local attacker could use this to cause a denial of service (system crash).
    (CVE-2024-40902)

    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;

    - M68K architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - SuperH RISC architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Accessibility subsystem;

    - ACPI drivers;

    - Android drivers;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Character device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - FireWire subsystem;

    - FPGA Framework;

    - GPIO subsystem;

    - GPU drivers;

    - Greybus drivers;

    - HID subsystem;

    - HW tracing;

    - I2C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device (Mouse) drivers;

    - IRQ chip drivers;

    - Macintosh device drivers;

    - Multiple devices driver;

    - Media drivers;

    - EEPROM drivers;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Near Field Communication (NFC) drivers;

    - NVME drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - Pin controllers subsystem;

    - PTP clock framework;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SoundWire subsystem;

    - Greybus lights staging drivers;

    - Media staging drivers;

    - Trusted Execution Environment drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Framebuffer layer;

    - ACRN Hypervisor Service Module driver;

    - Xen hypervisor drivers;

    - 9P distributed file system;

    - File systems infrastructure;

    - BTRFS file system;

    - eCrypt file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - GFS2 file system;

    - JFFS2 file system;

    - JFS file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - NTFS3 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - IOMMU subsystem;

    - Memory management;

    - Socket messages infrastructure;

    - Netfilter;

    - BPF subsystem;

    - Kernel debugger infrastructure;

    - DMA mapping infrastructure;

    - IRQ subsystem;

    - Core kernel;

    - Tracing infrastructure;

    - Dynamic debug library;

    - PCI iomap interfaces;

    - 9P file system network protocol;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - Distributed Switch Architecture;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - NET/ROM layer;

    - NFC subsystem;

    - NSH protocol;

    - Open vSwitch;

    - Phonet protocol;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - XFRM subsystem;

    - Key management;

    - ALSA framework;

    - HD-audio driver;

    - ALSA SH drivers;

    - SoC Audio for Freescale CPUs drivers;

    - Kirkwood ASoC drivers;

    - KVM core; (CVE-2024-42085, CVE-2024-42154, CVE-2024-42229, CVE-2024-38548, CVE-2024-42120,     CVE-2024-38555, CVE-2024-38598, CVE-2024-40954, CVE-2024-38571, CVE-2024-36020, CVE-2024-36270,     CVE-2024-39482, CVE-2024-39468, CVE-2024-38607, CVE-2024-26923, CVE-2024-42145, CVE-2024-41040,     CVE-2024-35852, CVE-2024-35805, CVE-2024-35890, CVE-2024-36965, CVE-2024-42077, CVE-2024-26958,     CVE-2024-35823, CVE-2024-42124, CVE-2024-26680, CVE-2024-38549, CVE-2024-36286, CVE-2024-27398,     CVE-2024-35990, CVE-2024-36975, CVE-2024-27437, CVE-2024-35848, CVE-2024-26900, CVE-2024-26654,     CVE-2024-40971, CVE-2024-35847, CVE-2024-35982, CVE-2024-42232, CVE-2022-48808, CVE-2024-35822,     CVE-2024-36950, CVE-2024-33621, CVE-2024-39276, CVE-2024-40968, CVE-2024-35857, CVE-2024-40905,     CVE-2023-52880, CVE-2024-35819, CVE-2024-35791, CVE-2024-42076, CVE-2024-40904, CVE-2024-35976,     CVE-2024-35854, CVE-2024-26642, CVE-2024-27393, CVE-2024-26934, CVE-2024-26960, CVE-2024-42137,     CVE-2024-38588, CVE-2024-40970, CVE-2024-36972, CVE-2024-26977, CVE-2024-38546, CVE-2024-41095,     CVE-2024-39292, CVE-2024-41087, CVE-2024-33847, CVE-2024-40978, CVE-2024-41049, CVE-2024-35895,     CVE-2024-35804, CVE-2024-42093, CVE-2024-36017, CVE-2024-38591, CVE-2024-42080, CVE-2024-41089,     CVE-2024-38613, CVE-2024-39466, CVE-2024-40931, CVE-2024-35907, CVE-2024-36919, CVE-2024-36934,     CVE-2024-42240, CVE-2024-35940, CVE-2024-36938, CVE-2024-42121, CVE-2024-39490, CVE-2024-40961,     CVE-2024-42223, CVE-2024-41041, CVE-2024-41093, CVE-2024-42068, CVE-2024-41044, CVE-2024-42086,     CVE-2024-42105, CVE-2024-36954, CVE-2024-35796, CVE-2024-38610, CVE-2024-36929, CVE-2024-35893,     CVE-2024-38601, CVE-2024-40981, CVE-2024-36889, CVE-2024-27015, CVE-2024-35897, CVE-2024-39469,     CVE-2024-35825, CVE-2024-26922, CVE-2024-38573, CVE-2024-42130, CVE-2024-38580, CVE-2024-26814,     CVE-2024-36955, CVE-2024-26813, CVE-2024-27396, CVE-2024-36937, CVE-2024-36928, CVE-2024-42224,     CVE-2024-27004, CVE-2024-42104, CVE-2024-42225, CVE-2024-38659, CVE-2024-35955, CVE-2024-42106,     CVE-2024-39489, CVE-2024-31076, CVE-2024-26817, CVE-2024-35884, CVE-2024-42095, CVE-2024-42131,     CVE-2024-40956, CVE-2024-40941, CVE-2024-36007, CVE-2024-27009, CVE-2024-40959, CVE-2024-42089,     CVE-2024-37078, CVE-2024-35960, CVE-2024-41002, CVE-2024-39301, CVE-2024-35988, CVE-2023-52887,     CVE-2024-35885, CVE-2024-39484, CVE-2024-35872, CVE-2024-40974, CVE-2024-35851, CVE-2024-26957,     CVE-2024-38623, CVE-2024-35944, CVE-2024-41005, CVE-2024-42152, CVE-2024-35888, CVE-2024-38621,     CVE-2024-26989, CVE-2024-42148, CVE-2024-27401, CVE-2024-36883, CVE-2024-35855, CVE-2024-26936,     CVE-2024-26935, CVE-2022-48772, CVE-2024-35853, CVE-2024-35997, CVE-2024-27059, CVE-2024-36953,     CVE-2024-35969, CVE-2024-42094, CVE-2024-38661, CVE-2024-35925, CVE-2024-40914, CVE-2024-36940,     CVE-2024-27016, CVE-2024-26828, CVE-2024-40911, CVE-2024-38634, CVE-2024-38558, CVE-2024-38582,     CVE-2023-52629, CVE-2024-27020, CVE-2024-35247, CVE-2024-26999, CVE-2024-26687, CVE-2024-38565,     CVE-2024-38612, CVE-2024-39495, CVE-2024-26974, CVE-2024-42101, CVE-2024-38597, CVE-2024-26929,     CVE-2024-40927, CVE-2024-26830, CVE-2024-26973, CVE-2024-40980, CVE-2024-38560, CVE-2024-41047,     CVE-2024-42098, CVE-2024-39507, CVE-2024-38599, CVE-2024-35789, CVE-2024-27395, CVE-2024-41092,     CVE-2024-42161, CVE-2024-41006, CVE-2024-36931, CVE-2024-38619, CVE-2024-35813, CVE-2024-35898,     CVE-2024-41027, CVE-2024-40932, CVE-2024-40960, CVE-2024-26925, CVE-2024-41048, CVE-2024-36886,     CVE-2024-35877, CVE-2024-40963, CVE-2024-36960, CVE-2024-38590, CVE-2024-40902, CVE-2024-35871,     CVE-2024-38579, CVE-2024-40987, CVE-2024-36025, CVE-2024-35806, CVE-2024-35899, CVE-2024-26993,     CVE-2024-41097, CVE-2024-39488, CVE-2024-42115, CVE-2024-42127, CVE-2024-37356, CVE-2024-26812,     CVE-2024-36939, CVE-2024-35807, CVE-2024-26886, CVE-2024-35809, CVE-2024-40937, CVE-2024-35970,     CVE-2024-35817, CVE-2024-35973, CVE-2024-40945, CVE-2024-42153, CVE-2024-36964, CVE-2024-42090,     CVE-2024-38552, CVE-2024-39467, CVE-2024-26961, CVE-2024-38615, CVE-2024-38618, CVE-2024-40988,     CVE-2024-38605, CVE-2024-41004, CVE-2024-26966, CVE-2024-42096, CVE-2024-26996, CVE-2024-36969,     CVE-2024-36489, CVE-2024-40957, CVE-2024-36974, CVE-2024-39502, CVE-2024-26976, CVE-2024-27399,     CVE-2024-36905, CVE-2024-35958, CVE-2024-35927, CVE-2024-27001, CVE-2024-39487, CVE-2024-41034,     CVE-2024-36904, CVE-2024-41055, CVE-2024-38550, CVE-2024-38567, CVE-2024-38586, CVE-2024-40916,     CVE-2024-38589, CVE-2023-52884, CVE-2024-26810, CVE-2024-35989, CVE-2024-36894, CVE-2024-39471,     CVE-2024-35900, CVE-2024-42097, CVE-2024-36959, CVE-2024-26931, CVE-2024-40934, CVE-2024-36947,     CVE-2024-34777, CVE-2024-27018, CVE-2024-39499, CVE-2024-36906, CVE-2024-35984, CVE-2024-39500,     CVE-2024-26965, CVE-2024-26921, CVE-2024-27013, CVE-2024-39509, CVE-2024-27008, CVE-2024-36916,     CVE-2024-40942, CVE-2024-35978, CVE-2024-26969, CVE-2024-26964, CVE-2024-35879, CVE-2024-36016,     CVE-2024-26629, CVE-2024-42236, CVE-2024-40943, CVE-2024-36902, CVE-2024-42247, CVE-2024-36006,     CVE-2024-36014, CVE-2024-26955, CVE-2024-39277, CVE-2024-39506, CVE-2024-35936, CVE-2024-26950,     CVE-2024-35938, CVE-2024-41035, CVE-2024-42140, CVE-2024-36971, CVE-2024-35910, CVE-2024-34027,     CVE-2024-35933, CVE-2024-35886, CVE-2024-39501, CVE-2024-42109, CVE-2024-42157, CVE-2024-35905,     CVE-2024-41007, CVE-2024-40912, CVE-2024-26984, CVE-2024-35915, CVE-2024-35934, CVE-2024-38633,     CVE-2024-26952, CVE-2024-27017, CVE-2024-38627, CVE-2024-42070, CVE-2024-41046, CVE-2024-35821,     CVE-2024-35815, CVE-2024-36978, CVE-2024-36967, CVE-2023-52752, CVE-2024-38583, CVE-2024-38578,     CVE-2024-26926, CVE-2023-52699, CVE-2024-36952, CVE-2024-38600, CVE-2024-42102, CVE-2024-38559,     CVE-2024-38637, CVE-2024-42082, CVE-2023-52488, CVE-2024-36032, CVE-2024-35950, CVE-2024-35930,     CVE-2024-38780, CVE-2024-40995, CVE-2024-36004, CVE-2024-26956, CVE-2024-35896, CVE-2024-26994,     CVE-2024-38624, CVE-2024-39480, CVE-2023-52882, CVE-2024-35912, CVE-2024-36015, CVE-2024-27019,     CVE-2024-40983, CVE-2023-52760, CVE-2024-39503, CVE-2024-36957, CVE-2024-26980, CVE-2024-40908,     CVE-2024-40958, CVE-2024-35902, CVE-2024-42087, CVE-2024-36933, CVE-2024-38635, CVE-2024-26988,     CVE-2024-36941, CVE-2024-26970, CVE-2024-36005, CVE-2024-36029, CVE-2024-36008, CVE-2024-42244,     CVE-2024-40967, CVE-2023-52585, CVE-2024-26951, CVE-2024-39475, CVE-2024-35922, CVE-2024-36901,     CVE-2024-40901, CVE-2024-36031, CVE-2024-41000, CVE-2024-40929, CVE-2024-40994, CVE-2024-42084,     CVE-2024-38547, CVE-2024-26937, CVE-2024-40984, CVE-2024-27000, CVE-2024-35785, CVE-2024-35849,     CVE-2024-42119, CVE-2024-35947, CVE-2024-39505, CVE-2024-42092, CVE-2024-26811, CVE-2024-35935,     CVE-2024-36946, CVE-2024-40990, CVE-2024-26981, CVE-2024-38596, CVE-2024-40976, CVE-2024-36880)

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-6893-1 advisory.

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

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

    - ARM64 architecture;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Compute Acceleration Framework;

    - Accessibility subsystem;

    - Android drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - Buffer Sharing and Synchronization framework;

    - GPU drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - Chrome hardware platform drivers;

    - i.MX PM domains;

    - TI SCI PM domains driver;

    - S/390 drivers;

    - SCSI drivers;

    - SPI subsystem;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - Framebuffer layer;

    - BTRFS file system;

    - Network file system server daemon;

    - NILFS2 file system;

    - File systems infrastructure;

    - Pstore file system;

    - SMB network file system;

    - BPF subsystem;

    - Bluetooth subsystem;

    - Netfilter;

    - io_uring subsystem;

    - Core kernel;

    - Extra boot config (XBC);

    - Memory management;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - NFC subsystem;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Sun RPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - SELinux security module; (CVE-2024-35967, CVE-2024-35886, CVE-2024-26999, CVE-2024-27008,     CVE-2024-26988, CVE-2024-35980, CVE-2024-26982, CVE-2024-35946, CVE-2024-35918, CVE-2024-27015,     CVE-2024-35900, CVE-2024-35942, CVE-2024-35879, CVE-2024-35961, CVE-2024-35944, CVE-2024-35934,     CVE-2024-35978, CVE-2024-35938, CVE-2024-27003, CVE-2024-35976, CVE-2024-36019, CVE-2024-35880,     CVE-2024-35866, CVE-2024-35929, CVE-2024-35917, CVE-2024-35912, CVE-2024-35896, CVE-2024-26986,     CVE-2024-35951, CVE-2024-35958, CVE-2024-26997, CVE-2024-35965, CVE-2024-35953, CVE-2024-26993,     CVE-2024-26991, CVE-2024-35892, CVE-2024-36026, CVE-2024-35882, CVE-2024-35964, CVE-2024-35865,     CVE-2024-35897, CVE-2024-26981, CVE-2024-35872, CVE-2024-36027, CVE-2024-26983, CVE-2024-35909,     CVE-2024-35985, CVE-2024-35875, CVE-2024-35890, CVE-2024-26922, CVE-2024-26994, CVE-2024-35903,     CVE-2024-35936, CVE-2024-35904, CVE-2024-27013, CVE-2024-36025, CVE-2024-26980, CVE-2024-27006,     CVE-2024-35861, CVE-2024-35864, CVE-2024-27018, CVE-2024-36022, CVE-2024-26990, CVE-2024-35968,     CVE-2024-35860, CVE-2024-36024, CVE-2024-35933, CVE-2024-27019, CVE-2024-35925, CVE-2024-35950,     CVE-2024-35915, CVE-2024-35916, CVE-2024-35956, CVE-2024-36020, CVE-2024-35873, CVE-2024-27002,     CVE-2024-35963, CVE-2024-35959, CVE-2024-35937, CVE-2024-27011, CVE-2024-27020, CVE-2024-35883,     CVE-2024-35913, CVE-2024-35910, CVE-2024-27021, CVE-2024-35921, CVE-2024-35905, CVE-2024-27010,     CVE-2024-35981, CVE-2024-35885, CVE-2024-35955, CVE-2024-35894, CVE-2024-35969, CVE-2024-36018,     CVE-2024-35867, CVE-2024-27007, CVE-2024-35908, CVE-2024-26985, CVE-2024-27016, CVE-2024-35960,     CVE-2024-35935, CVE-2024-35932, CVE-2024-35957, CVE-2024-27001, CVE-2024-35871, CVE-2024-35907,     CVE-2024-35878, CVE-2024-35979, CVE-2024-35972, CVE-2024-35975, CVE-2024-35877, CVE-2024-35926,     CVE-2024-26817, CVE-2024-35899, CVE-2024-27004, CVE-2024-35920, CVE-2024-35924, CVE-2024-35977,     CVE-2024-35930, CVE-2024-35911, CVE-2024-26996, CVE-2024-27005, CVE-2024-35870, CVE-2024-35982,     CVE-2024-35895, CVE-2024-35943, CVE-2024-35902, CVE-2024-35919, CVE-2024-35973, CVE-2024-35931,     CVE-2024-35888, CVE-2024-35914, CVE-2024-35970, CVE-2024-36023, CVE-2024-27012, CVE-2024-35939,     CVE-2024-26984, CVE-2024-35884, CVE-2024-35901, CVE-2024-26811, CVE-2024-35966, CVE-2024-35891,     CVE-2024-35887, CVE-2024-35945, CVE-2024-35971, CVE-2024-35862, CVE-2024-26987, CVE-2024-26921,     CVE-2024-26989, CVE-2024-35952, CVE-2024-27009, CVE-2024-35893, CVE-2024-26995, CVE-2024-26925,     CVE-2024-35868, CVE-2024-35954, CVE-2024-35922, CVE-2024-27000, CVE-2024-36021, CVE-2024-27014,     CVE-2024-35940, CVE-2024-26992, CVE-2024-26926, CVE-2024-35927, CVE-2024-35863, CVE-2024-27022,     CVE-2024-26998, CVE-2024-27017, CVE-2024-26928, CVE-2024-35889, CVE-2024-35898, CVE-2024-35869,     CVE-2024-26936, CVE-2024-26923, CVE-2023-52699, CVE-2024-35974)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    - ARM64 architecture;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Accessibility subsystem;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - Netfilter;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - NFC subsystem;

    - Open vSwitch;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Unix domain sockets;

    - eXpress Data Path;

    - ALSA SH drivers;

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

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

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

An update of the linux package has been released.

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

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

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

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

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

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

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

    - ARM64 architecture;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Accessibility subsystem;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - Netfilter;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - NFC subsystem;

    - Open vSwitch;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Unix domain sockets;

    - eXpress Data Path;

    - ALSA SH drivers;

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

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

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

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

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

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

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

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

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

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

    - ARM64 architecture;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Accessibility subsystem;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - Netfilter;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - Networking core;

    - Distributed Switch Architecture;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - NFC subsystem;

    - Open vSwitch;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Unix domain sockets;

    - eXpress Data Path;

    - Key management;

    - ALSA SH drivers;

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

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix racy issue from session     lookup and expire Increment the session reference count within the lock for lookup to avoid racy issue     with session expire. (CVE-2024-58087)

  - In the Linux kernel, the following vulnerability has been resolved: nouveau: fix instmem race condition     around ptr stores Running a lot of VK CTS in parallel against nouveau, once every few hours you might see     something like this crash. BUG: kernel NULL pointer dereference, address: 0000000000000008 PGD     8000000114e6e067 P4D 8000000114e6e067 PUD 109046067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 7 PID:
    53891 Comm: deqp-vk Not tainted 6.8.0-rc6+ #27 Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS     PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F8 11/05/2021 RIP: 0010:gp100_vmm_pgt_mem+0xe3/0x180 [nouveau]     Code: c7 48 01 c8 49 89 45 58 85 d2 0f 84 95 00 00 00 41 0f b7 46 12 49 8b 7e 08 89 da 42 8d 2c f8 48 8b     47 08 41 83 c7 01 48 89 ee <48> 8b 40 08 ff d0 0f 1f 00 49 8b 7e 08 48 89 d9 48 8d 75 04 48 c1 RSP:
    0000:ffffac20c5857838 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 00000000004d8001 RCX: 0000000000000001     RDX: 00000000004d8001 RSI: 00000000000006d8 RDI: ffffa07afe332180 RBP: 00000000000006d8 R08:
    ffffac20c5857ad0 R09: 0000000000ffff10 R10: 0000000000000001 R11: ffffa07af27e2de0 R12: 000000000000001c     R13: ffffac20c5857ad0 R14: ffffa07a96fe9040 R15: 000000000000001c FS: 00007fe395eed7c0(0000)     GS:ffffa07e2c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    0000000000000008 CR3: 000000011febe001 CR4: 00000000003706f0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ... ?     gp100_vmm_pgt_mem+0xe3/0x180 [nouveau] ? gp100_vmm_pgt_mem+0x37/0x180 [nouveau] nvkm_vmm_iter+0x351/0xa20     [nouveau] ? __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ?
    __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ? __lock_acquire+0x3ed/0x2170 ?
    __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] nvkm_vmm_ptes_get_map+0xc2/0x100 [nouveau] ?
    __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau]     nvkm_vmm_map_locked+0x224/0x3a0 [nouveau] Adding any sort of useful debug usually makes it go away, so I     hand wrote the function in a line, and debugged the asm. Every so often pt->memory->ptrs is NULL. This     ptrs ptr is set in the nv50_instobj_acquire called from nvkm_kmap. If Thread A and Thread B both get to     nv50_instobj_acquire around the same time, and Thread A hits the refcount_set line, and in lockstep thread     B succeeds at refcount_inc_not_zero, there is a chance the ptrs value won't have been stored since     refcount_set is unordered. Force a memory barrier here, I picked smp_mb, since we want it on all CPUs and     it's write followed by a read. v2: use paired smp_rmb/smp_wmb. (CVE-2024-26984)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free bugs     caused by sco_sock_timeout When the sco connection is established and then, the sco socket is releasing,     timeout_work will be scheduled to judge whether the sco disconnection is timeout. The sock will be     deallocated later, but it is dereferenced again in sco_sock_timeout. As a result, the use-after-free bugs     will happen. The root cause is shown below: Cleanup Thread | Worker Thread sco_sock_release |     sco_sock_close | __sco_sock_close | sco_sock_set_timer | schedule_delayed_work | sco_sock_kill | (wait a     time) sock_put(sk) //FREE | sco_sock_timeout | sock_hold(sk) //USE The KASAN report triggered by POC is     shown below: [ 95.890016] ================================================================== [ 95.890496]     BUG: KASAN: slab-use-after-free in sco_sock_timeout+0x5e/0x1c0 [ 95.890755] Write of size 4 at addr     ffff88800c388080 by task kworker/0:0/7 ... [ 95.890755] Workqueue: events sco_sock_timeout [ 95.890755]     Call Trace: [ 95.890755] <TASK> [ 95.890755] dump_stack_lvl+0x45/0x110 [ 95.890755]     print_address_description+0x78/0x390 [ 95.890755] print_report+0x11b/0x250 [ 95.890755] ?
    __virt_addr_valid+0xbe/0xf0 [ 95.890755] ? sco_sock_timeout+0x5e/0x1c0 [ 95.890755]     kasan_report+0x139/0x170 [ 95.890755] ? update_load_avg+0xe5/0x9f0 [ 95.890755] ?     sco_sock_timeout+0x5e/0x1c0 [ 95.890755] kasan_check_range+0x2c3/0x2e0 [ 95.890755]     sco_sock_timeout+0x5e/0x1c0 [ 95.890755] process_one_work+0x561/0xc50 [ 95.890755]     worker_thread+0xab2/0x13c0 [ 95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] kthread+0x279/0x300 [     95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755]     ret_from_fork+0x34/0x60 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755] ret_from_fork_asm+0x11/0x20 [     95.890755] </TASK> [ 95.890755] [ 95.890755] Allocated by task 506: [ 95.890755]     kasan_save_track+0x3f/0x70 [ 95.890755] __kasan_kmalloc+0x86/0x90 [ 95.890755] __kmalloc+0x17f/0x360 [     95.890755] sk_prot_alloc+0xe1/0x1a0 [ 95.890755] sk_alloc+0x31/0x4e0 [ 95.890755] bt_sock_alloc+0x2b/0x2a0     [ 95.890755] sco_sock_create+0xad/0x320 [ 95.890755] bt_sock_create+0x145/0x320 [ 95.890755]
    __sock_create+0x2e1/0x650 [ 95.890755] __sys_socket+0xd0/0x280 [ 95.890755] __x64_sys_socket+0x75/0x80 [     95.890755] do_syscall_64+0xc4/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [     95.890755] Freed by task 506: [ 95.890755] kasan_save_track+0x3f/0x70 [ 95.890755]     kasan_save_free_info+0x40/0x50 [ 95.890755] poison_slab_object+0x118/0x180 [ 95.890755]
    __kasan_slab_free+0x12/0x30 [ 95.890755] kfree+0xb2/0x240 [ 95.890755] __sk_destruct+0x317/0x410 [     95.890755] sco_sock_release+0x232/0x280 [ 95.890755] sock_close+0xb2/0x210 [ 95.890755] __fput+0x37f/0x770     [ 95.890755] task_work_run+0x1ae/0x210 [ 95.890755] get_signal+0xe17/0xf70 [ 95.890755]     arch_do_signal_or_restart+0x3f/0x520 [ 95.890755] syscall_exit_to_user_mode+0x55/0x120 [ 95.890755]     do_syscall_64+0xd1/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [ 95.890755]     The buggy address belongs to the object at ffff88800c388000 [ 95.890755] which belongs to the cache     kmalloc-1k of size 1024 [ 95.890755] The buggy address is located 128 bytes inside of [ 95.890755] freed     1024-byte region [ffff88800c388000, ffff88800c388400) [ 95.890755] [ 95.890755] The buggy address belongs     to the physical page: [ 95.890755] page: refcount:1 mapcount:0 mapping:0000000000000000     index:0xffff88800c38a800 pfn:0xc388 [ 95.890755] head: order:3 entire_mapcount:0 nr_pages_mapped:0     pincount:0 [ 95.890755] ano ---truncated--- (CVE-2024-27398)

  - In the Linux kernel, the following vulnerability has been resolved: firewire: nosy: ensure user_length is     taken into account when fetching packet contents Ensure that packet_buffer_get respects the user_length     provided. If the length of the head packet exceeds the user_length, packet_buffer_get will now return 0 to     signify to the user that no data were read and a larger buffer size is required. Helps prevent user space     overflows. (CVE-2024-27401)

  - In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage     childregs represents the registers which are active for the new thread in user context. For a kernel     thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode     helper, the gp value can be observed in user space after execve or possibly by other means. [From the     email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for     user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern     is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they     exec. childregs is the *user* context during syscall execution and it is observable from userspace in at     least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register     state for PID 1 and other user processes started by the kernel has sp = user stack, gp = kernel
    __global_pointer$, all other integer registers zeroed by the memset in the patch comment. This is a bug in     its own right, but I'm unwilling to bet that it is the only way to exploit the issue addressed by this     patch. 2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread before it execs,     but ptrace requires SIGSTOP to be delivered which can only happen at user/kernel boundaries. 3.
    /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for user_mode_helpers before the exec     completes, but gp is not one of the registers it returns. 4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally     prevents access to kernel addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses are     also exposed via PERF_SAMPLE_REGS_USER which is permitted under LOCKDOWN_PERF. I have not attempted to     write exploit code. 5. Much of the tracing infrastructure allows access to user registers. I have not     attempted to determine which forms of tracing allow access to user registers without already allowing     access to kernel registers. (CVE-2024-35871)

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-6918-1 advisory.

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service.

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

    - ARM64 architecture;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Compute Acceleration Framework;

    - Accessibility subsystem;

    - Android drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - Buffer Sharing and Synchronization framework;

    - GPU drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - Chrome hardware platform drivers;

    - i.MX PM domains;

    - TI SCI PM domains driver;

    - S/390 drivers;

    - SCSI drivers;

    - SPI subsystem;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - Framebuffer layer;

    - BTRFS file system;

    - Network file system server daemon;

    - NILFS2 file system;

    - File systems infrastructure;

    - Pstore file system;

    - SMB network file system;

    - BPF subsystem;

    - Bluetooth subsystem;

    - Netfilter;

    - io_uring subsystem;

    - Core kernel;

    - Extra boot config (XBC);

    - Memory management;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - NFC subsystem;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Sun RPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - SELinux security module; (CVE-2024-26988, CVE-2024-36023, CVE-2024-35869, CVE-2024-35938,     CVE-2024-27000, CVE-2024-35880, CVE-2024-35915, CVE-2024-35959, CVE-2024-35883, CVE-2024-35886,     CVE-2024-35976, CVE-2024-35903, CVE-2024-35980, CVE-2024-27020, CVE-2024-35955, CVE-2024-35964,     CVE-2024-26980, CVE-2024-35882, CVE-2024-35927, CVE-2024-35884, CVE-2024-35914, CVE-2024-35905,     CVE-2024-26925, CVE-2024-35885, CVE-2024-26990, CVE-2024-27012, CVE-2024-35969, CVE-2024-35862,     CVE-2024-35956, CVE-2024-35971, CVE-2024-27022, CVE-2024-35935, CVE-2024-26992, CVE-2024-27010,     CVE-2024-35892, CVE-2024-26999, CVE-2024-26989, CVE-2024-35963, CVE-2024-35981, CVE-2024-26997,     CVE-2024-35920, CVE-2024-35918, CVE-2024-35933, CVE-2024-35867, CVE-2024-35904, CVE-2024-35890,     CVE-2024-35968, CVE-2024-35917, CVE-2024-35897, CVE-2024-26922, CVE-2024-36026, CVE-2024-27013,     CVE-2024-26991, CVE-2024-26996, CVE-2024-35873, CVE-2024-26987, CVE-2024-35895, CVE-2024-36027,     CVE-2024-35896, CVE-2024-35894, CVE-2024-26983, CVE-2024-35966, CVE-2024-35967, CVE-2024-35945,     CVE-2024-27003, CVE-2024-35939, CVE-2024-35861, CVE-2024-26985, CVE-2024-27015, CVE-2024-35982,     CVE-2024-35912, CVE-2024-35979, CVE-2024-35879, CVE-2024-26982, CVE-2024-35891, CVE-2024-35925,     CVE-2024-35870, CVE-2024-27021, CVE-2024-35866, CVE-2024-27014, CVE-2024-27001, CVE-2024-27004,     CVE-2024-35953, CVE-2024-36021, CVE-2024-35931, CVE-2024-27007, CVE-2024-35922, CVE-2024-35872,     CVE-2024-35926, CVE-2024-27016, CVE-2024-26984, CVE-2024-35919, CVE-2024-35911, CVE-2024-26923,     CVE-2024-35929, CVE-2024-35887, CVE-2024-35893, CVE-2024-35898, CVE-2024-35930, CVE-2024-35934,     CVE-2024-35916, CVE-2024-35877, CVE-2024-26926, CVE-2024-35974, CVE-2024-36018, CVE-2024-27002,     CVE-2024-35975, CVE-2024-35864, CVE-2024-35958, CVE-2024-35944, CVE-2024-35985, CVE-2024-35940,     CVE-2024-35900, CVE-2024-27018, CVE-2024-26936, CVE-2024-36024, CVE-2024-26998, CVE-2024-35954,     CVE-2024-35878, CVE-2024-26928, CVE-2024-35952, CVE-2024-36020, CVE-2024-26986, CVE-2024-35950,     CVE-2024-35957, CVE-2024-35909, CVE-2024-27005, CVE-2024-35978, CVE-2024-35875, CVE-2024-35943,     CVE-2024-35970, CVE-2024-35863, CVE-2024-26993, CVE-2024-35865, CVE-2024-26995, CVE-2024-35888,     CVE-2024-35899, CVE-2024-35868, CVE-2023-52699, CVE-2024-26994, CVE-2024-26817, CVE-2024-35902,     CVE-2024-35977, CVE-2024-35961, CVE-2024-36025, CVE-2024-35936, CVE-2024-35913, CVE-2024-27017,     CVE-2024-35889, CVE-2024-35972, CVE-2024-35901, CVE-2024-26921, CVE-2024-26924, CVE-2024-35951,     CVE-2024-35860, CVE-2024-35907, CVE-2024-35910, CVE-2024-36022, CVE-2024-27019, CVE-2024-27009,     CVE-2024-26981, CVE-2024-35973, CVE-2024-35965, CVE-2024-36019, CVE-2024-35871, CVE-2024-27008,     CVE-2024-26811, CVE-2024-35908, CVE-2024-35921, CVE-2024-35942, CVE-2024-35946, CVE-2024-35924,     CVE-2024-27011, CVE-2024-35960, CVE-2024-27006, CVE-2024-35937, CVE-2024-35932)

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

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

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

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

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

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

    - ARM64 architecture;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Accessibility subsystem;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - Freescale SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - Network file system client;

    - Network file system server daemon;

    - NILFS2 file system;

    - Pstore file system;

    - SMB network file system;

    - UBI file system;

    - Netfilter;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - NFC subsystem;

    - Open vSwitch;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Unix domain sockets;

    - eXpress Data Path;

    - ALSA SH drivers;

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

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

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

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3842 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-3842-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     June 25, 2024                                 https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-5.10     Version        : 5.10.216-1~deb10u1     CVE ID         : CVE-2022-38096 CVE-2023-6270 CVE-2023-7042 CVE-2023-28746                      CVE-2023-47233 CVE-2023-52429 CVE-2023-52434 CVE-2023-52435                      CVE-2023-52447 CVE-2023-52458 CVE-2023-52482 CVE-2023-52486                      CVE-2023-52488 CVE-2023-52489 CVE-2023-52491 CVE-2023-52492                      CVE-2023-52493 CVE-2023-52497 CVE-2023-52498 CVE-2023-52583                      CVE-2023-52587 CVE-2023-52594 CVE-2023-52595 CVE-2023-52597                      CVE-2023-52598 CVE-2023-52599 CVE-2023-52600 CVE-2023-52601                      CVE-2023-52602 CVE-2023-52603 CVE-2023-52604 CVE-2023-52606                      CVE-2023-52607 CVE-2023-52614 CVE-2023-52615 CVE-2023-52616                      CVE-2023-52617 CVE-2023-52618 CVE-2023-52619 CVE-2023-52620                      CVE-2023-52622 CVE-2023-52623 CVE-2023-52627 CVE-2023-52635                      CVE-2023-52637 CVE-2023-52642 CVE-2023-52644 CVE-2023-52650                      CVE-2023-52656 CVE-2023-52669 CVE-2023-52670 CVE-2023-52672                      CVE-2023-52699 CVE-2023-52880 CVE-2024-0340 CVE-2024-0565                      CVE-2024-0607 CVE-2024-0841 CVE-2024-1151 CVE-2024-22099                      CVE-2024-23849 CVE-2024-23850 CVE-2024-23851 CVE-2024-24857                      CVE-2024-24858 CVE-2024-24861 CVE-2024-25739 CVE-2024-26581                      CVE-2024-26593 CVE-2024-26600 CVE-2024-26601 CVE-2024-26602                      CVE-2024-26606 CVE-2024-26610 CVE-2024-26614 CVE-2024-26615                      CVE-2024-26622 CVE-2024-26625 CVE-2024-26627 CVE-2024-26635                      CVE-2024-26636 CVE-2024-26640 CVE-2024-26641 CVE-2024-26642                      CVE-2024-26643 CVE-2024-26644 CVE-2024-26645 CVE-2024-26651                      CVE-2024-26654 CVE-2024-26659 CVE-2024-26663 CVE-2024-26664                      CVE-2024-26665 CVE-2024-26671 CVE-2024-26673 CVE-2024-26675                      CVE-2024-26679 CVE-2024-26684 CVE-2024-26685 CVE-2024-26687                      CVE-2024-26688 CVE-2024-26689 CVE-2024-26695 CVE-2024-26696                      CVE-2024-26697 CVE-2024-26698 CVE-2024-26702 CVE-2024-26704                      CVE-2024-26707 CVE-2024-26712 CVE-2024-26720 CVE-2024-26722                      CVE-2024-26727 CVE-2024-26733 CVE-2024-26735 CVE-2024-26736                      CVE-2024-26743 CVE-2024-26744 CVE-2024-26747 CVE-2024-26748                      CVE-2024-26749 CVE-2024-26751 CVE-2024-26752 CVE-2024-26753                      CVE-2024-26754 CVE-2024-26763 CVE-2024-26764 CVE-2024-26766                      CVE-2024-26771 CVE-2024-26772 CVE-2024-26773 CVE-2024-26776                      CVE-2024-26777 CVE-2024-26778 CVE-2024-26779 CVE-2024-26781                      CVE-2024-26782 CVE-2024-26787 CVE-2024-26788 CVE-2024-26790                      CVE-2024-26791 CVE-2024-26793 CVE-2024-26795 CVE-2024-26801                      CVE-2024-26804 CVE-2024-26805 CVE-2024-26808 CVE-2024-26809                      CVE-2024-26810 CVE-2024-26812 CVE-2024-26813 CVE-2024-26814                      CVE-2024-26816 CVE-2024-26817 CVE-2024-26820 CVE-2024-26825                      CVE-2024-26833 CVE-2024-26835 CVE-2024-26839 CVE-2024-26840                      CVE-2024-26843 CVE-2024-26845 CVE-2024-26846 CVE-2024-26848                      CVE-2024-26851 CVE-2024-26852 CVE-2024-26855 CVE-2024-26857                      CVE-2024-26859 CVE-2024-26861 CVE-2024-26862 CVE-2024-26863                      CVE-2024-26870 CVE-2024-26872 CVE-2024-26874 CVE-2024-26875                      CVE-2024-26877 CVE-2024-26878 CVE-2024-26880 CVE-2024-26882                      CVE-2024-26883 CVE-2024-26884 CVE-2024-26885 CVE-2024-26889                      CVE-2024-26891 CVE-2024-26894 CVE-2024-26895 CVE-2024-26897                      CVE-2024-26898 CVE-2024-26901 CVE-2024-26903 CVE-2024-26906                      CVE-2024-26907 CVE-2024-26910 CVE-2024-26917 CVE-2024-26922                      CVE-2024-26923 CVE-2024-26924 CVE-2024-26925 CVE-2024-26926                      CVE-2024-26931 CVE-2024-26934 CVE-2024-26935 CVE-2024-26937                      CVE-2024-26950 CVE-2024-26951 CVE-2024-26955 CVE-2024-26956                      CVE-2024-26957 CVE-2024-26958 CVE-2024-26960 CVE-2024-26961                      CVE-2024-26965 CVE-2024-26966 CVE-2024-26969 CVE-2024-26970                      CVE-2024-26973 CVE-2024-26974 CVE-2024-26976 CVE-2024-26978                      CVE-2024-26981 CVE-2024-26984 CVE-2024-26988 CVE-2024-26993                      CVE-2024-26994 CVE-2024-26997 CVE-2024-26999 CVE-2024-27000                      CVE-2024-27001 CVE-2024-27004 CVE-2024-27008 CVE-2024-27013                      CVE-2024-27020 CVE-2024-27024 CVE-2024-27025 CVE-2024-27028                      CVE-2024-27030 CVE-2024-27038 CVE-2024-27043 CVE-2024-27044                      CVE-2024-27045 CVE-2024-27046 CVE-2024-27047 CVE-2024-27051                      CVE-2024-27052 CVE-2024-27053 CVE-2024-27059 CVE-2024-27065                      CVE-2024-27073 CVE-2024-27074 CVE-2024-27075 CVE-2024-27076                      CVE-2024-27077 CVE-2024-27078 CVE-2024-27388 CVE-2024-27395                      CVE-2024-27396 CVE-2024-27405 CVE-2024-27410 CVE-2024-27412                      CVE-2024-27413 CVE-2024-27414 CVE-2024-27416 CVE-2024-27417                      CVE-2024-27419 CVE-2024-27431 CVE-2024-27436 CVE-2024-27437                      CVE-2024-35785 CVE-2024-35789 CVE-2024-35791 CVE-2024-35796                      CVE-2024-35805 CVE-2024-35806 CVE-2024-35807 CVE-2024-35809                      CVE-2024-35811 CVE-2024-35813 CVE-2024-35815 CVE-2024-35819                      CVE-2024-35821 CVE-2024-35822 CVE-2024-35823 CVE-2024-35825                      CVE-2024-35828 CVE-2024-35829 CVE-2024-35830 CVE-2024-35833                      CVE-2024-35835 CVE-2024-35837 CVE-2024-35845 CVE-2024-35847                      CVE-2024-35849 CVE-2024-35852 CVE-2024-35853 CVE-2024-35854                      CVE-2024-35855 CVE-2024-35871 CVE-2024-35877 CVE-2024-35879                      CVE-2024-35884 CVE-2024-35886 CVE-2024-35888 CVE-2024-35893                      CVE-2024-35895 CVE-2024-35896 CVE-2024-35897 CVE-2024-35898                      CVE-2024-35899 CVE-2024-35900 CVE-2024-35902 CVE-2024-35905                      CVE-2024-35910 CVE-2024-35915 CVE-2024-35922 CVE-2024-35925                      CVE-2024-35930 CVE-2024-35933 CVE-2024-35934 CVE-2024-35935                      CVE-2024-35936 CVE-2024-35940 CVE-2024-35944 CVE-2024-35950                      CVE-2024-35955 CVE-2024-35958 CVE-2024-35960 CVE-2024-35962                      CVE-2024-35967 CVE-2024-35969 CVE-2024-35973 CVE-2024-35976                      CVE-2024-35978 CVE-2024-35982 CVE-2024-35983 CVE-2024-35984                      CVE-2024-35988 CVE-2024-35990 CVE-2024-35996 CVE-2024-35997                      CVE-2024-36004 CVE-2024-36005 CVE-2024-36006 CVE-2024-36007                      CVE-2024-36008 CVE-2024-36020     Debian Bug     : 1064035

    Several vulnerabilities were discovered in the Linux kernel that may     lead to a privilege escalation, denial of service or information     leaks.

    For Debian 10 buster, these problems were fixed earlier in version     5.10.216-1~deb10u1.  This update also fixed a regression in kernel     documentation generation, and included many more bug fixes from stable     updates 5.10.210-5.10.216 inclusive.

    For the detailed security status of linux-5.10 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux-5.10

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian 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	名称	产品	系列	发布时间	最近更新时间	严重程度
207384	Ubuntu 22.04 LTS : Linux kernel vulnerabilities (USN-7019-1)	Nessus	Ubuntu Local Security Checks	2024/9/18	2026/2/3	high
202230	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6893-1)	Nessus	Ubuntu Local Security Checks	2024/7/11	2025/9/24	high
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	2025/7/25	2026/1/6	high
203020	Ubuntu 20.04 LTS : Linux kernel vulnerabilities (USN-6898-4)	Nessus	Ubuntu Local Security Checks	2024/7/23	2025/9/24	high
204313	Photon OS 4.0: Linux PHSA-2024-4.0-0607	Nessus	PhotonOS Local Security Checks	2024/7/24	2026/3/3	high
204159	Photon OS 5.0: Linux PHSA-2024-5.0-0274	Nessus	PhotonOS Local Security Checks	2024/7/24	2025/12/10	high
202689	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6898-3)	Nessus	Ubuntu Local Security Checks	2024/7/19	2024/12/31	high
204793	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6917-1)	Nessus	Ubuntu Local Security Checks	2024/7/26	2025/9/24	high
238008	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0084)	Nessus	NewStart CGSL Local Security Checks	2025/6/9	2025/6/18	high
239342	TencentOS Server 4: kernel (TSSA-2024:0981)	Nessus	Tencent Local Security Checks	2025/6/16	2025/12/4	high
204795	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6918-1)	Nessus	Ubuntu Local Security Checks	2024/7/26	2025/9/24	high
202578	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6898-2)	Nessus	Ubuntu Local Security Checks	2024/7/17	2025/9/24	high
201105	Debian dla-3842 : linux-config-5.10 - security update	Nessus	Debian Local Security Checks	2024/6/27	2025/10/30	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high

high