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

  - A vulnerability classified as problematic has been found in Linux Kernel. Affected is the function     j1939_session_destroy of the file net/can/j1939/transport.c. The manipulation leads to memory leak. It is     recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211932.
    (CVE-2022-3633)

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

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

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

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

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

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

    Maxim Suhanov discovered that the NTFS file system implementation in the Linux kernel did not properly     validate file name length in certain situations, leading to an out-of-bounds read. An attacker could use     this to construct a malicious NTFS image that, when mounted and operated on, could expose sensitive     information (kernel memory). (CVE-2023-45896)

    It was discovered that some AMD processors did not properly clear data in the floating point divider unit     during speculative execution. A local attacker could use this to expose sensitive information.
    (CVE-2025-54505)

    It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the     operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a     higher privilege level, resulting in privilege escalation. (CVE-2025-54518)

    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;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - ATM drivers;

    - Drivers core;

    - Power management core;

    - DRBD Distributed Replicated Block Device drivers;

    - RNBD block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Character device driver;

    - TPM device driver;

    - Clocksource drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - CPU idle management framework;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - Arm Firmware Framework for ARMv8-A(FFA);

    - EFI core;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - IIO subsystem;

    - IIO ADC drivers;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - MediaTek SMI driver;

    - NVIDIA Tegra memory controller driver;

    - Multifunction device drivers;

    - IBM Advanced System Management driver;

    - MMC subsystem;

    - MTD block device drivers;

    - Network drivers;

    - Ethernet bonding driver;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - STMicroelectronics network drivers;

    - MediaTek network drivers;

    - Near Field Communication (NFC) drivers;

    - NTB driver;

    - NVDIMM (Non-Volatile Memory Device) drivers;

    - NVME drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Broadcom BCM2835 power domain driver;

    - Power supply drivers;

    - RapidIO drivers;

    - Remote Processor subsystem;

    - RPMSG subsystem;

    - SCSI subsystem;

    - Freescale SoC drivers;

    - Texas Instruments SoC drivers;

    - SPI subsystem;

    - Greybus lights staging drivers;

    - Media staging drivers;

    - Realtek RTL8723BS SDIO drivers;

    - SM750 framebuffer staging driver;

    - TCM subsystem;

    - TTY drivers;

    - UFS subsystem;

    - Cadence USB3 driver;

    - USB Device Class drivers;

    - ULPI bus;

    - USB core drivers;

    - DesignWare USB2 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Mustek MDC800 USB digital camera driver;

    - USB YUREX driver;

    - Renesas USBHS Controller drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - FUSE (File system in Userspace);

    - GFS2 file system;

    - HFS+ file system;

    - JFS file system;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - Proc file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - SquashFS file system;

    - UDF file system;

    - XFS file system;

    - Audit subsystem;

    - RAS (Reliability, Availability, Serviceability) subsystem;

    - Software nodes and device properties;

    - Memory Management;

    - KVM subsystem;

    - Memory management;

    - PPP protocol drivers and compressors;

    - Linux Security Modules (LSM) Framework;

    - Network traffic control;

    - Bluetooth subsystem;

    - MAC80211 subsystem;

    - Netfilter;

    - IP tunnels definitions;

    - Tracing infrastructure;

    - User-space API (UAPI);

    - io_uring subsystem;

    - BPF subsystem;

    - Control group (cgroup);

    - Kernel fork() syscall;

    - Kernel futex primitives;

    - Kernel kexec() syscall;

    - Kernel module support;

    - Scheduler infrastructure;

    - Cryptographic library;

    - KASAN memory debugging framework;

    - Asynchronous Transfer Mode (ATM) subsystem;

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

    - Ethernet bridge;

    - CAIF protocol;

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - Distributed Switch Architecture;

    - IPv4 networking;

    - IPv6 networking;

    - XFRM subsystem;

    - L2TP protocol;

    - Management Component Transport Protocol (MCTP);

    - Multipath TCP;

    - NCSI (Network Controller Sideband Interface) driver;

    - NFC subsystem;

    - Open vSwitch;

    - Phonet protocol;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - RF switch subsystem;

    - Rose network layer;

    - RxRPC session sockets;

    - SCTP protocol;

    - SMC sockets;

    - Stream parser;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - X.25 network layer;

    - eXpress Data Path;

    - AppArmor security module;

    - Simplified Mandatory Access Control Kernel framework;

    - ALSA framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - AudioScience HPI driver;

    - Creative Sound Blaster X-Fi driver;

    - AMD SoC Alsa drivers;

    - SoC audio core drivers;

    - STI ASoC drivers;

    - USB sound devices; (CVE-2022-49803, CVE-2022-49961, CVE-2022-50073, CVE-2022-50116, CVE-2022-50552,     CVE-2023-52682, CVE-2023-52737, CVE-2023-53545, CVE-2023-53596, CVE-2023-53629, CVE-2024-27389,     CVE-2024-35865, CVE-2024-36898, CVE-2024-36922, CVE-2024-41079, CVE-2024-46715, CVE-2024-46770,     CVE-2024-47809, CVE-2024-50012, CVE-2024-53221, CVE-2024-56557, CVE-2024-56584, CVE-2024-56657,     CVE-2024-56719, CVE-2024-56727, CVE-2025-21712, CVE-2025-21739, CVE-2025-21863, CVE-2025-22107,     CVE-2025-23141, CVE-2025-37786, CVE-2025-38006, CVE-2025-38105, CVE-2025-38192, CVE-2025-38250,     CVE-2025-38562, CVE-2025-38626, CVE-2025-38659, CVE-2025-38710, CVE-2025-39748, CVE-2025-39764,     CVE-2025-40005, CVE-2025-40016, CVE-2025-40103, CVE-2025-40323, CVE-2025-68206, CVE-2025-68239,     CVE-2025-68256, CVE-2025-68307, CVE-2025-68358, CVE-2025-71150, CVE-2025-71161, CVE-2025-71221,     CVE-2025-71232, CVE-2025-71233, CVE-2025-71235, CVE-2025-71236, CVE-2025-71237, CVE-2025-71238,     CVE-2025-71239, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71274, CVE-2025-71287,     CVE-2025-71292, CVE-2025-71304, CVE-2026-23031, CVE-2026-23066, CVE-2026-23100, CVE-2026-23113,     CVE-2026-23141, CVE-2026-23157, CVE-2026-23169, CVE-2026-23204, CVE-2026-23220, CVE-2026-23221,     CVE-2026-23222, CVE-2026-23227, CVE-2026-23228, CVE-2026-23229, CVE-2026-23234, CVE-2026-23235,     CVE-2026-23236, CVE-2026-23237, CVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,     CVE-2026-23253, CVE-2026-23266, CVE-2026-23270, CVE-2026-23277, CVE-2026-23279, CVE-2026-23281,     CVE-2026-23286, CVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23293, CVE-2026-23296,     CVE-2026-23298, CVE-2026-23300, CVE-2026-23303, CVE-2026-23304, CVE-2026-23307, CVE-2026-23312,     CVE-2026-23318, CVE-2026-23324, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,     CVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23362, CVE-2026-23365,     CVE-2026-23367, CVE-2026-23368, CVE-2026-23370, CVE-2026-23372, CVE-2026-23379, CVE-2026-23381,     CVE-2026-23382, CVE-2026-23388, CVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,     CVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23420, CVE-2026-23434,     CVE-2026-23438, CVE-2026-23439, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446, CVE-2026-23452,     CVE-2026-23454, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23462,     CVE-2026-23463, CVE-2026-23474, CVE-2026-31393, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,     CVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31415,     CVE-2026-31416, CVE-2026-31417, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423, CVE-2026-31424,     CVE-2026-31425, CVE-2026-31427, CVE-2026-31428, CVE-2026-31433, CVE-2026-31446, CVE-2026-31447,     CVE-2026-31450, CVE-2026-31452, CVE-2026-31454, CVE-2026-31455, CVE-2026-31464, CVE-2026-31466,     CVE-2026-31467, CVE-2026-31469, CVE-2026-31473, CVE-2026-31476, CVE-2026-31480, CVE-2026-31483,     CVE-2026-31485, CVE-2026-31489, CVE-2026-31494, CVE-2026-31495, CVE-2026-31497, CVE-2026-31498,     CVE-2026-31507, CVE-2026-31508, CVE-2026-31509, CVE-2026-31510, CVE-2026-31512, CVE-2026-31515,     CVE-2026-31518, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524, CVE-2026-31532,     CVE-2026-31540, CVE-2026-31545, CVE-2026-31546, CVE-2026-31549, CVE-2026-31550, CVE-2026-31551,     CVE-2026-31552, CVE-2026-31555, CVE-2026-31565, CVE-2026-31570, CVE-2026-31576, CVE-2026-31577,     CVE-2026-31578, CVE-2026-31580, CVE-2026-31581, CVE-2026-31583, CVE-2026-31585, CVE-2026-31586,     CVE-2026-31588, CVE-2026-31590, CVE-2026-31594, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598,     CVE-2026-31599, CVE-2026-31602, CVE-2026-31603, CVE-2026-31605, CVE-2026-31615, CVE-2026-31616,     CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,     CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31630,     CVE-2026-31634, CVE-2026-31642, CVE-2026-31651, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,     CVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31670,     CVE-2026-31671, CVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31676, CVE-2026-31679,     CVE-2026-31680, CVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31687,     CVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699,     CVE-2026-31701, CVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31726, CVE-2026-31728,     CVE-2026-31737, CVE-2026-31738, CVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,     CVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,     CVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31770, CVE-2026-31773, CVE-2026-31778,     CVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43014, CVE-2026-43015, CVE-2026-43020,     CVE-2026-43024, CVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,     CVE-2026-43035, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43046, CVE-2026-43047,     CVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43058, CVE-2026-43060,     CVE-2026-43061, CVE-2026-43062, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,     CVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43085,     CVE-2026-43089, CVE-2026-43093, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,     CVE-2026-43105, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43123,     CVE-2026-43124, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134, CVE-2026-43135,     CVE-2026-43136, CVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43145, CVE-2026-43147,     CVE-2026-43148, CVE-2026-43149, CVE-2026-43152, CVE-2026-43156, CVE-2026-43158, CVE-2026-43159,     CVE-2026-43163, CVE-2026-43168, CVE-2026-43171, CVE-2026-43180, CVE-2026-43182, CVE-2026-43183,     CVE-2026-43184, CVE-2026-43187, CVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43200,     CVE-2026-43202, CVE-2026-43203, CVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,     CVE-2026-43211, CVE-2026-43218, CVE-2026-43223, CVE-2026-43225, CVE-2026-43226, CVE-2026-43227,     CVE-2026-43230, CVE-2026-43231, CVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43241,     CVE-2026-43242, CVE-2026-43246, CVE-2026-43251, CVE-2026-43255, CVE-2026-43257, CVE-2026-43261,     CVE-2026-43262, CVE-2026-43264, CVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,     CVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,     CVE-2026-43287, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295, CVE-2026-43296, CVE-2026-43302,     CVE-2026-43312, CVE-2026-43313, CVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43324,     CVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,     CVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343, CVE-2026-43357, CVE-2026-43363,     CVE-2026-43365, CVE-2026-43370, CVE-2026-43373, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,     CVE-2026-43386, CVE-2026-43387, CVE-2026-43405, CVE-2026-43411, CVE-2026-43420, CVE-2026-43425,     CVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429, CVE-2026-43430, CVE-2026-43432,     CVE-2026-43439, CVE-2026-43445, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,     CVE-2026-43453, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43469, CVE-2026-43472,     CVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480, CVE-2026-43484, CVE-2026-43496,     CVE-2026-43497, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,     CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,     CVE-2026-45846, CVE-2026-45847, CVE-2026-45848, CVE-2026-45852, CVE-2026-45856, CVE-2026-45857,     CVE-2026-45860, CVE-2026-45862, CVE-2026-45864, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,     CVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45873, CVE-2026-45875, CVE-2026-45879,     CVE-2026-45883, CVE-2026-45885, CVE-2026-45890, CVE-2026-45891, CVE-2026-45899, CVE-2026-45902,     CVE-2026-45904, CVE-2026-45911, CVE-2026-45912, CVE-2026-45915, CVE-2026-45916, CVE-2026-45919,     CVE-2026-45920, CVE-2026-45924, CVE-2026-45935, CVE-2026-45936, CVE-2026-45941, CVE-2026-45946,     CVE-2026-45948, CVE-2026-45954, CVE-2026-45956, CVE-2026-45958, CVE-2026-45960, CVE-2026-45964,     CVE-2026-45965, CVE-2026-45968, CVE-2026-45969, CVE-2026-45970, CVE-2026-45974, CVE-2026-45978,     CVE-2026-45983, CVE-2026-45984, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987, CVE-2026-45994,     CVE-2026-46002, CVE-2026-46004, CVE-2026-46006, CVE-2026-46009, CVE-2026-46015, CVE-2026-46018,     CVE-2026-46019, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46027, CVE-2026-46033,     CVE-2026-46037, CVE-2026-46040, CVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,     CVE-2026-46050, CVE-2026-46051, CVE-2026-46053, CVE-2026-46062, CVE-2026-46064, CVE-2026-46070,     CVE-2026-46072, CVE-2026-46077, CVE-2026-46080, CVE-2026-46082, CVE-2026-46088, CVE-2026-46098,     CVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46107, CVE-2026-46108, CVE-2026-46112,     CVE-2026-46120, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46127, CVE-2026-46128,     CVE-2026-46132, CVE-2026-46133, CVE-2026-46137, CVE-2026-46146, CVE-2026-46149, CVE-2026-46150,     CVE-2026-46151, CVE-2026-46161, CVE-2026-46163, CVE-2026-46167, CVE-2026-46168, CVE-2026-46172,     CVE-2026-46174, CVE-2026-46177, CVE-2026-46178, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,     CVE-2026-46189, CVE-2026-46197, CVE-2026-46198, CVE-2026-46205, CVE-2026-46206, CVE-2026-46209,     CVE-2026-46212, CVE-2026-46214, CVE-2026-46219, CVE-2026-46220, CVE-2026-46227, CVE-2026-46230,     CVE-2026-46231, CVE-2026-46233, CVE-2026-46234, CVE-2026-46236, CVE-2026-46238, CVE-2026-46249,     CVE-2026-46250, CVE-2026-46253, CVE-2026-46259, CVE-2026-46267, CVE-2026-46270, CVE-2026-46273,     CVE-2026-46274, CVE-2026-46275, CVE-2026-46285, CVE-2026-46294, CVE-2026-46301, CVE-2026-46303,     CVE-2026-46304, CVE-2026-46307, CVE-2026-46319, CVE-2026-46328, CVE-2026-52911, CVE-2026-52912,     CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921,     CVE-2026-52922, CVE-2026-52925, CVE-2026-52926, CVE-2026-52931, CVE-2026-52954, CVE-2026-52955,     CVE-2026-52957, CVE-2026-52958, CVE-2026-52962, CVE-2026-52963, CVE-2026-52969, CVE-2026-52970,     CVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52992, CVE-2026-52993,     CVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003,     CVE-2026-53004, CVE-2026-53006, CVE-2026-53011, CVE-2026-53012, CVE-2026-53016, CVE-2026-53021,     CVE-2026-53022, CVE-2026-53023, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041,     CVE-2026-53043, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,     CVE-2026-53050, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53064,     CVE-2026-53065, CVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,     CVE-2026-53074, CVE-2026-53075, CVE-2026-53077, CVE-2026-53082, CVE-2026-53088, CVE-2026-53093,     CVE-2026-53096, CVE-2026-53112, CVE-2026-53128, CVE-2026-53130, CVE-2026-53287, CVE-2026-53291,     CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53304, CVE-2026-53306, CVE-2026-53309,     CVE-2026-53320, CVE-2026-53369, CVE-2026-53379, CVE-2026-63860, CVE-2026-63865, CVE-2026-64018,     CVE-2026-64032, CVE-2026-64033, CVE-2026-64034, CVE-2026-64039, CVE-2026-64046, CVE-2026-64047,     CVE-2026-64055, CVE-2026-64056, CVE-2026-64083, CVE-2026-64084, CVE-2026-64085, CVE-2026-64086,     CVE-2026-64087, CVE-2026-64088, CVE-2026-64089, CVE-2026-64096, CVE-2026-64102, CVE-2026-64103,     CVE-2026-64113, CVE-2026-64114, CVE-2026-64115, CVE-2026-64125, CVE-2026-64133, CVE-2026-64135,     CVE-2026-64153, CVE-2026-64155, CVE-2026-64164, CVE-2026-64165, CVE-2026-64166, CVE-2026-64168,     CVE-2026-64173, CVE-2026-64174, CVE-2026-64177, CVE-2026-64178, CVE-2026-64179, CVE-2026-64185,     CVE-2026-64218, CVE-2026-64219, CVE-2026-64220, CVE-2026-64221, CVE-2026-64587)

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

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

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

    This update for xen fixes the following issues

    - CVE-2025-54505: Floating Point Divider State Sampling on AMD CPUs AMD-SN-7053 (bsc#1262428).
    - CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264066).
    - CVE-2026-23557: Xenstored DoS via XS_RESET_WATCHES command (bsc#1262178).
    - CVE-2026-23558: grant table v2 race in status page mapping (bsc#1262180).

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 Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6424 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6424-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     August 09, 2026                       https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : xen     CVE ID         : CVE-2025-10263 CVE-2025-54505 CVE-2025-54518 CVE-2026-23554                      CVE-2026-23555 CVE-2026-23556 CVE-2026-23557 CVE-2026-23558                      CVE-2026-42487 CVE-2026-42488 CVE-2026-42489 CVE-2026-42490                      CVE-2026-42493 CVE-2026-42494 CVE-2026-42495 CVE-2026-62423                      CVE-2026-62424 CVE-2026-62425 CVE-2026-62426 CVE-2026-62427                      CVE-2026-62428 CVE-2026-62429 CVE-2026-62430 CVE-2026-62431                      CVE-2026-62432 CVE-2026-62433 CVE-2026-62434 CVE-2026-62435                      CVE-2026-62436

    Multiple vulnerabilities have been discovered in the Xen hypervisor,     which could result in privilege escalation, information disclosure or     denial of service.

    For the stable distribution (trixie), these problems have been fixed in     version 4.20.3+127-gc42374a105-0+deb13u1.

    We recommend that you upgrade your xen packages.

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

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

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.

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

    - -------------------------------------------------------------------------     Debian LTS Advisory DLA-4818-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                  Hans van Kranenburg     October 04, 2026                              https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    Package        : xen     Version        : 4.17.7-0+deb12u1     CVE ID         : CVE-2025-10263 CVE-2025-54505 CVE-2025-54518 CVE-2025-58150                      CVE-2026-23553 CVE-2026-23554 CVE-2026-23556 CVE-2026-23557                      CVE-2026-23558 CVE-2026-42487 CVE-2026-42488 CVE-2026-42489                      CVE-2026-42490 CVE-2026-42493 CVE-2026-42494 CVE-2026-42495                      CVE-2026-62423 CVE-2026-62424 CVE-2026-62425 CVE-2026-62426                      CVE-2026-62427 CVE-2026-62428 CVE-2026-62429 CVE-2026-62430                      CVE-2026-62431 CVE-2026-62432 CVE-2026-62433 CVE-2026-62434                      CVE-2026-62435 CVE-2026-62436

    Multiple vulnerabilities have been discovered in the Xen hypervisor,     which could result in privilege escalation, information disclosure or     denial of service.

    For Debian 12 bookworm, these problems have been fixed in version     4.17.7-0+deb12u1.

    We recommend that you upgrade your xen packages.

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

    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

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.

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

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

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

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.

  - A transient execution vulnerability within AMD CPUs may allow a local user-privileged attacker to leak     data via the floating point divisor unit, potentially resulting in loss of confidentiality.
    (CVE-2025-54505)

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

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

    It was discovered that some AMD processors did not properly clear data in the floating point divider unit     during speculative execution. A local attacker could use this to expose sensitive information.
    (CVE-2025-54505)

    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;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Rados block device (RBD) driver;

    - Compressed RAM block device driver;

    - Character device driver;

    - TPM device driver;

    - Hardware crypto device drivers;

    - EDAC drivers;

    - GPU drivers;

    - Greybus drivers;

    - HID subsystem;

    - Microsoft Hyper-V drivers;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - IBM Advanced System Management driver;

    - MTD block device drivers;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - NTB driver;

    - NVME drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - Remote Processor subsystem;

    - SCSI subsystem;

    - SPI subsystem;

    - Realtek RTL8723BS SDIO drivers;

    - SM750 framebuffer staging driver;

    - Thermal drivers;

    - USB Gadget drivers;

    - USB over IP driver;

    - VFIO drivers;

    - Framebuffer layer;

    - 9P distributed file system;

    - AFS file system;

    - Ceph distributed file system;

    - File systems infrastructure;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - Journaling layer for block devices (JBD2);

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - SMB network file system;

    - UDF file system;

    - XFS file system;

    - Codetag library;

    - Memory management;

    - Memory Management;

    - KVM subsystem;

    - Tracing infrastructure;

    - User-space API (UAPI);

    - io_uring subsystem;

    - Locking primitives;

    - Timer subsystem;

    - Scatterlist API;

    - Heterogeneous memory management;

    - KASAN memory debugging framework;

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAIF protocol;

    - CAN network layer;

    - Ceph Core library;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Packet sockets;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - RxRPC session sockets;

    - SMC sockets;

    - Stream parser;

    - Landlock security;

    - SELinux security module;

    - ALSA framework;

    - Generic PCM loopback sound driver;

    - FireWire sound drivers;

    - Creative Sound Blaster X-Fi driver;

    - QCOM ASoC drivers;

    - USB sound devices;

    - Objtool; (CVE-2026-31532, CVE-2026-31574, CVE-2026-31575, CVE-2026-31576, CVE-2026-31577,     CVE-2026-31578, CVE-2026-31579, CVE-2026-31580, CVE-2026-31581, CVE-2026-31582, CVE-2026-31583,     CVE-2026-31584, CVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31589,     CVE-2026-31590, CVE-2026-31591, CVE-2026-31592, CVE-2026-31593, CVE-2026-31594, CVE-2026-31595,     CVE-2026-31596, CVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31600, CVE-2026-31601,     CVE-2026-31602, CVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,     CVE-2026-31608, CVE-2026-31609, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,     CVE-2026-31614, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,     CVE-2026-31620, CVE-2026-31621, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,     CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31686, CVE-2026-31694,     CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,     CVE-2026-31702, CVE-2026-31703, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,     CVE-2026-31708, CVE-2026-31709, CVE-2026-31710, CVE-2026-31711, CVE-2026-31712, CVE-2026-31713,     CVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31717, CVE-2026-31718, CVE-2026-31719,     CVE-2026-43058, CVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43348, CVE-2026-43349,     CVE-2026-43350, CVE-2026-43491, CVE-2026-43493, CVE-2026-43499, CVE-2026-43501, CVE-2026-45986,     CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994,     CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002,     CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008,     CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014,     CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021,     CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027,     CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033,     CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039,     CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045,     CVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052,     CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059,     CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065,     CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071,     CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077,     CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083,     CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089,     CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095,     CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101,     CVE-2026-46102, CVE-2026-46103, CVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46137,     CVE-2026-46155, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46276,     CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282,     CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288,     CVE-2026-46289, CVE-2026-46316, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906,     CVE-2026-52907, CVE-2026-52933)

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

  - A vulnerability classified as problematic has been found in Linux Kernel. Affected is the function     j1939_session_destroy of the file net/can/j1939/transport.c. The manipulation leads to memory leak. It is     recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211932.
    (CVE-2022-3633)

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

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

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

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
359640	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/21	low
340682	Ubuntu 20.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8668-1)	Nessus	Ubuntu Local Security Checks	2026/8/26	2026/9/24	high
317658	SUSE SLES15 Security Update : xen (SUSE-SU-2026:2102-1)	Nessus	SuSE Local Security Checks	2026/5/29	2026/5/29	high
333555	Debian dsa-6424 : libxen-dev - security update	Nessus	Debian Local Security Checks	2026/8/9	2026/8/9	critical
362913	Debian dla-4818 : libxen-dev - security update	Nessus	Debian Local Security Checks	2026/10/4	2026/10/4	critical
340680	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (Raspberry Pi) vulnerabilities (USN-8665-1)	Nessus	Ubuntu Local Security Checks	2026/8/26	2026/8/27	high
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/22	low
307400	Linux Distros Unpatched Vulnerability : CVE-2025-54505	Nessus	Misc.	2026/4/17	2026/11/6	low
325421	Ubuntu 26.04 LTS : Linux kernel (NVIDIA) vulnerabilities (USN-8507-1)	Nessus	Ubuntu Local Security Checks	2026/7/7	2026/7/30	low
359694	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1782155469)	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/21	low

检测

插件搜索

low

high

high

critical

critical

high

low

low

low

low