In the Linux kernel, the following vulnerability has been resolved: ppp_synctty: ensure a writeable skb header ppp_sync_txmunge() checks headroom before prepending the address and control bytes, but does not ensure that the skb header is writable. A received skb can reach this function through PPP channel bridging without passing through ppp_start_xmit(), which calls skb_cow_head(). For example, a PPPoE frame may share its buffer with a clone queued to an AF_PACKET socket. If it is bridged to a synchronous tty channel, the address/control bytes can overwrite data still visible to that socket. Use skb_cow_head() to ensure both sufficient headroom and a writable header.

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

  - In the Linux kernel, the following vulnerability has been resolved: rv: Use strings in da monitors     tracepoints Using DA monitors tracepoints with KASAN enabled triggers the following warning: BUG: KASAN:
    global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0 Read of size 32 at addr     ffffffffaada8980 by task ... Call Trace: <TASK> [...] do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0     ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10 ? trace_event_sncid+0x83/0x200     trace_event_sncid+0x163/0x200 [...] The buggy address belongs to the variable: automaton_snep+0x4e0/0x5e0     This is caused by the tracepoints reading 32 bytes __array instead of __string from the automata     definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g.
    the next automaton's data in this case). The error is harmless as, while printing the string, we stop at     the null terminator, but it should still be fixed. Use the __string facilities while defining the     tracepoints to avoid reading out of bound memory. (CVE-2025-38636)

  - In the Linux kernel, the following vulnerability has been resolved: iommufd: Prevent ALIGN() overflow When     allocating IOVA the candidate range gets aligned to the target alignment. If the range is close to     ULONG_MAX then the ALIGN() can wrap resulting in a corrupted iova. Open code the ALIGN() using     get_add_overflow() to prevent this. This simplifies the checks as we don't need to check for length     earlier either. Consolidate the two copies of this code under a single helper. This bug would allow     userspace to create a mapping that overlaps with some other mapping or a reserved range. (CVE-2025-38688)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix NULL dereference in     ath11k_qmi_m3_load() If ab->fw.m3_data points to data, then fw pointer remains null. Further, if m3_mem is     not allocated, then fw is dereferenced to be passed to ath11k_err function. Replace fw->size by m3_len.
    Found by Linux Verification Center (linuxtesting.org) with SVACE. (CVE-2025-39991)

  - In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-     bounds writes in handle_auth_session_key() The len field originates from untrusted network packets.
    Boundary checks have been added to prevent potential out-of-bounds writes when decrypting the connection     secret or processing service tickets. [ idryomov: changelog ] (CVE-2025-68284)

  - In the Linux kernel, the following vulnerability has been resolved: tipc: fix bc_ackers underflow on     duplicate GRP_ACK_MSG The GRP_ACK_MSG handler in tipc_group_proto_rcv() currently decrements bc_ackers on     every inbound group ACK, even when the same member has already acknowledged the current broadcast round.
    Because bc_ackers is a u16, a duplicate ACK received after the last legitimate ACK wraps the counter to     65535. Once wrapped, tipc_group_bc_cong() keeps reporting congestion and later group broadcasts on the     affected socket stay blocked until the group is recreated. Fix this by ignoring duplicate or stale ACKs     before touching bc_acked or bc_ackers. This makes repeated GRP_ACK_MSG handling idempotent and prevents     the underflow path. (CVE-2026-31662)

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:1793866396 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: rv: Use strings in da monitors     tracepoints Using DA monitors tracepoints with KASAN enabled triggers the following warning: BUG: KASAN:
    global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0 Read of size 32 at addr     ffffffffaada8980 by task ... Call Trace: <TASK> [...] do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0     ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10 ? trace_event_sncid+0x83/0x200     trace_event_sncid+0x163/0x200 [...] The buggy address belongs to the variable: automaton_snep+0x4e0/0x5e0     This is caused by the tracepoints reading 32 bytes __array instead of __string from the automata     definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g.
    the next automaton's data in this case). The error is harmless as, while printing the string, we stop at     the null terminator, but it should still be fixed. Use the __string facilities while defining the     tracepoints to avoid reading out of bound memory. (CVE-2025-38636)

  - In the Linux kernel, the following vulnerability has been resolved: iommufd: Prevent ALIGN() overflow When     allocating IOVA the candidate range gets aligned to the target alignment. If the range is close to     ULONG_MAX then the ALIGN() can wrap resulting in a corrupted iova. Open code the ALIGN() using     get_add_overflow() to prevent this. This simplifies the checks as we don't need to check for length     earlier either. Consolidate the two copies of this code under a single helper. This bug would allow     userspace to create a mapping that overlaps with some other mapping or a reserved range. (CVE-2025-38688)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix NULL dereference in     ath11k_qmi_m3_load() If ab->fw.m3_data points to data, then fw pointer remains null. Further, if m3_mem is     not allocated, then fw is dereferenced to be passed to ath11k_err function. Replace fw->size by m3_len.
    Found by Linux Verification Center (linuxtesting.org) with SVACE. (CVE-2025-39991)

  - In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-     bounds writes in handle_auth_session_key() The len field originates from untrusted network packets.
    Boundary checks have been added to prevent potential out-of-bounds writes when decrypting the connection     secret or processing service tickets. [ idryomov: changelog ] (CVE-2025-68284)

  - In the Linux kernel, the following vulnerability has been resolved: tipc: fix bc_ackers underflow on     duplicate GRP_ACK_MSG The GRP_ACK_MSG handler in tipc_group_proto_rcv() currently decrements bc_ackers on     every inbound group ACK, even when the same member has already acknowledged the current broadcast round.
    Because bc_ackers is a u16, a duplicate ACK received after the last legitimate ACK wraps the counter to     65535. Once wrapped, tipc_group_bc_cong() keeps reporting congestion and later group broadcasts on the     affected socket stay blocked until the group is recreated. Fix this by ignoring duplicate or stale ACKs     before touching bc_acked or bc_ackers. This makes repeated GRP_ACK_MSG handling idempotent and prevents     the underflow path. (CVE-2026-31662)

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

    Duoming Zhou discovered race conditions in the AX.25 amateur radio protocol implementation in the Linux     kernel, leading to use-after-free vulnerabilities. A local attacker could possibly use this to cause a     denial of service (system crash). (CVE-2022-1205)

    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:

    - USB Gadget drivers;

    - ARM32 architecture;

    - ARM64 architecture;

    - OpenRISC architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Speakup Console Speech Driver;

    - ACPI drivers;

    - Serial ATA and Parallel ATA drivers;

    - Auxiliary display drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - Clocksource drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - EDAC drivers;

    - Google firmware drivers;

    - FPGA Framework;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - HSI subsystem;

    - Hardware monitoring drivers;

    - CoreSight HW tracing drivers;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - Media drivers;

    - Analog Devices digital potentiometer driver;

    - Broadcom VK accelerator driver;

    - Fastrpc Driver;

    - MMC subsystem;

    - MTD block device drivers;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - MediaTek network drivers;

    - Near Field Communication (NFC) drivers;

    - NTB driver;

    - NVDIMM (Non-Volatile Memory Device) drivers;

    - NVME drivers;

    - Device tree and open firmware driver;

    - PA-RISC drivers;

    - PCI subsystem;

    - PHY drivers;

    - Pin controllers subsystem;

    - Chrome hardware platform drivers;

    - Mellanox platform drivers;

    - Microsoft Surface platform drivers;

    - x86 platform drivers;

    - Power supply drivers;

    - RapidIO drivers;

    - Voltage and Current Regulator drivers;

    - Remote Processor subsystem;

    - RPMSG subsystem;

    - Real Time Clock drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - SPI subsystem;

    - small TFT LCD display modules;

    - Greybus lights staging drivers;

    - Media staging drivers;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - Thermal drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - Userspace I/O drivers;

    - USB DSL drivers;

    - Cypress C67X00 USB driver;

    - USB core drivers;

    - USB Host Controller drivers;

    - Mustek MDC800 USB digital camera driver;

    - USB Serial drivers;

    - USB Mass Storage drivers;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - vDPA drivers;

    - VFIO drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - W1 Dallas's 1-wire bus driver;

    - Watchdog drivers;

    - File systems infrastructure;

    - BFS file system;

    - BTRFS file system;

    - Ceph distributed file system;

    - eCrypt file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - FUSE (File system in Userspace);

    - HFS+ file system;

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

    - OCFS2 file system;

    - OrangeFS file system;

    - SMB network file system;

    - SquashFS file system;

    - UBI file system;

    - UDF file system;

    - XFS file system;

    - BPF subsystem;

    - IPv4 networking;

    - Internal shared memory driver;

    - Networking core;

    - Scheduler infrastructure;

    - Sun RPC protocol;

    - Virtio network driver;

    - Amateur Radio drivers;

    - IP tunnels definitions;

    - Network traffic control;

    - SCTP protocol;

    - TCP network protocol;

    - eXpress Data Path;

    - XFRM subsystem;

    - User-space API (UAPI);

    - io_uring subsystem;

    - Audit subsystem;

    - Perf events;

    - KCOV code coverage framework;

    - Locking primitives;

    - RCU subsystem;

    - Signal handling mechanism;

    - Timer subsystem;

    - Tracing infrastructure;

    - Kernel build system;

    - Heterogeneous memory management;

    - UCS-2 string library;

    - Memory management;

    - Appletalk network protocol;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAN network layer;

    - Ceph Core library;

    - Distributed Switch Architecture;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IPv6 networking;

    - IUCV driver;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - MAC80211 subsystem;

    - MultiProtocol Label Switching driver;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Packet sockets;

    - Phonet protocol;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - SMC sockets;

    - TIPC protocol;

    - VMware vSockets driver;

    - Wireless networking;

    - AppArmor security module;

    - Integrity Measurement Architecture(IMA) framework;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - ALSA framework;

    - Generic PCM loopback sound driver;

    - Generic sound devices;

    - ESS ES18xx ALSA driver;

    - Digigram PCXHR ALSA driver;

    - Cirrus Logic audio codecs;

    - QCOM ASoC drivers;

    - Realtek audio codecs;

    - WCD audio codecs;

    - Amlogic Meson SoC drivers;

    - Rockchip ASoC drivers;

    - SoC audio core drivers;

    - Spreadtrum ASoC drivers;

    - STI ASoC drivers;

    - Xilinx ASoC drivers;

    - USB sound devices;

    - Perf tools; (CVE-2022-49234, CVE-2022-49359, CVE-2022-49562, CVE-2022-49651, CVE-2022-49858,     CVE-2022-50071, CVE-2022-50303, CVE-2022-50406, CVE-2023-52676, CVE-2023-53231, CVE-2023-53320,     CVE-2023-53707, CVE-2024-41062, CVE-2024-46754, CVE-2024-49568, CVE-2024-50017, CVE-2024-53187,     CVE-2024-53210, CVE-2024-53220, CVE-2024-54683, CVE-2024-57945, CVE-2024-57982, CVE-2024-57999,     CVE-2024-58094, CVE-2024-58095, CVE-2024-58096, CVE-2025-21649, CVE-2025-21651, CVE-2025-21759,     CVE-2025-21801, CVE-2025-21812, CVE-2025-21947, CVE-2025-22039, CVE-2025-22057, CVE-2025-22083,     CVE-2025-22103, CVE-2025-37861, CVE-2025-37920, CVE-2025-38069, CVE-2025-38097, CVE-2025-38239,     CVE-2025-38259, CVE-2025-38349, CVE-2025-38361, CVE-2025-38615, CVE-2025-38643, CVE-2025-39726,     CVE-2025-39779, CVE-2025-39810, CVE-2025-39925, CVE-2025-40102, CVE-2025-40123, CVE-2025-68190,     CVE-2025-68794, CVE-2026-23191, CVE-2026-31420, CVE-2026-43088, CVE-2026-43437, CVE-2026-43456,     CVE-2026-46113, CVE-2026-46158, CVE-2026-46170, CVE-2026-46242, CVE-2026-52944, CVE-2026-52988,     CVE-2026-53078, CVE-2026-53089, CVE-2026-64561, CVE-2026-64581, CVE-2026-68236, CVE-2026-68399,     CVE-2026-68476, CVE-2026-72323, CVE-2026-74268, CVE-2026-74378, CVE-2026-74496, CVE-2026-74582,     CVE-2026-74626, CVE-2026-74632, CVE-2026-74637, CVE-2026-74647, CVE-2026-74662, CVE-2026-74663,     CVE-2026-74666, CVE-2026-74668, CVE-2026-74743, CVE-2026-80536, CVE-2026-80547, CVE-2026-80548,     CVE-2026-80552, CVE-2026-80553, CVE-2026-80555, CVE-2026-80557, CVE-2026-80562, CVE-2026-80583,     CVE-2026-80587, CVE-2026-80590, CVE-2026-80671, CVE-2026-80689, CVE-2026-80737, CVE-2026-80765,     CVE-2026-80766, CVE-2026-80767, CVE-2026-80768, CVE-2026-80781, CVE-2026-80782, CVE-2026-80783,     CVE-2026-80788, CVE-2026-80789, CVE-2026-80790, CVE-2026-80792, CVE-2026-80793, CVE-2026-80794,     CVE-2026-80795, CVE-2026-80796, CVE-2026-80797, CVE-2026-80798, CVE-2026-80799, CVE-2026-80800,     CVE-2026-80801, CVE-2026-80802, CVE-2026-80803, CVE-2026-80805, CVE-2026-80806, CVE-2026-80807,     CVE-2026-80808, CVE-2026-80809, CVE-2026-80812, CVE-2026-80814, CVE-2026-80819, CVE-2026-80823,     CVE-2026-80824, CVE-2026-80826, CVE-2026-80827, CVE-2026-80828, CVE-2026-80829, CVE-2026-80830,     CVE-2026-80831, CVE-2026-80832, CVE-2026-80833, CVE-2026-80834, CVE-2026-80840, CVE-2026-80842,     CVE-2026-80843, CVE-2026-80844, CVE-2026-80846, CVE-2026-80848, CVE-2026-80854, CVE-2026-80855,     CVE-2026-80856, CVE-2026-80863, CVE-2026-80888, CVE-2026-80912, CVE-2026-80916, CVE-2026-80917,     CVE-2026-80918, CVE-2026-80921, CVE-2026-80923, CVE-2026-80928, CVE-2026-80930, CVE-2026-80931,     CVE-2026-80932, CVE-2026-80938, CVE-2026-80941, CVE-2026-80944, CVE-2026-80949, CVE-2026-80951,     CVE-2026-80952, CVE-2026-80963, CVE-2026-80964, CVE-2026-80965, CVE-2026-80966, CVE-2026-80967,     CVE-2026-80968, CVE-2026-80969, CVE-2026-80971, CVE-2026-80972, CVE-2026-80973, CVE-2026-80976,     CVE-2026-80977, CVE-2026-80978, CVE-2026-80983, CVE-2026-80987, CVE-2026-80988, CVE-2026-80994,     CVE-2026-81000, CVE-2026-81001, CVE-2026-81002, CVE-2026-81003, CVE-2026-81005, CVE-2026-81007,     CVE-2026-81008, CVE-2026-81017, CVE-2026-89440, CVE-2026-89444, CVE-2026-89456, CVE-2026-89457,     CVE-2026-89458, CVE-2026-89461, CVE-2026-89463, CVE-2026-89464, CVE-2026-89469, CVE-2026-89470,     CVE-2026-89471, CVE-2026-89474, CVE-2026-89475, CVE-2026-89476, CVE-2026-89477, CVE-2026-89478,     CVE-2026-89479, CVE-2026-89480, CVE-2026-89482, CVE-2026-89483, CVE-2026-89485, CVE-2026-89487,     CVE-2026-89488, CVE-2026-89489, CVE-2026-89490, CVE-2026-89491, CVE-2026-89493, CVE-2026-89494,     CVE-2026-89495, CVE-2026-89496, CVE-2026-89497, CVE-2026-89498, CVE-2026-89504, CVE-2026-89508,     CVE-2026-89510, CVE-2026-89511, CVE-2026-89512, CVE-2026-89515, CVE-2026-89524, CVE-2026-89525,     CVE-2026-89532, CVE-2026-89533, CVE-2026-89538, CVE-2026-89540, CVE-2026-89541, CVE-2026-89542,     CVE-2026-89548, CVE-2026-89549, CVE-2026-89551, CVE-2026-89554, CVE-2026-89555, CVE-2026-89557,     CVE-2026-89559, CVE-2026-89560, CVE-2026-89562, CVE-2026-89563, CVE-2026-89569, CVE-2026-89573,     CVE-2026-89575, CVE-2026-89576, CVE-2026-89582, CVE-2026-89585, CVE-2026-89586, CVE-2026-89594,     CVE-2026-89595, CVE-2026-89596, CVE-2026-89597, CVE-2026-89599, CVE-2026-89605, CVE-2026-89606,     CVE-2026-89607, CVE-2026-89608, CVE-2026-89609, CVE-2026-89615, CVE-2026-89616, CVE-2026-89617,     CVE-2026-89621, CVE-2026-89626, CVE-2026-89627, CVE-2026-89628, CVE-2026-89643, CVE-2026-89649,     CVE-2026-89650, CVE-2026-89653, CVE-2026-89655, CVE-2026-89656, CVE-2026-89662, CVE-2026-89663,     CVE-2026-89665, CVE-2026-89669, CVE-2026-89673, CVE-2026-89674, CVE-2026-89684, CVE-2026-89694,     CVE-2026-89696, CVE-2026-89697, CVE-2026-89699, CVE-2026-89704, CVE-2026-89706, CVE-2026-89710,     CVE-2026-89711, CVE-2026-89712, CVE-2026-89720, CVE-2026-89723, CVE-2026-89724, CVE-2026-89725,     CVE-2026-89726, CVE-2026-89729, CVE-2026-89730, CVE-2026-89732, CVE-2026-89733, CVE-2026-89736,     CVE-2026-89741, CVE-2026-89742, CVE-2026-89749, CVE-2026-89752, CVE-2026-89753, CVE-2026-89765,     CVE-2026-89777, CVE-2026-89778, CVE-2026-89779, CVE-2026-89780, CVE-2026-89781, CVE-2026-89782,     CVE-2026-89783, CVE-2026-89784, CVE-2026-89785, CVE-2026-89786, CVE-2026-89787, CVE-2026-89789,     CVE-2026-89792, CVE-2026-89796, CVE-2026-89816, CVE-2026-89817, CVE-2026-89821, CVE-2026-89823,     CVE-2026-89843, CVE-2026-89845, CVE-2026-89846, CVE-2026-89847, CVE-2026-89849, CVE-2026-89850,     CVE-2026-89851, CVE-2026-89852, CVE-2026-89853, CVE-2026-89854, CVE-2026-89855, CVE-2026-89856,     CVE-2026-89858, CVE-2026-89861, CVE-2026-89863, CVE-2026-89864, CVE-2026-89865, CVE-2026-89871,     CVE-2026-89872, CVE-2026-89876, CVE-2026-89878, CVE-2026-89879, CVE-2026-89880, CVE-2026-89881,     CVE-2026-89883, CVE-2026-89887, CVE-2026-89888, CVE-2026-89890, CVE-2026-89891, CVE-2026-89892,     CVE-2026-89893, CVE-2026-89894, CVE-2026-89895, CVE-2026-89896, CVE-2026-89897, CVE-2026-89901,     CVE-2026-89923, CVE-2026-89924, CVE-2026-89925, CVE-2026-89926, CVE-2026-89927, CVE-2026-89930,     CVE-2026-89932, CVE-2026-89936, CVE-2026-89937, CVE-2026-89939, CVE-2026-89945, CVE-2026-89946,     CVE-2026-89947, CVE-2026-89948, CVE-2026-89949, CVE-2026-89951, CVE-2026-89952, CVE-2026-89953,     CVE-2026-89954, CVE-2026-89964, CVE-2026-89965, CVE-2026-89968, CVE-2026-89969, CVE-2026-89973,     CVE-2026-89979, CVE-2026-89982, CVE-2026-89983, CVE-2026-89984, CVE-2026-89989, CVE-2026-89993,     CVE-2026-89997, CVE-2026-89999, CVE-2026-90000, CVE-2026-90007, CVE-2026-90011, CVE-2026-90015,     CVE-2026-90017, CVE-2026-90018, CVE-2026-90019, CVE-2026-90020, CVE-2026-90025, CVE-2026-90031,     CVE-2026-90032, CVE-2026-90033, CVE-2026-90034, CVE-2026-90049, CVE-2026-90053, CVE-2026-90054,     CVE-2026-90055, CVE-2026-90056, CVE-2026-90058, CVE-2026-90062, CVE-2026-90063, CVE-2026-90067,     CVE-2026-90068, CVE-2026-90070, CVE-2026-90071, CVE-2026-90072, CVE-2026-90073, CVE-2026-90074,     CVE-2026-90075, CVE-2026-90078, CVE-2026-90081, CVE-2026-90088, CVE-2026-90102, CVE-2026-90103,     CVE-2026-90107, CVE-2026-90114, CVE-2026-90126, CVE-2026-90128, CVE-2026-90140, CVE-2026-90141,     CVE-2026-90143, CVE-2026-90151, CVE-2026-90157, CVE-2026-90160, CVE-2026-90198, CVE-2026-90202,     CVE-2026-90203, CVE-2026-90209, CVE-2026-90214, CVE-2026-90216, CVE-2026-90218, CVE-2026-90219,     CVE-2026-90221, CVE-2026-90222, CVE-2026-90223, CVE-2026-90224, CVE-2026-90225, CVE-2026-90226,     CVE-2026-90228, CVE-2026-90245, CVE-2026-90248, CVE-2026-90249, CVE-2026-90251, CVE-2026-90257,     CVE-2026-90274, CVE-2026-90281, CVE-2026-90283, CVE-2026-90284, CVE-2026-90285, CVE-2026-90286,     CVE-2026-90290, CVE-2026-90292, CVE-2026-90293, CVE-2026-90294, CVE-2026-90295, CVE-2026-90296,     CVE-2026-90297, CVE-2026-90298, CVE-2026-90302, CVE-2026-90303, CVE-2026-90307, CVE-2026-90314,     CVE-2026-90316, CVE-2026-90318, CVE-2026-90319, CVE-2026-90327, CVE-2026-90329, CVE-2026-90334,     CVE-2026-90341, CVE-2026-90348, CVE-2026-90360, CVE-2026-90361, CVE-2026-90362, CVE-2026-90372,     CVE-2026-90378, CVE-2026-90382, CVE-2026-90386, CVE-2026-90388, CVE-2026-90391, CVE-2026-90393,     CVE-2026-90394, CVE-2026-90395, CVE-2026-90403, CVE-2026-90411, CVE-2026-90413, CVE-2026-90414,     CVE-2026-90415, CVE-2026-90416, CVE-2026-90419, CVE-2026-90420, CVE-2026-90431, CVE-2026-90434,     CVE-2026-90435, CVE-2026-92476, CVE-2026-92494, CVE-2026-92496, CVE-2026-92498, CVE-2026-92501,     CVE-2026-92504, CVE-2026-92508, CVE-2026-92521, CVE-2026-92522, CVE-2026-92524, CVE-2026-93037,     CVE-2026-93039, CVE-2026-93040, CVE-2026-93041, CVE-2026-93046, CVE-2026-93048, CVE-2026-93049,     CVE-2026-93051, CVE-2026-93052, CVE-2026-93053, CVE-2026-93054, CVE-2026-93055, CVE-2026-93056,     CVE-2026-93061, CVE-2026-93067, CVE-2026-93095, CVE-2026-93098, CVE-2026-93102, CVE-2026-93103,     CVE-2026-93108, CVE-2026-93109, CVE-2026-93110, CVE-2026-93114, CVE-2026-93115, CVE-2026-93120,     CVE-2026-93130, CVE-2026-93131, CVE-2026-93138, CVE-2026-93140, CVE-2026-93141, CVE-2026-93145,     CVE-2026-93151, CVE-2026-93158, CVE-2026-93159, CVE-2026-93160, CVE-2026-93161, CVE-2026-93165,     CVE-2026-93167, CVE-2026-93170, CVE-2026-93177, CVE-2026-93178, CVE-2026-93183, CVE-2026-93185,     CVE-2026-93188, CVE-2026-93189, CVE-2026-93191, CVE-2026-93203, CVE-2026-93204, CVE-2026-93206,     CVE-2026-93213, CVE-2026-93214, CVE-2026-93219, CVE-2026-93222, CVE-2026-93226, CVE-2026-93234,     CVE-2026-93236, CVE-2026-93242, CVE-2026-93245, CVE-2026-93252, CVE-2026-93256, CVE-2026-93261,     CVE-2026-93262, CVE-2026-93264, CVE-2026-93268, CVE-2026-93271, CVE-2026-93274, CVE-2026-93280,     CVE-2026-93283, CVE-2026-93286, CVE-2026-93287, CVE-2026-93288, CVE-2026-93782, CVE-2026-93783,     CVE-2026-93784, CVE-2026-93785, CVE-2026-93789, CVE-2026-93795, CVE-2026-93797, CVE-2026-93798,     CVE-2026-93800, CVE-2026-93802, CVE-2026-93803, CVE-2026-93805, CVE-2026-93807, CVE-2026-93808,     CVE-2026-93811, CVE-2026-93812, CVE-2026-93813, CVE-2026-93815, CVE-2026-93816, CVE-2026-93819,     CVE-2026-93820, CVE-2026-93821, CVE-2026-93822, CVE-2026-93825, CVE-2026-93830, CVE-2026-97407,     CVE-2026-97408, CVE-2026-97411, CVE-2026-97413, CVE-2026-97416, CVE-2026-97417, CVE-2026-97418,     CVE-2026-97419, CVE-2026-97420, CVE-2026-97421, CVE-2026-97430, CVE-2026-97434, CVE-2026-97435,     CVE-2026-97436, CVE-2026-97437, CVE-2026-97438, CVE-2026-97439, CVE-2026-97440, CVE-2026-97441,     CVE-2026-97443, CVE-2026-97444, CVE-2026-97445, CVE-2026-97446, CVE-2026-97448, CVE-2026-97449,     CVE-2026-97450, CVE-2026-97451, CVE-2026-97452, CVE-2026-97453, CVE-2026-97454, CVE-2026-97455,     CVE-2026-97456, CVE-2026-97472, CVE-2026-97475, CVE-2026-97476, CVE-2026-97481, CVE-2026-97482,     CVE-2026-97483, CVE-2026-97484, CVE-2026-97485, CVE-2026-97486, CVE-2026-97487, CVE-2026-97488,     CVE-2026-97489, CVE-2026-97490, CVE-2026-97491, CVE-2026-97492, CVE-2026-97502, CVE-2026-97506,     CVE-2026-97507, CVE-2026-97508, CVE-2026-97510, CVE-2026-97523, CVE-2026-97524, CVE-2026-97568,     CVE-2026-97572, CVE-2026-97573, CVE-2026-97576, CVE-2026-97582, CVE-2026-97592, CVE-2026-97596,     CVE-2026-97598, CVE-2026-97601, CVE-2026-97604, CVE-2026-97608, CVE-2026-97611, CVE-2026-97612,     CVE-2026-97899, CVE-2026-97904, CVE-2026-97905, CVE-2026-97909, CVE-2026-97910, CVE-2026-97923,     CVE-2026-97926, CVE-2026-97927, CVE-2026-97930, CVE-2026-97931, CVE-2026-97940, CVE-2026-97948,     CVE-2026-97951, CVE-2026-97954, CVE-2026-97957, CVE-2026-97958, CVE-2026-97959, CVE-2026-97963,     CVE-2026-97964, CVE-2026-97969, CVE-2026-97970, CVE-2026-97981, CVE-2026-97982, CVE-2026-97991,     CVE-2026-97993, CVE-2026-97995, CVE-2026-97998, CVE-2026-98006, CVE-2026-98009, CVE-2026-98010,     CVE-2026-98011, CVE-2026-98012, CVE-2026-98013, CVE-2026-98014, CVE-2026-98015, CVE-2026-98016,     CVE-2026-98022, CVE-2026-98023, CVE-2026-98025, CVE-2026-98027, CVE-2026-98030, CVE-2026-98031,     CVE-2026-98063, CVE-2026-98064, CVE-2026-98066, CVE-2026-98068, CVE-2026-98069, CVE-2026-98070,     CVE-2026-98071, CVE-2026-98072, CVE-2026-98074, CVE-2026-98075, CVE-2026-98076, CVE-2026-98077,     CVE-2026-98078, CVE-2026-98080, CVE-2026-98088, CVE-2026-98090, CVE-2026-98091, CVE-2026-98094,     CVE-2026-98095, CVE-2026-98096, CVE-2026-98098, CVE-2026-98108, CVE-2026-98113, CVE-2026-98116,     CVE-2026-98121, CVE-2026-98123, CVE-2026-98130, CVE-2026-98154, CVE-2026-98157, CVE-2026-98158)

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 Oracle Linux 8 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-500574 advisory.

    - ipv4: validate checksum_start before completing checksum (Michael S. Tsirkin)  [Orabug: 40165811]     {CVE-2026-99999}
    - ipv4: free inet_opt and ireq_opt after an RCU grace period (Eric Dumazet)  [Orabug: 40165788]     {CVE-2026-98432}
    - exec: Cleanup POSIX timers right after de_thread() (Hyunwoo Kim)  [Orabug: 40120750]  {CVE-2026-98260}

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

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

An update of the linux package has been released.

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

  - In the Linux kernel, the following vulnerability has been resolved: vhost: fix hung thread due to     erroneous iotlb entries In vhost_iotlb_add_range_ctx(), range size can overflow to 0 when start is 0 and     last is ULONG_MAX. One instance where it can happen is when userspace sends an IOTLB message with     iova=size=uaddr=0 (vhost_process_iotlb_msg). So, an entry with size = 0, start = 0, last = ULONG_MAX ends     up in the iotlb. Next time a packet is sent, iotlb_access_ok() loops indefinitely due to that erroneous     entry. Call Trace: <TASK> iotlb_access_ok+0x21b/0x3e0 drivers/vhost/vhost.c:1340     vq_meta_prefetch+0xbc/0x280 drivers/vhost/vhost.c:1366 vhost_transport_do_send_pkt+0xe0/0xfd0     drivers/vhost/vsock.c:104 vhost_worker+0x23d/0x3d0 drivers/vhost/vhost.c:372 kthread+0x2e9/0x3a0     kernel/kthread.c:377 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 </TASK> Reported by syzbot at:
    https://syzkaller.appspot.com/bug?extid=0abd373e2e50d704db87 To fix this, do two things: 1. Return -EINVAL     in vhost_chr_write_iter() when userspace asks to map a range with size 0. 2. Fix     vhost_iotlb_add_range_ctx() to handle the range [0, ULONG_MAX] by splitting it into two entries.
    (CVE-2022-48862)

  - In the Linux kernel, the following vulnerability has been resolved: net: hns3: add vlan list lock to     protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in     vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free     error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Fix crash due to race     between amd_pmu_enable_all, perf NMI and throttling amd_pmu_enable_all() does: if (!test_bit(idx,     cpuc->active_mask)) continue; amd_pmu_enable_event(cpuc->events[idx]); A perf NMI of another event can     come between these two steps. Perf NMI handler internally disables and enables _all_ events, including the     one which nmi-intercepted amd_pmu_enable_all() was in process of enabling. If that unintentionally enabled     event has very low sampling period and causes immediate successive NMI, causing the event to be throttled,     cpuc->events[idx] and cpuc->active_mask gets cleared by x86_pmu_stop(). This will result in     amd_pmu_enable_event() getting called with event=NULL when amd_pmu_enable_all() resumes after handling the     NMIs. This causes a kernel crash: BUG: kernel NULL pointer dereference, address: 0000000000000198 #PF:
    supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page [...] Call Trace: <TASK>     amd_pmu_enable_all+0x68/0xb0 ctx_resched+0xd9/0x150 event_function+0xb8/0x130 ?     hrtimer_start_range_ns+0x141/0x4a0 ? perf_duration_warn+0x30/0x30 remote_function+0x4d/0x60
    __flush_smp_call_function_queue+0xc4/0x500 flush_smp_call_function_queue+0x11d/0x1b0 do_idle+0x18f/0x2d0     cpu_startup_entry+0x19/0x20 start_secondary+0x121/0x160 secondary_startup_64_no_verify+0xe5/0xeb </TASK>     amd_pmu_disable_all()/amd_pmu_enable_all() calls inside perf NMI handler were recently added as part of     BRS enablement but I'm not sure whether we really need them. We can just disable BRS in the beginning and     enable it back while returning from NMI. This will solve the issue by not enabling those events whose     active_masks are set but are not yet enabled in hw pmu. (CVE-2022-49781)

  - In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on     add_disk() failures When a gendisk is successfully initialized but add_disk() fails such as when a loop     device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and     then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but     doesn't get cleaned up in the latter. This is because, in non-error cases, the cleanup is performed by     del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of     them, can only be activated once the disk is fully registered and visible. That assumption is true for wbt     and iocost, but not so for iolatency as it gets initialized before add_disk() is called. It is desirable     to lazy-init rq_qos policies because they are optional features and add to hot path overhead once     initialized - each IO has to walk all the registered rq_qos policies. So, we want to switch iolatency to     lazy init too. However, that's a bigger change. As a fix for the immediate problem, let's just add an     extra call to rq_qos_exit() in blkcg_exit_disk(). This is safe because duplicate calls to rq_qos_exit()     become noop's. (CVE-2022-50550)

  - In the Linux kernel, the following vulnerability has been resolved: i40e: Do not allow untrusted VF to     remove administratively set MAC Currently when PF administratively sets VF's MAC address and the VF is put     down (VF tries to delete all MACs) then the MAC is removed from MAC filters and primary VF MAC is zeroed.
    Do not allow untrusted VF to remove primary MAC when it was set administratively by PF. Reproducer: 1)     Create VF 2) Set VF interface up 3) Administratively set the VF's MAC 4) Put VF interface down [root@host     ~]# echo 1 > /sys/class/net/enp2s0f0/device/sriov_numvfs [root@host ~]# ip link set enp2s0f0v0 up     [root@host ~]# ip link set enp2s0f0 vf 0 mac fe:6c:b5:da:c7:7d [root@host ~]# ip link show enp2s0f0 23:
    enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen     1000 link/ether 3c:ec:ef:b7:dd:04 brd ff:ff:ff:ff:ff:ff vf 0 link/ether fe:6c:b5:da:c7:7d brd     ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off [root@host ~]# ip link set enp2s0f0v0     down [root@host ~]# ip link show enp2s0f0 23: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc     mq state UP mode DEFAULT group default qlen 1000 link/ether 3c:ec:ef:b7:dd:04 brd ff:ff:ff:ff:ff:ff vf 0     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off     (CVE-2024-26830)

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.

  - ppp_synctty: ensure a writeable skb header ppp_sync_txmunge() checks headroom before prepending the     address and control bytes, but does not ensure that the skb header is writable. A received skb can reach     this function through PPP channel bridging without passing through ppp_start_xmit(), which calls     skb_cow_head(). For example, a PPPoE frame may share its buffer with a clone queued to an AF_PACKET     socket. If it is bridged to a synchronous tty channel, the address/control bytes can overwrite data still     visible to that socket. Use skb_cow_head() to ensure both sufficient headroom and a writable header.
    (CVE-2026-97964)

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

ID	Name	Product	Family	Type	Severity
376443	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel vulnerabilities (USN-8959-1)	Nessus	Ubuntu Local Security Checks	Local	high
376433	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793866396)	Nessus	Alma Linux Local Security Checks	Local	high
376432	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793866396)	Nessus	Rocky Linux Local Security Checks	Local	high
375805	Ubuntu 22.04 LTS : Linux kernel (Azure CVM) vulnerabilities (USN-8962-1)	Nessus	Ubuntu Local Security Checks	Local	high
375804	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-8961-1)	Nessus	Ubuntu Local Security Checks	Local	high
375468	Oracle Linux 8 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500574)	Nessus	Oracle Linux Local Security Checks	Local	high
375113	Photon OS 5.0: Linux PHSA-2026-5.0-91-1014	Nessus	PhotonOS Local Security Checks	Local	high
375014	Photon OS 5.0: Linux PHSA-2026-5.0-92-1014	Nessus	PhotonOS Local Security Checks	Local	high
373463	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-3336)	Nessus	Amazon Linux Local Security Checks	Local	medium
366919	Debian dla-4841 : ata-modules-6.1.0-53-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
365680	Oracle Linux 8 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500385)	Nessus	Oracle Linux Local Security Checks	Local	medium
365258	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-3192)	Nessus	Amazon Linux Local Security Checks	Local	high
365209	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-3193)	Nessus	Amazon Linux Local Security Checks	Local	medium
364688	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1791741836)	Nessus	Alma Linux Local Security Checks	Local	critical
364137	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500374)	Nessus	Oracle Linux Local Security Checks	Local	high
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
350512	Linux Distros Unpatched Vulnerability : CVE-2026-97964	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-97964

high

Tenable Plugins

high

high

high

high

high

high

high

high

medium

high

medium

high

medium

critical

high

high

high

high