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

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

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

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

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

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

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

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Android drivers;

    - Serial ATA and Parallel ATA drivers;

    - ATM drivers;

    - Drivers core;

    - ATA over ethernet (AOE) driver;

    - Null block device driver;

    - TPM device driver;

    - Character device driver;

    - Clock framework and drivers;

    - Buffer Sharing and Synchronization framework;

    - ARM SCMI message protocol;

    - EFI core;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - ISDN/mISDN subsystem;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - STMicroelectronics network drivers;

    - Near Field Communication (NFC) drivers;

    - NTB driver;

    - Virtio pmem driver;

    - NVME drivers;

    - Device tree and open firmware driver;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Thermal drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - Userspace I/O drivers;

    - USB Device Class drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Type-C Port Controller Manager driver;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - 9P distributed file system;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - SMB network file system;

    - Bitmap API;

    - Network file system (NFS) superblock;

    - Objagg library;

    - Perf events;

    - Virtio network driver;

    - Bluetooth subsystem;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - Network traffic control;

    - Network sockets;

    - TCP network protocol;

    - BPF subsystem;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Kernel thread helper (kthread);

    - Locking primitives;

    - Padata parallel execution mechanism;

    - RCU subsystem;

    - Arbitrary resource management;

    - Scheduler infrastructure;

    - Static call mechanism;

    - Tracing infrastructure;

    - Radix Tree data structure library;

    - Kernel userspace event delivery library;

    - Memory management;

    - Amateur Radio drivers;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - Ethtool driver;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - Netlink;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - Wireless networking;

    - AppArmor security module;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - AudioScience HPI driver;

    - Amlogic Meson SoC drivers;

    - SoC audio core drivers;

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

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

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

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

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

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

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

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

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

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

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

    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;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Android drivers;

    - ATM drivers;

    - Drivers core;

    - Ublk userspace block driver;

    - Bluetooth drivers;

    - Character device driver;

    - Hardware crypto device drivers;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - Qualcomm firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Near Field Communication (NFC) drivers;

    - NVME drivers;

    - Device tree and open firmware driver;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Power supply drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - JFS file system;

    - Network file systems library;

    - 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;

    - Tracing file system;

    - Bitmap API;

    - BPF subsystem;

    - Memory Management;

    - Objagg library;

    - Perf events;

    - Virtio network driver;

    - VMware vSockets driver;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Locking primitives;

    - Padata parallel execution mechanism;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Radix Tree data structure library;

    - Kernel userspace event delivery library;

    - KUnit for arithmetic overflow checks;

    - Memory management;

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - Ethtool driver;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - Network traffic control;

    - SCTP protocol;

    - TIPC protocol;

    - Wireless networking;

    - AppArmor security module;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - AMD SoC Alsa drivers;

    - Texas InstrumentS Audio (ASoC/HDA) drivers;

    - SoC Audio for Freescale CPUs drivers;

    - Intel ASoC drivers;

    - Amlogic Meson SoC drivers;

    - SoC audio core drivers;

    - USB sound devices;

    - Real-Time Linux Analysis tools; (CVE-2024-46783, CVE-2024-44960, CVE-2024-46743, CVE-2024-45009,     CVE-2024-43820, CVE-2024-43888, CVE-2024-45010, CVE-2024-43839, CVE-2024-42304, CVE-2024-43846,     CVE-2024-42258, CVE-2024-45005, CVE-2024-46709, CVE-2024-46774, CVE-2024-43883, CVE-2024-43859,     CVE-2024-46721, CVE-2024-44944, CVE-2024-43913, CVE-2024-43843, CVE-2024-43845, CVE-2024-45018,     CVE-2024-43909, CVE-2024-46755, CVE-2024-42284, CVE-2024-42301, CVE-2024-46779, CVE-2024-44971,     CVE-2024-46711, CVE-2024-43889, CVE-2024-46842, CVE-2024-44978, CVE-2024-46803, CVE-2024-42277,     CVE-2024-43892, CVE-2024-45019, CVE-2024-44988, CVE-2024-46798, CVE-2024-44995, CVE-2024-43860,     CVE-2024-46762, CVE-2024-43831, CVE-2024-44990, CVE-2024-46845, CVE-2024-46765, CVE-2024-45012,     CVE-2024-44975, CVE-2024-46770, CVE-2024-46802, CVE-2024-44970, CVE-2024-46691, CVE-2024-43833,     CVE-2024-43876, CVE-2024-42292, CVE-2024-42291, CVE-2024-43891, CVE-2024-46788, CVE-2024-44938,     CVE-2024-46710, CVE-2024-42272, CVE-2024-43868, CVE-2024-43875, CVE-2024-45030, CVE-2024-46689,     CVE-2024-46859, CVE-2024-46795, CVE-2024-46683, CVE-2024-44999, CVE-2024-44942, CVE-2024-47669,     CVE-2024-42318, CVE-2024-43911, CVE-2024-46693, CVE-2024-42296, CVE-2024-43894, CVE-2024-45002,     CVE-2024-46673, CVE-2024-46852, CVE-2024-45001, CVE-2024-43907, CVE-2024-42319, CVE-2024-44972,     CVE-2024-43905, CVE-2024-45028, CVE-2024-46816, CVE-2024-46847, CVE-2024-46834, CVE-2024-44982,     CVE-2024-46807, CVE-2024-44948, CVE-2024-46685, CVE-2024-46811, CVE-2024-42317, CVE-2024-43818,     CVE-2024-46786, CVE-2024-43881, CVE-2024-42294, CVE-2024-46708, CVE-2024-42285, CVE-2024-44941,     CVE-2024-43823, CVE-2024-46694, CVE-2024-46730, CVE-2024-42259, CVE-2024-42270, CVE-2024-47658,     CVE-2024-46718, CVE-2024-44947, CVE-2024-46701, CVE-2024-43895, CVE-2024-43890, CVE-2024-46826,     CVE-2024-46687, CVE-2024-46768, CVE-2024-45025, CVE-2024-42267, CVE-2024-42263, CVE-2024-44958,     CVE-2024-44989, CVE-2024-43906, CVE-2024-43869, CVE-2024-43887, CVE-2024-42297, CVE-2024-46702,     CVE-2024-42320, CVE-2024-42322, CVE-2024-46857, CVE-2024-43861, CVE-2024-45008, CVE-2024-44969,     CVE-2024-46821, CVE-2024-44967, CVE-2024-43914, CVE-2024-46870, CVE-2024-46781, CVE-2024-43842,     CVE-2024-47665, CVE-2024-46753, CVE-2024-43866, CVE-2024-43886, CVE-2024-44939, CVE-2024-42312,     CVE-2024-46864, CVE-2024-46695, CVE-2024-46818, CVE-2024-45006, CVE-2024-43841, CVE-2024-46703,     CVE-2024-46749, CVE-2024-44986, CVE-2024-46717, CVE-2024-42273, CVE-2024-43856, CVE-2024-46777,     CVE-2024-44984, CVE-2024-46719, CVE-2024-46858, CVE-2024-43821, CVE-2024-46750, CVE-2024-43829,     CVE-2024-43817, CVE-2024-42281, CVE-2024-42287, CVE-2024-45007, CVE-2024-46793, CVE-2024-45003,     CVE-2024-45011, CVE-2024-47683, CVE-2024-44934, CVE-2024-46722, CVE-2024-46860, CVE-2024-42314,     CVE-2024-46675, CVE-2024-43899, CVE-2024-46752, CVE-2024-46851, CVE-2024-42310, CVE-2024-46853,     CVE-2024-39472, CVE-2024-43837, CVE-2024-45021, CVE-2024-46713, CVE-2024-44943, CVE-2024-46787,     CVE-2024-43893, CVE-2024-44946, CVE-2024-45026, CVE-2024-44996, CVE-2024-46761, CVE-2024-46723,     CVE-2024-42311, CVE-2024-42316, CVE-2024-47663, CVE-2024-44940, CVE-2024-43867, CVE-2024-42265,     CVE-2024-44950, CVE-2024-46867, CVE-2024-45020, CVE-2024-46707, CVE-2024-44966, CVE-2024-42309,     CVE-2024-46767, CVE-2024-46758, CVE-2024-46732, CVE-2024-42262, CVE-2024-46778, CVE-2024-43884,     CVE-2024-44991, CVE-2024-47668, CVE-2024-46698, CVE-2024-46825, CVE-2024-42302, CVE-2024-46716,     CVE-2024-46726, CVE-2024-43870, CVE-2024-42307, CVE-2024-46830, CVE-2024-43910, CVE-2024-46735,     CVE-2024-43828, CVE-2024-43904, CVE-2024-44965, CVE-2024-46831, CVE-2024-44979, CVE-2024-44961,     CVE-2024-46771, CVE-2024-46844, CVE-2024-46871, CVE-2024-43877, CVE-2024-46746, CVE-2024-44987,     CVE-2024-46676, CVE-2024-46766, CVE-2024-46731, CVE-2024-46810, CVE-2024-46806, CVE-2024-45000,     CVE-2024-42313, CVE-2024-45015, CVE-2024-46784, CVE-2024-43834, CVE-2024-46737, CVE-2024-46797,     CVE-2024-43908, CVE-2024-46724, CVE-2024-44980, CVE-2024-43847, CVE-2024-46679, CVE-2024-46681,     CVE-2024-43819, CVE-2024-46776, CVE-2024-44954, CVE-2024-45022, CVE-2024-46819, CVE-2024-46775,     CVE-2024-43824, CVE-2024-44953, CVE-2024-46759, CVE-2024-43873, CVE-2024-46756, CVE-2024-42303,     CVE-2024-46738, CVE-2024-42290, CVE-2024-42295, CVE-2024-43849, CVE-2024-44931, CVE-2024-46741,     CVE-2024-43863, CVE-2024-44974, CVE-2024-46829, CVE-2024-44959, CVE-2024-42315, CVE-2024-44983,     CVE-2024-46715, CVE-2024-46697, CVE-2024-43850, CVE-2024-46728, CVE-2024-44963, CVE-2024-46823,     CVE-2024-46692, CVE-2024-46760, CVE-2024-46705, CVE-2024-42261, CVE-2024-42321, CVE-2024-46785,     CVE-2024-46686, CVE-2024-49984, CVE-2024-46706, CVE-2024-45029, CVE-2024-46809, CVE-2024-43827,     CVE-2024-44998, CVE-2024-47667, CVE-2024-43835, CVE-2024-46866, CVE-2024-46841, CVE-2024-42286,     CVE-2024-43852, CVE-2024-43832, CVE-2024-46773, CVE-2024-46817, CVE-2024-46868, CVE-2024-46812,     CVE-2024-47660, CVE-2024-46725, CVE-2024-42288, CVE-2024-46824, CVE-2024-42269, CVE-2024-44957,     CVE-2024-45017, CVE-2024-46747, CVE-2024-47662, CVE-2024-46843, CVE-2024-46849, CVE-2024-43879,     CVE-2024-46751, CVE-2024-42298, CVE-2024-46861, CVE-2024-44993, CVE-2024-46729, CVE-2024-46846,     CVE-2024-46794, CVE-2024-43826, CVE-2024-44973, CVE-2024-46672, CVE-2024-44985, CVE-2024-46815,     CVE-2024-46822, CVE-2024-46754, CVE-2024-43854, CVE-2024-42278, CVE-2024-46720, CVE-2024-46677,     CVE-2024-46854, CVE-2024-43840, CVE-2024-43830, CVE-2024-46804, CVE-2024-45013, CVE-2024-46782,     CVE-2024-46840, CVE-2024-44977, CVE-2024-46838, CVE-2024-42264, CVE-2024-47661, CVE-2024-43857,     CVE-2023-52918, CVE-2024-44935, CVE-2024-46739, CVE-2024-43825, CVE-2024-43864, CVE-2024-47659,     CVE-2024-42260, CVE-2024-44962, CVE-2024-46835, CVE-2024-43871, CVE-2024-47674, CVE-2024-46827,     CVE-2024-42283, CVE-2024-42299, CVE-2024-46714, CVE-2024-46740, CVE-2024-46680, CVE-2024-46791,     CVE-2024-43912, CVE-2024-46813, CVE-2024-46733, CVE-2024-47664, CVE-2024-42279, CVE-2024-46850,     CVE-2024-42289, CVE-2024-46808, CVE-2024-43880, CVE-2024-46832, CVE-2024-42276, CVE-2024-44937,     CVE-2024-42274, CVE-2024-46772, CVE-2024-47666, CVE-2024-44956, CVE-2024-46763, CVE-2024-46805,     CVE-2023-52889, CVE-2024-46678, CVE-2024-43902, CVE-2024-46757, CVE-2024-46792, CVE-2024-42268,     CVE-2024-43853, CVE-2024-45027, CVE-2024-42305, CVE-2024-46828, CVE-2024-43900, CVE-2024-46848,     CVE-2024-46814, CVE-2024-46855, CVE-2024-46727, CVE-2024-46836, CVE-2024-46744, CVE-2024-46780,     CVE-2024-46745, CVE-2024-42306)

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: PCI: endpoint: Clean up error handling     in vpci_scan_bus() Smatch complains about inconsistent NULL checking in vpci_scan_bus():
    drivers/pci/endpoint/functions/pci-epf-vntb.c:1024 vpci_scan_bus() error: we previously assumed 'vpci_bus'     could be null (see line 1021) Instead of printing an error message and then crashing we should return an     error code and clean up. Also the NULL check is reversed so it prints an error for success instead of     failure. (CVE-2024-43875)

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

An update of the linux package has been released.

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

    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;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Android drivers;

    - ATM drivers;

    - Drivers core;

    - Ublk userspace block driver;

    - Bluetooth drivers;

    - Character device driver;

    - Hardware crypto device drivers;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - Qualcomm firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Near Field Communication (NFC) drivers;

    - NVME drivers;

    - Device tree and open firmware driver;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Power supply drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - JFS file system;

    - Network file systems library;

    - 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;

    - Tracing file system;

    - Bitmap API;

    - BPF subsystem;

    - Memory Management;

    - Objagg library;

    - Perf events;

    - Virtio network driver;

    - VMware vSockets driver;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Locking primitives;

    - Padata parallel execution mechanism;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Radix Tree data structure library;

    - Kernel userspace event delivery library;

    - KUnit for arithmetic overflow checks;

    - Memory management;

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - Ethtool driver;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - Network traffic control;

    - SCTP protocol;

    - TIPC protocol;

    - Wireless networking;

    - AppArmor security module;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - AMD SoC Alsa drivers;

    - Texas InstrumentS Audio (ASoC/HDA) drivers;

    - SoC Audio for Freescale CPUs drivers;

    - Intel ASoC drivers;

    - Amlogic Meson SoC drivers;

    - SoC audio core drivers;

    - USB sound devices;

    - Real-Time Linux Analysis tools; (CVE-2024-44979, CVE-2024-47658, CVE-2024-44970, CVE-2024-43913,     CVE-2024-46816, CVE-2024-46738, CVE-2024-46777, CVE-2024-46730, CVE-2024-46811, CVE-2024-44954,     CVE-2024-42317, CVE-2024-42279, CVE-2024-45002, CVE-2024-43826, CVE-2024-44967, CVE-2024-46721,     CVE-2024-46763, CVE-2024-43856, CVE-2024-42284, CVE-2024-42289, CVE-2024-46806, CVE-2024-46776,     CVE-2024-43843, CVE-2024-42298, CVE-2024-43832, CVE-2024-42321, CVE-2024-42292, CVE-2024-44982,     CVE-2024-43842, CVE-2024-46772, CVE-2024-46702, CVE-2024-45017, CVE-2024-43888, CVE-2024-47683,     CVE-2024-46714, CVE-2024-43899, CVE-2024-45025, CVE-2024-46751, CVE-2024-45020, CVE-2024-44977,     CVE-2024-46853, CVE-2024-46753, CVE-2024-46792, CVE-2024-46675, CVE-2024-46805, CVE-2024-43890,     CVE-2024-46703, CVE-2024-43841, CVE-2024-44960, CVE-2024-46846, CVE-2024-46798, CVE-2024-44965,     CVE-2024-46812, CVE-2024-43835, CVE-2024-43839, CVE-2024-43886, CVE-2024-46843, CVE-2024-50264,     CVE-2024-46706, CVE-2024-46851, CVE-2024-46758, CVE-2024-45027, CVE-2024-43887, CVE-2024-42278,     CVE-2024-46701, CVE-2024-46708, CVE-2024-46817, CVE-2024-46871, CVE-2024-46771, CVE-2024-42304,     CVE-2024-43877, CVE-2024-44996, CVE-2024-46741, CVE-2024-46842, CVE-2024-43902, CVE-2024-43818,     CVE-2024-47662, CVE-2024-44931, CVE-2024-46793, CVE-2024-46746, CVE-2024-46782, CVE-2024-43914,     CVE-2024-43824, CVE-2024-46767, CVE-2024-43871, CVE-2024-44971, CVE-2024-47666, CVE-2024-45008,     CVE-2024-42263, CVE-2024-46815, CVE-2024-46824, CVE-2024-45015, CVE-2024-45000, CVE-2024-46841,     CVE-2024-46770, CVE-2024-44942, CVE-2024-46679, CVE-2024-46724, CVE-2024-46759, CVE-2024-43845,     CVE-2024-46795, CVE-2024-46818, CVE-2024-44988, CVE-2024-46807, CVE-2024-46787, CVE-2024-43894,     CVE-2024-46803, CVE-2024-44947, CVE-2024-46786, CVE-2024-46689, CVE-2024-46686, CVE-2024-42290,     CVE-2024-46868, CVE-2024-43857, CVE-2024-43909, CVE-2023-52889, CVE-2024-44944, CVE-2024-44973,     CVE-2024-43905, CVE-2024-44938, CVE-2024-43864, CVE-2024-46850, CVE-2024-43867, CVE-2024-43819,     CVE-2024-46691, CVE-2024-47664, CVE-2024-46821, CVE-2024-46867, CVE-2024-46716, CVE-2024-43881,     CVE-2024-46788, CVE-2024-43912, CVE-2024-43904, CVE-2024-46727, CVE-2024-46680, CVE-2024-44985,     CVE-2024-46813, CVE-2024-47668, CVE-2024-42277, CVE-2024-42291, CVE-2024-45003, CVE-2024-42309,     CVE-2024-44937, CVE-2024-44953, CVE-2024-46718, CVE-2024-42276, CVE-2024-45028, CVE-2024-43863,     CVE-2024-46866, CVE-2024-42258, CVE-2024-42273, CVE-2024-46717, CVE-2024-46797, CVE-2024-46854,     CVE-2024-44972, CVE-2024-46791, CVE-2024-45010, CVE-2024-43825, CVE-2024-46775, CVE-2024-46745,     CVE-2024-46808, CVE-2024-46831, CVE-2024-45018, CVE-2024-42319, CVE-2024-46822, CVE-2024-43883,     CVE-2024-46722, CVE-2024-46694, CVE-2024-45009, CVE-2024-42320, CVE-2024-46825, CVE-2024-43821,     CVE-2024-46749, CVE-2024-45006, CVE-2024-43895, CVE-2024-44950, CVE-2024-43827, CVE-2024-43876,     CVE-2024-47659, CVE-2024-44989, CVE-2024-46804, CVE-2024-46754, CVE-2024-46766, CVE-2024-46728,     CVE-2024-46828, CVE-2024-46826, CVE-2024-46810, CVE-2024-44963, CVE-2024-44934, CVE-2024-43829,     CVE-2024-42268, CVE-2024-43850, CVE-2024-43853, CVE-2024-43854, CVE-2024-43892, CVE-2024-43859,     CVE-2024-42285, CVE-2024-44962, CVE-2024-46725, CVE-2024-46814, CVE-2024-44935, CVE-2024-42264,     CVE-2024-42260, CVE-2024-46858, CVE-2024-46778, CVE-2024-46774, CVE-2024-46848, CVE-2024-45013,     CVE-2024-43837, CVE-2024-46683, CVE-2024-46757, CVE-2024-46726, CVE-2024-43831, CVE-2024-46737,     CVE-2024-43893, CVE-2024-46823, CVE-2024-42302, CVE-2024-44990, CVE-2024-46755, CVE-2024-46707,     CVE-2024-43833, CVE-2024-44940, CVE-2024-42259, CVE-2024-46855, CVE-2024-46827, CVE-2024-46809,     CVE-2024-46836, CVE-2024-43907, CVE-2024-42312, CVE-2024-46692, CVE-2024-42297, CVE-2024-46864,     CVE-2024-42299, CVE-2024-45011, CVE-2024-46838, CVE-2024-44993, CVE-2024-46802, CVE-2024-44966,     CVE-2024-46739, CVE-2024-46780, CVE-2024-44961, CVE-2024-42316, CVE-2024-47660, CVE-2024-46859,     CVE-2024-46762, CVE-2024-43861, CVE-2024-45012, CVE-2024-46784, CVE-2024-43908, CVE-2024-46832,     CVE-2024-44969, CVE-2024-46750, CVE-2024-44958, CVE-2024-46740, CVE-2024-46829, CVE-2024-43873,     CVE-2024-49984, CVE-2024-44983, CVE-2024-42288, CVE-2024-46735, CVE-2024-46676, CVE-2024-43823,     CVE-2024-46779, CVE-2024-46744, CVE-2024-42310, CVE-2024-44980, CVE-2024-46870, CVE-2024-42307,     CVE-2024-46768, CVE-2024-44984, CVE-2024-45007, CVE-2024-46710, CVE-2024-44978, CVE-2024-46723,     CVE-2024-46845, CVE-2024-44999, CVE-2024-42311, CVE-2024-43884, CVE-2024-44939, CVE-2024-44974,     CVE-2024-42314, CVE-2024-42318, CVE-2024-39472, CVE-2024-46693, CVE-2024-46794, CVE-2024-46844,     CVE-2024-46695, CVE-2024-46720, CVE-2024-46860, CVE-2024-46835, CVE-2024-47665, CVE-2024-46715,     CVE-2024-42305, CVE-2024-46773, CVE-2024-45030, CVE-2024-46697, CVE-2024-46705, CVE-2024-42286,     CVE-2024-46834, CVE-2024-46681, CVE-2024-53057, CVE-2024-42303, CVE-2024-46678, CVE-2024-46756,     CVE-2023-52918, CVE-2024-43860, CVE-2024-43911, CVE-2024-43880, CVE-2024-43910, CVE-2024-44975,     CVE-2024-44959, CVE-2024-46747, CVE-2024-43846, CVE-2024-42274, CVE-2024-46672, CVE-2024-43852,     CVE-2024-46709, CVE-2024-42306, CVE-2024-42281, CVE-2024-46849, CVE-2024-46719, CVE-2024-43830,     CVE-2024-46685, CVE-2024-44998, CVE-2024-42313, CVE-2024-43820, CVE-2024-44991, CVE-2024-47674,     CVE-2024-46785, CVE-2024-45021, CVE-2024-46677, CVE-2024-43870, CVE-2024-46698, CVE-2024-43900,     CVE-2024-44956, CVE-2024-43849, CVE-2024-46687, CVE-2024-42296, CVE-2024-46830, CVE-2024-47669,     CVE-2024-46732, CVE-2024-46733, CVE-2024-46852, CVE-2024-43906, CVE-2024-43847, CVE-2024-42294,     CVE-2024-46731, CVE-2024-45029, CVE-2024-47667, CVE-2024-42272, CVE-2024-45022, CVE-2024-43879,     CVE-2024-46765, CVE-2024-45026, CVE-2024-44986, CVE-2024-44995, CVE-2024-47663, CVE-2024-42262,     CVE-2024-43889, CVE-2024-44987, CVE-2024-43866, CVE-2024-42265, CVE-2024-46847, CVE-2024-46673,     CVE-2024-46783, CVE-2024-46761, CVE-2024-46840, CVE-2024-42301, CVE-2024-43868, CVE-2024-45005,     CVE-2024-42322, CVE-2024-43828, CVE-2024-43834, CVE-2024-43891, CVE-2024-46861, CVE-2024-42261,     CVE-2024-43875, CVE-2024-43840, CVE-2024-42287, CVE-2024-46752, CVE-2024-46711, CVE-2024-46713,     CVE-2024-44943, CVE-2024-46743, CVE-2024-43869, CVE-2024-46781, CVE-2024-44946, CVE-2024-42283,     CVE-2024-47661, CVE-2024-43817, CVE-2024-46819, CVE-2024-42267, CVE-2024-46729, CVE-2024-46857,     CVE-2024-42295, CVE-2024-46760, CVE-2024-42315, CVE-2024-45019, CVE-2024-44948, CVE-2024-44941,     CVE-2024-42269, CVE-2024-44957, CVE-2024-49967)

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

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

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

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


    The following security bugs were fixed:

    - CVE-2024-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session     (bsc#1229827).
    - CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
    - CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
    - CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).
    - CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).
    - CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).
    - CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).
    - CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)
    - CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).
    - CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).
    - CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).
    - CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)
    - CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).
    - CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).
    - CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)
    - CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).
    - CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level() (bsc#1229353).
    - CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)
    - CVE-2024-42308: Update DRM patch reference (bsc#1229411)
    - CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).
    - CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).
    - CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).
    - CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).
    - CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)
    - CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)
    - CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).
    - CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
    - CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).
    - CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init()     (bsc#1229402).
    - CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).
    - CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).
    - CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket     (bsc#1228989).
    - CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).
    - CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).
    - CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).
    - CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).
    - CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).
    - CVE-2024-42159: scsi: mpi3mr: fix sanitise num_phys (bsc#1228754).
    - CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
    - CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727).
    - CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).
    - CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).
    - CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).
    - CVE-2024-42145: IB/core: Implement a limit on UMAD receive List (bsc#1228743).
    - CVE-2024-42142: net/mlx5: E-switch, Create ingress ACL when needed (bsc#1228491).
    - CVE-2024-42139: ice: Fix improper extts handling (bsc#1228503).
    - CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file     (bsc#1228500).
    - CVE-2024-42124: scsi: qedf: Make qedf_execute_tmf() non-preemptible (bsc#1228705).
    - CVE-2024-42122: drm/amd/display: Add NULL pointer check for kzalloc (bsc#1228591).
    - CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).
    - CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx()     (bsc#1228501).
    - CVE-2024-42109: netfilter: nf_tables: unconditionally flush pending work before notifier (bsc#1228505).
    - CVE-2024-42107: ice: Do not process extts if PTP is disabled (bsc#1228494).
    - CVE-2024-42106: inet_diag: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).
    - CVE-2024-42096: x86: stop playing stack games in profile_pc() (bsc#1228633).
    - CVE-2024-42095: serial: 8250_omap: Fix Errata i2310 with RX FIFO level check (bsc#1228446).
    - CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack (bsc#1228680).
    - CVE-2024-42082: xdp: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).
    - CVE-2024-42079: gfs2: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).
    - CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).
    - CVE-2024-42070: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers     (bsc#1228470).
    - CVE-2024-41084: cxl/region: Avoid null pointer dereference in region lookup (bsc#1228472).
    - CVE-2024-41081: ila: block BH in ila_output() (bsc#1228617).
    - CVE-2024-41080: io_uring: fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).
    - CVE-2024-41078: btrfs: qgroup: fix quota root leak after quota disable failure (bsc#1228655).
    - CVE-2024-41076: NFSv4: Fix memory leak in nfs4_set_security_label (bsc#1228649).
    - CVE-2024-41075: cachefiles: add consistency check for copen/cread (bsc#1228646).
    - CVE-2024-41074: cachefiles: Set object to close if ondemand_id < 0 in copen (bsc#1228643).
    - CVE-2024-41070: KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).
    - CVE-2024-41069: ASoC: topology: Fix route memory corruption (bsc#1228644).
    - CVE-2024-41068: s390/sclp: Fix sclp_init() cleanup on failure (bsc#1228579).
    - CVE-2024-41066: ibmvnic: add tx check to prevent skb leak (bsc#1228640).
    - CVE-2024-41064: powerpc/eeh: avoid possible crash when edev->pdev changes (bsc#1228599).
    - CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).
    - CVE-2024-41058: cachefiles: fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).
    - CVE-2024-41057: cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).
    - CVE-2024-41051: cachefiles: wait for ondemand_object_worker to finish when dropping object     (bsc#1228468).
    - CVE-2024-41050: cachefiles: cyclic allocation of msg_id to avoid reuse (bsc#1228499).
    - CVE-2024-41048: skmsg: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).
    - CVE-2024-41044: ppp: reject claimed-as-LCP but actually malformed packets (bsc#1228530).
    - CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).
    - CVE-2024-41040: net/sched: Fix UAF when resolving a clash (bsc#1228518).
    - CVE-2024-41036: net: ks8851: Fix deadlock with the SPI chip variant (bsc#1228496).
    - CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask (bsc#1228460).
    - CVE-2024-41020: filelock: Fix fcntl/close race recovery compat path (bsc#1228427).
    - CVE-2024-41015: ocfs2: add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).
    - CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected (bsc#1228247).
    - CVE-2024-41010: bpf: Fix too early release of tcx_entry (bsc#1228021).
    - CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).
    - CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).
    - CVE-2024-41000: block/ioctl: prefer different overflow check (bsc#1227867).
    - CVE-2024-40995: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).
    - CVE-2024-40994: ptp: fix integer overflow in max_vclocks_store (bsc#1227829).
    - CVE-2024-40989: KVM: arm64: Disassociate vcpus from redistributor region on teardown (bsc#1227823).
    - CVE-2024-40978: scsi: qedi: Fix crash while reading debugfs attribute (bsc#1227929).
    - CVE-2024-40959: xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).
    - CVE-2024-40958: netns: Make get_net_ns() handle zero refcount net (bsc#1227812).
    - CVE-2024-40957: seg6: fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors     (bsc#1227811).
    - CVE-2024-40956: dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).
    - CVE-2024-40954: net: do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)
    - CVE-2024-40939: net: wwan: iosm: Fix tainted pointer delete is case of region creation fail     (bsc#1227799).
    - CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).
    - CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
    - CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
    - CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).
    - CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
    - CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).
    - CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)
    - CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).
    - CVE-2024-36979: net: bridge: mst: fix vlan use-after-free (bsc#1226604).
    - CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).
    - CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).
    - CVE-2024-36911: hv_netvsc: Do not free decrypted memory (bsc#1225745).
    - CVE-2024-36910: uio_hv_generic: Do not free decrypted memory (bsc#1225717).
    - CVE-2024-36909: Drivers: hv: vmbus: Do not free ring buffers that couldn't be re-encrypted     (bsc#1225744).
    - CVE-2024-36881: mm/userfaultfd: Fix reset ptes when close() for wr-protected (bsc#1225718).
    - CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)
    - CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()     (bsc#1226801)
    - CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch     (bsc#1226798)
    - CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).
    - CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
    - CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion     (bsc#1224510).
    - CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).
    - CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in     clk_mt8135_apmixed_probe() (bsc#1224711).
    - CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).
    - CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).
    - CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).
    - CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).
    - CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).
    - CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)
    - CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of     the list of MDB events to replay (bsc#1222973).
    - CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).
    - CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).
    - CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path     (bsc#1222633).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).
    - CVE-2024-26677: blacklist.conf: Add e7870cf13d20 ('rxrpc: Fix delayed ACKs to not set the reference     serial number') (bsc#1222387)
    - CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).
    - CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).
    - CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
    - CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).
    - CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).
    - CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).
    - CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).
    - CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section->usage (bsc#1221326).



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

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

The remote 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.

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
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
213500	Ubuntu 22.04 LTS : Linux kernel (HWE) vulnerabilities (USN-7154-2)	Nessus	Ubuntu Local Security Checks	2025/1/6	2026/1/6	high
229408	Linux Distros Unpatched Vulnerability : CVE-2024-43875	Nessus	Misc.	2025/3/5	2026/7/17	medium
206730	Photon OS 5.0: Linux PHSA-2024-5.0-0359	Nessus	PhotonOS Local Security Checks	2024/9/6	2026/7/22	high
213655	Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel (Azure) vulnerabilities (USN-7196-1)	Nessus	Ubuntu Local Security Checks	2025/1/9	2026/1/6	high
207676	SUSE SLED15: cluster-md-kmp-64kb / cluster-md-kmp-default / dlm-kmp-64kb / etc (SUSE-SU-2024:3383-1)	Nessus	SuSE Local Security Checks	2024/9/24	2026/6/26	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

检测

插件搜索

critical

high

high

medium

high

high

high

high