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

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4404-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     December 12, 2025                             https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux     Version        : 5.10.247-1     CVE ID         : CVE-2023-53498 CVE-2024-47666 CVE-2024-50143 CVE-2024-57947                      CVE-2025-21861 CVE-2025-21887 CVE-2025-22058 CVE-2025-23143                      CVE-2025-38678 CVE-2025-39866 CVE-2025-39869 CVE-2025-39876                      CVE-2025-39883 CVE-2025-39885 CVE-2025-39907 CVE-2025-39911                      CVE-2025-39913 CVE-2025-39923 CVE-2025-39937 CVE-2025-39945                      CVE-2025-39949 CVE-2025-39951 CVE-2025-39953 CVE-2025-39955                      CVE-2025-39964 CVE-2025-39967 CVE-2025-39968 CVE-2025-39969                      CVE-2025-39970 CVE-2025-39971 CVE-2025-39972 CVE-2025-39973                      CVE-2025-39980 CVE-2025-39985 CVE-2025-39986 CVE-2025-39987                      CVE-2025-39993 CVE-2025-39994 CVE-2025-39995 CVE-2025-39996                      CVE-2025-39998 CVE-2025-40001 CVE-2025-40006 CVE-2025-40011                      CVE-2025-40018 CVE-2025-40019 CVE-2025-40020 CVE-2025-40021                      CVE-2025-40022 CVE-2025-40026 CVE-2025-40027 CVE-2025-40029                      CVE-2025-40030 CVE-2025-40035 CVE-2025-40042 CVE-2025-40044                      CVE-2025-40048 CVE-2025-40049 CVE-2025-40053 CVE-2025-40055                      CVE-2025-40070 CVE-2025-40078 CVE-2025-40081 CVE-2025-40083                      CVE-2025-40087 CVE-2025-40088 CVE-2025-40105 CVE-2025-40106                      CVE-2025-40109 CVE-2025-40111 CVE-2025-40115 CVE-2025-40116                      CVE-2025-40118 CVE-2025-40121 CVE-2025-40125 CVE-2025-40127                      CVE-2025-40134 CVE-2025-40140 CVE-2025-40153 CVE-2025-40154                      CVE-2025-40167 CVE-2025-40173 CVE-2025-40178 CVE-2025-40183                      CVE-2025-40186 CVE-2025-40187 CVE-2025-40188 CVE-2025-40190                      CVE-2025-40194 CVE-2025-40197 CVE-2025-40198 CVE-2025-40200                      CVE-2025-40204 CVE-2025-40205 CVE-2025-40211 CVE-2025-40219                      CVE-2025-40220 CVE-2025-40223 CVE-2025-40231 CVE-2025-40233                      CVE-2025-40240 CVE-2025-40243 CVE-2025-40244 CVE-2025-40248                      CVE-2025-40254 CVE-2025-40257 CVE-2025-40258 CVE-2025-40259                      CVE-2025-40261 CVE-2025-40262 CVE-2025-40263 CVE-2025-40264                      CVE-2025-40269 CVE-2025-40271 CVE-2025-40273 CVE-2025-40275                      CVE-2025-40277 CVE-2025-40278 CVE-2025-40280 CVE-2025-40281                      CVE-2025-40282 CVE-2025-40283 CVE-2025-40304 CVE-2025-40306                      CVE-2025-40308 CVE-2025-40309 CVE-2025-40312 CVE-2025-40315                      CVE-2025-40317 CVE-2025-40319 CVE-2025-40321 CVE-2025-40322                      CVE-2025-40324 CVE-2025-40331 CVE-2025-40342     Debian Bug     : 1107479 1114557

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

    For Debian 11 bullseye, these problems have been fixed in version     5.10.247-1.  This version additionally includes many more bug fixes     from stable updates 5.10.245-5.10.247.  The broken pktcdvd driver has     also been disabled.

    We recommend that you upgrade your linux packages.

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

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

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

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

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

    Qualys discovered that several vulnerabilities existed in the AppArmor Linux kernel Security Module (LSM).
    An unprivileged local attacker could use these issues to load, replace, and remove arbitrary AppArmor     profiles causing denial of service, exposure of sensitive information (kernel memory), local privilege     escalation, or possibly escape a container. (LP: #2143853, CVE-2026-23268, CVE-2026-23269)

    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:

    - Nios II architecture;

    - PowerPC architecture;

    - Sun Sparc architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - ATM drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Character device driver;

    - Hardware random number generator core;

    - TPM device driver;

    - Data acquisition framework and drivers;

    - Counter interface drivers;

    - CPU frequency scaling framework;

    - DMA engine subsystem;

    - Intel Stratix 10 firmware drivers;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - CoreSight HW tracing drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - Input Device (Tablet) drivers;

    - ISDN/mISDN subsystem;

    - Macintosh device drivers;

    - Multiple devices driver;

    - Media drivers;

    - MOST (Media Oriented Systems Transport) drivers;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - Texas Instruments network drivers;

    - Ethernet team driver;

    - MediaTek network drivers;

    - NVME drivers;

    - PA-RISC drivers;

    - PCI subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - Chrome hardware platform drivers;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PWM drivers;

    - Voltage and Current Regulator drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - Texas Instruments SoC drivers;

    - SPI subsystem;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - USB Mass Storage drivers;

    - USB Type-C Connector System Software Interface driver;

    - Backlight driver;

    - Framebuffer layer;

    - Watchdog drivers;

    - BFS file system;

    - BTRFS file system;

    - File systems infrastructure;

    - Ext4 file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - HFS file system;

    - HFS+ file system;

    - HugeTLB file system;

    - Journaling layer for block devices (JBD2);

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - OrangeFS file system;

    - Proc file system;

    - SMB network file system;

    - SquashFS file system;

    - UDF file system;

    - XFS file system;

    - BPF subsystem;

    - Ethernet bridge;

    - Memory management;

    - padata parallel execution mechanism;

    - IP tunnels definitions;

    - Network traffic control;

    - Network sockets;

    - XFRM subsystem;

    - io_uring subsystem;

    - Control group (cgroup);

    - Locking primitives;

    - Padata parallel execution mechanism;

    - PID allocator;

    - Scheduler infrastructure;

    - Shadow Call Stack mechanism;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Bluetooth subsystem;

    - CAIF protocol;

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - Ethtool driver;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NET/ROM layer;

    - NFC subsystem;

    - Open vSwitch;

    - RF switch subsystem;

    - Rose network layer;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - Rust bindings mechanism;

    - Integrity Measurement Architecture(IMA) framework;

    - Key management;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - Turtle Beach Wavefront ALSA driver;

    - Intel ASoC drivers;

    - STMicroelectronics SoC drivers;

    - USB sound devices; (CVE-2022-49465, CVE-2022-49635, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,     CVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968, CVE-2024-53114, CVE-2024-56538,     CVE-2024-58011, CVE-2025-21780, CVE-2025-21861, CVE-2025-22022, CVE-2025-22058, CVE-2025-22111,     CVE-2025-22121, CVE-2025-23143, CVE-2025-38022, CVE-2025-38129, CVE-2025-38236, CVE-2025-38248,     CVE-2025-38556, CVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876, CVE-2025-39880,     CVE-2025-39883, CVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913, CVE-2025-39923,     CVE-2025-39934, CVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949, CVE-2025-39951,     CVE-2025-39953, CVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969, CVE-2025-39970,     CVE-2025-39971, CVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985, CVE-2025-39986,     CVE-2025-39987, CVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996, CVE-2025-39998,     CVE-2025-40001, CVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021, CVE-2025-40026,     CVE-2025-40027, CVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040, CVE-2025-40042,     CVE-2025-40043, CVE-2025-40044, CVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,     CVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081, CVE-2025-40083,     CVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092, CVE-2025-40094, CVE-2025-40105,     CVE-2025-40106, CVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,     CVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121, CVE-2025-40124, CVE-2025-40125,     CVE-2025-40126, CVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,     CVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178, CVE-2025-40179, CVE-2025-40183,     CVE-2025-40187, CVE-2025-40188, CVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,     CVE-2025-40211, CVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223, CVE-2025-40231,     CVE-2025-40233, CVE-2025-40240, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,     CVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,     CVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40269, CVE-2025-40271,     CVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279,     CVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40304, CVE-2025-40306,     CVE-2025-40308, CVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,     CVE-2025-40317, CVE-2025-40319, CVE-2025-40321, CVE-2025-40322, CVE-2025-40324, CVE-2025-40331,     CVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40349, CVE-2025-40351,     CVE-2025-40360, CVE-2025-40363, CVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,     CVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200, CVE-2025-68204, CVE-2025-68217,     CVE-2025-68220, CVE-2025-68227, CVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,     CVE-2025-68245, CVE-2025-68249, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257, CVE-2025-68258,     CVE-2025-68261, CVE-2025-68264, CVE-2025-68266, CVE-2025-68282, CVE-2025-68284, CVE-2025-68285,     CVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290, CVE-2025-68295,     CVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68308, CVE-2025-68312, CVE-2025-68321,     CVE-2025-68325, CVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331, CVE-2025-68332,     CVE-2025-68335, CVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68344, CVE-2025-68346,     CVE-2025-68349, CVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,     CVE-2025-68372, CVE-2025-68724, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,     CVE-2025-68734, CVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759,     CVE-2025-68764, CVE-2025-68765, CVE-2025-68767, CVE-2025-68769, CVE-2025-68771, CVE-2025-68774,     CVE-2025-68776, CVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783, CVE-2025-68785,     CVE-2025-68787, CVE-2025-68788, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68799,     CVE-2025-68800, CVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808, CVE-2025-68813,     CVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820,     CVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069, CVE-2025-71075, CVE-2025-71077,     CVE-2025-71078, CVE-2025-71079, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,     CVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,     CVE-2025-71096, CVE-2025-71097, CVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,     CVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,     CVE-2025-71118, CVE-2025-71120, CVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,     CVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137, CVE-2025-71147, CVE-2025-71154,     CVE-2025-71180, CVE-2025-71182, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,     CVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-23019,     CVE-2026-23020, CVE-2026-23021, CVE-2026-23047)

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

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

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

    Qualys discovered that several vulnerabilities existed in the AppArmor Linux kernel Security Module (LSM).
    An unprivileged local attacker could use these issues to load, replace, and remove arbitrary AppArmor     profiles causing denial of service, exposure of sensitive information (kernel memory), local privilege     escalation, or possibly escape a container. (LP: #2143853)

    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;

    - Nios II architecture;

    - PA-RISC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - Sun Sparc architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Xtensa architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - ATM drivers;

    - Drivers core;

    - Block device driver;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Hardware random number generator core;

    - Character device driver;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - Device frequency scaling framework;

    - DMA engine subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - Intel Stratix 10 firmware drivers;

    - GPU drivers;

    - HID subsystem;

    - CoreSight HW tracing drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - Input Device (Tablet) drivers;

    - IOMMU subsystem;

    - ISDN/mISDN subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - MTD block device drivers;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - Texas Instruments network drivers;

    - Ethernet team driver;

    - NVME drivers;

    - PCI subsystem;

    - PCCARD (PCMCIA/CardBus) bus subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - PWM drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - Texas Instruments SoC drivers;

    - TCM subsystem;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - USB Mass Storage drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - AFS file system;

    - BTRFS file system;

    - Ceph distributed file system;

    - File systems infrastructure;

    - EFI Variable file system;

    - exFAT file system;

    - Ext4 file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - GFS2 file system;

    - HFS file system;

    - HFS+ file system;

    - HugeTLB file system;

    - JFS file system;

    - KERNFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - OrangeFS file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - SquashFS file system;

    - UDF file system;

    - XFS file system;

    - Asynchronous Transfer Mode (ATM) subsystem;

    - BPF subsystem;

    - Mellanox drivers;

    - NFS page cache wrapper;

    - Memory management;

    - Memory Management;

    - Media input infrastructure;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - Network traffic control;

    - Rose network layer;

    - Network sockets;

    - io_uring subsystem;

    - Control group (cgroup);

    - Kernel crash support code;

    - Kernel futex primitives;

    - PID allocator;

    - Scheduler infrastructure;

    - Syscalls implementation;

    - Timer subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Ceph Core library;

    - Networking core;

    - Devlink API;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - RF switch subsystem;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - Wireless networking;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - Intel ASoC drivers;

    - QCOM ASoC drivers;

    - USB sound devices; (CVE-2025-21833, CVE-2025-22037, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,     CVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124, CVE-2025-22125, CVE-2025-23129,     CVE-2025-23130, CVE-2025-23133, CVE-2025-23143, CVE-2025-37860, CVE-2025-37899, CVE-2025-38105,     CVE-2025-38502, CVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709, CVE-2025-39678,     CVE-2025-39697, CVE-2025-39805, CVE-2025-39806, CVE-2025-39807, CVE-2025-39808, CVE-2025-39810,     CVE-2025-39811, CVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817, CVE-2025-39819,     CVE-2025-39823, CVE-2025-39824, CVE-2025-39825, CVE-2025-39826, CVE-2025-39827, CVE-2025-39828,     CVE-2025-39829, CVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838, CVE-2025-39839,     CVE-2025-39841, CVE-2025-39842, CVE-2025-39843, CVE-2025-39844, CVE-2025-39845, CVE-2025-39846,     CVE-2025-39847, CVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851, CVE-2025-39852,     CVE-2025-39853, CVE-2025-39854, CVE-2025-39857, CVE-2025-39860, CVE-2025-39861, CVE-2025-39863,     CVE-2025-39864, CVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870, CVE-2025-39871,     CVE-2025-39873, CVE-2025-39876, CVE-2025-39877, CVE-2025-39880, CVE-2025-39881, CVE-2025-39883,     CVE-2025-39885, CVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895, CVE-2025-39897,     CVE-2025-39899, CVE-2025-39901, CVE-2025-39902, CVE-2025-39907, CVE-2025-39909, CVE-2025-39911,     CVE-2025-39913, CVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923, CVE-2025-39927,     CVE-2025-39929, CVE-2025-39931, CVE-2025-39932, CVE-2025-39934, CVE-2025-39937, CVE-2025-39938,     CVE-2025-39940, CVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945, CVE-2025-39947,     CVE-2025-39948, CVE-2025-39949, CVE-2025-39950, CVE-2025-39951, CVE-2025-39952, CVE-2025-39953,     CVE-2025-39955, CVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967, CVE-2025-39968,     CVE-2025-39969, CVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973, CVE-2025-39977,     CVE-2025-39978, CVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985, CVE-2025-39986,     CVE-2025-39987, CVE-2025-39988, CVE-2025-39991, CVE-2025-39992, CVE-2025-39994, CVE-2025-39995,     CVE-2025-39996, CVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006, CVE-2025-40008,     CVE-2025-40009, CVE-2025-40010, CVE-2025-40011, CVE-2025-40013, CVE-2025-40016, CVE-2025-40020,     CVE-2025-40021, CVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,     CVE-2025-40031, CVE-2025-40032, CVE-2025-40033, CVE-2025-40035, CVE-2025-40036, CVE-2025-40037,     CVE-2025-40038, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047, CVE-2025-40048,     CVE-2025-40049, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053, CVE-2025-40055, CVE-2025-40056,     CVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061, CVE-2025-40062,     CVE-2025-40067, CVE-2025-40068, CVE-2025-40070, CVE-2025-40071, CVE-2025-40077, CVE-2025-40078,     CVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084, CVE-2025-40085,     CVE-2025-40087, CVE-2025-40088, CVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,     CVE-2025-40096, CVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103, CVE-2025-40104,     CVE-2025-40105, CVE-2025-40106, CVE-2025-40107, CVE-2025-40109, CVE-2025-40110, CVE-2025-40111,     CVE-2025-40112, CVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,     CVE-2025-40123, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127, CVE-2025-40129,     CVE-2025-40134, CVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153, CVE-2025-40154,     CVE-2025-40155, CVE-2025-40156, CVE-2025-40159, CVE-2025-40160, CVE-2025-40165, CVE-2025-40166,     CVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173, CVE-2025-40176,     CVE-2025-40178, CVE-2025-40179, CVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,     CVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198, CVE-2025-40200,     CVE-2025-40201, CVE-2025-40202, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,     CVE-2025-40211, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,     CVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235, CVE-2025-40237, CVE-2025-40238,     CVE-2025-40240, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,     CVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40257,     CVE-2025-40258, CVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,     CVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272, CVE-2025-40273,     CVE-2025-40275, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,     CVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287,     CVE-2025-40288, CVE-2025-40289, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,     CVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,     CVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,     CVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,     CVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,     CVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341, CVE-2025-40342, CVE-2025-40343,     CVE-2025-40345, CVE-2025-40346, CVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,     CVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168, CVE-2025-68171,     CVE-2025-68172, CVE-2025-68173, CVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,     CVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68190, CVE-2025-68191,     CVE-2025-68192, CVE-2025-68194, CVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,     CVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217, CVE-2025-68218, CVE-2025-68219,     CVE-2025-68220, CVE-2025-68222, CVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,     CVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,     CVE-2025-68245, CVE-2025-68246, CVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,     CVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,     CVE-2025-68295, CVE-2025-68297, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,     CVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313,     CVE-2025-68315, CVE-2025-68320, CVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,     CVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340, CVE-2025-68342, CVE-2025-68343,     CVE-2025-68734)

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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2025-1254 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths (CVE-2025-39816)

    In the Linux kernel, the following vulnerability has been resolved:

    crypto: af_alg - Set merge to zero early in af_alg_sendmsg (CVE-2025-39931)

    In the Linux kernel, the following vulnerability has been resolved:

    dm-stripe: fix a possible integer overflow (CVE-2025-39940)

    In the Linux kernel, the following vulnerability has been resolved:

    tls: make sure to abort the stream if headers are bogus (CVE-2025-39946)

    In the Linux kernel, the following vulnerability has been resolved:

    net/mlx5e: Harden uplink netdev access against device unbind (CVE-2025-39947)

    In the Linux kernel, the following vulnerability has been resolved:

    cgroup: split cgroup_destroy_wq into 3 workqueues (CVE-2025-39953)

    In the Linux kernel, the following vulnerability has been resolved:

    tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). (CVE-2025-39955)

    In the Linux kernel, the following vulnerability has been resolved:

    igc: don't fail igc_probe() on LED setup error (CVE-2025-39956)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu/amd/pgtbl: Fix possible race while increase page table level (CVE-2025-39961)

    In the Linux kernel, the following vulnerability has been resolved:

    io_uring: fix incorrect io_kiocb reference in io_link_skb (CVE-2025-39963)

    In the Linux kernel, the following vulnerability has been resolved:

    crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (CVE-2025-39964)

    In the Linux kernel, the following vulnerability has been resolved:

    xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (CVE-2025-39965)

    In the Linux kernel, the following vulnerability has been resolved:

    fbcon: fix integer overflow in fbcon_do_set_font (CVE-2025-39967)

    In the Linux kernel, the following vulnerability has been resolved:

    smb: client: fix wrong index reference in smb2_compound_op() (CVE-2025-39975)

    In the Linux kernel, the following vulnerability has been resolved:

    futex: Prevent use-after-free during requeue-PI (CVE-2025-39977)

    In the Linux kernel, the following vulnerability has been resolved:

    nexthop: Forbid FDB status change while nexthop is in a group (CVE-2025-39980)

    In the Linux kernel, the following vulnerability has been resolved:

    net: tun: Update napi->skb after XDP process (CVE-2025-39984)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Check the helper function is valid in get_helper_proto (CVE-2025-39990)

    In the Linux kernel, the following vulnerability has been resolved:

    mm: swap: check for stable address space before operating on the VMA (CVE-2025-39992)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: target: target_core_configfs: Add length check to avoid buffer overflow (CVE-2025-39998)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/hugetlb: fix folio is still mapped when deleted (CVE-2025-40006)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/proc/task_mmu: check p->vec_buf for NULL (CVE-2025-40009)

    In the Linux kernel, the following vulnerability has been resolved:

    ipvs: Defer ip_vs_ftp unregister during netns cleanup (CVE-2025-40018)

    In the Linux kernel, the following vulnerability has been resolved:

    tracing: dynevent: Add a missing lockdown check on dynevent (CVE-2025-40021)

    In the Linux kernel, the following vulnerability has been resolved:

    vhost: Take a reference on the task in struct vhost_task. (CVE-2025-40024)

    In the Linux kernel, the following vulnerability has been resolved:

    pinctrl: check the return value of pinmux_ops::get_function_name() (CVE-2025-40030)

    In the Linux kernel, the following vulnerability has been resolved:

    Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak (CVE-2025-40035)

    In the Linux kernel, the following vulnerability has been resolved:

    fs: udf: fix OOB read in lengthAllocDescs handling (CVE-2025-40044)

    In the Linux kernel, the following vulnerability has been resolved:

    io_uring/waitid: always prune wait queue entry in io_waitid_wait() (CVE-2025-40047)

    In the Linux kernel, the following vulnerability has been resolved:

    uio_hv_generic: Let userspace take care of interrupt mask (CVE-2025-40048)

    In the Linux kernel, the following vulnerability has been resolved:

    Squashfs: fix uninit-value in squashfs_get_parent (CVE-2025-40049)

    In the Linux kernel, the following vulnerability has been resolved:

    smb: client: fix crypto buffers in non-linear memory (CVE-2025-40052)

    In the Linux kernel, the following vulnerability has been resolved:

    ptp: Add a upper bound on max_vclocks (CVE-2025-40057)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu/vt-d: Disallow dirty tracking if incoherent page walk (CVE-2025-40058)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist (CVE-2025-40067)

    In the Linux kernel, the following vulnerability has been resolved:

    fs: ntfs3: Fix integer overflow in run_unpack() (CVE-2025-40068)

    In the Linux kernel, the following vulnerability has been resolved:

    pps: fix warning in pps_register_cdev when register device fail (CVE-2025-40070)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Explicitly check accesses to bpf_sock_addr (CVE-2025-40078)

    In the Linux kernel, the following vulnerability has been resolved:

    nbd: restrict sockets to TCP and UDP (CVE-2025-40080)

    In the Linux kernel, the following vulnerability has been resolved:

    perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (CVE-2025-40081)

    In the Linux kernel, the following vulnerability has been resolved:

    crypto: rng - Ensure set_ent is always present (CVE-2025-40109)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (CVE-2025-40115)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Enforce expected_attach_type for tailcall compatibility (CVE-2025-40123)

    In the Linux kernel, the following vulnerability has been resolved:

    blk-mq: check kobject state_in_sysfs before deleting in blk_mq_unregister_hctx (CVE-2025-40125)

    In the Linux kernel, the following vulnerability has been resolved:

    sunrpc: fix null pointer dereference on zero-length checksum (CVE-2025-40129)

    In the Linux kernel, the following vulnerability has been resolved:

    dm: fix NULL pointer dereference in __dm_suspend() (CVE-2025-40134)

    In the Linux kernel, the following vulnerability has been resolved:

    mm: hugetlb: avoid soft lockup when mprotect to large memory area (CVE-2025-40153)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Reject negative offsets for ALU ops (CVE-2025-40169)

Tenable has extracted the preceding description block directly from the tested product 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: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: usb: roles: fix NULL pointer issue     when put module's reference In current design, usb role class driver will get usb_role_switch parent's     module reference after the user get usb_role_switch device and put the reference after the user put the     usb_role_switch device. However, the parent device of usb_role_switch may be removed before the user put     the usb_role_switch. If so, then, NULL pointer issue will be met when the user put the parent module's     reference. This will save the module pointer in structure of usb_role_switch. Then, we don't need to find     module by iterating long relations. (CVE-2024-26747)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: kunit: Fix potential null dereference     in kunit_device_driver_test() kunit_kzalloc() may return a NULL pointer, dereferencing it without NULL     check may lead to NULL dereference. Add a NULL check for test_state. (CVE-2024-56773)

  - In the Linux kernel, the following vulnerability has been resolved: arm64: ptrace: fix partial SETREGSET     for NT_ARM_FPMR Currently fpmr_set() doesn't initialize the temporary 'fpmr' variable, and a SETREGSET     call with a length of zero will leave this uninitialized. Consequently an arbitrary value will be written     back to target->thread.uw.fpmr, potentially leaking up to 64 bits of memory from the kernel stack. The     read is limited to a specific slot on the stack, and the issue does not provide a write mechanism. Fix     this by initializing the temporary value before copying the regset from userspace, as for other regsets     (e.g. NT_PRSTATUS, NT_PRFPREG, NT_ARM_SYSTEM_CALL). In the case of a zero-length write, the existing     contents of FPMR will be retained. Before this patch: | # ./fpmr-test | Attempting to write     NT_ARM_FPMR::fpmr = 0x900d900d900d900d | SETREGSET(nt=0x40e, len=8) wrote 8 bytes | | Attempting to read     NT_ARM_FPMR::fpmr | GETREGSET(nt=0x40e, len=8) read 8 bytes | Read NT_ARM_FPMR::fpmr = 0x900d900d900d900d     | | Attempting to write NT_ARM_FPMR (zero length) | SETREGSET(nt=0x40e, len=0) wrote 0 bytes | |     Attempting to read NT_ARM_FPMR::fpmr | GETREGSET(nt=0x40e, len=8) read 8 bytes | Read NT_ARM_FPMR::fpmr =     0xffff800083963d50 After this patch: | # ./fpmr-test | Attempting to write NT_ARM_FPMR::fpmr =     0x900d900d900d900d | SETREGSET(nt=0x40e, len=8) wrote 8 bytes | | Attempting to read NT_ARM_FPMR::fpmr |     GETREGSET(nt=0x40e, len=8) read 8 bytes | Read NT_ARM_FPMR::fpmr = 0x900d900d900d900d | | Attempting to     write NT_ARM_FPMR (zero length) | SETREGSET(nt=0x40e, len=0) wrote 0 bytes | | Attempting to read     NT_ARM_FPMR::fpmr | GETREGSET(nt=0x40e, len=8) read 8 bytes | Read NT_ARM_FPMR::fpmr = 0x900d900d900d900d     (CVE-2024-57878)

  - In the Linux kernel, the following vulnerability has been resolved: mptcp: fix 'scheduling while atomic'     in mptcp_pm_nl_append_new_local_addr If multiple connection requests attempt to create an implicit mptcp     endpoint in parallel, more than one caller may end up in mptcp_pm_nl_append_new_local_addr because none     found the address in local_addr_list during their call to mptcp_pm_nl_get_local_id. In this case, the     concurrent new_local_addr calls may delete the address entry created by the previous caller. These deletes     use synchronize_rcu, but this is not permitted in some of the contexts where this function may be called.
    During packet recv, the caller may be in a rcu read critical section and have preemption disabled. An     example stack: BUG: scheduling while atomic: swapper/2/0/0x00000302 Call Trace: <IRQ> dump_stack_lvl     (lib/dump_stack.c:117 (discriminator 1)) dump_stack (lib/dump_stack.c:124) __schedule_bug     (kernel/sched/core.c:5943) schedule_debug.constprop.0 (arch/x86/include/asm/preempt.h:33     kernel/sched/core.c:5970) __schedule (arch/x86/include/asm/jump_label.h:27 include/linux/jump_label.h:207     kernel/sched/features.h:29 kernel/sched/core.c:6621) schedule (arch/x86/include/asm/preempt.h:84     kernel/sched/core.c:6804 kernel/sched/core.c:6818) schedule_timeout (kernel/time/timer.c:2160)     wait_for_completion (kernel/sched/completion.c:96 kernel/sched/completion.c:116     kernel/sched/completion.c:127 kernel/sched/completion.c:148) __wait_rcu_gp (include/linux/rcupdate.h:311     kernel/rcu/update.c:444) synchronize_rcu (kernel/rcu/tree.c:3609) mptcp_pm_nl_append_new_local_addr     (net/mptcp/pm_netlink.c:966 net/mptcp/pm_netlink.c:1061) mptcp_pm_nl_get_local_id     (net/mptcp/pm_netlink.c:1164) mptcp_pm_get_local_id (net/mptcp/pm.c:420) subflow_check_req     (net/mptcp/subflow.c:98 net/mptcp/subflow.c:213) subflow_v4_route_req (net/mptcp/subflow.c:305)     tcp_conn_request (net/ipv4/tcp_input.c:7216) subflow_v4_conn_request (net/mptcp/subflow.c:651)     tcp_rcv_state_process (net/ipv4/tcp_input.c:6709) tcp_v4_do_rcv (net/ipv4/tcp_ipv4.c:1934) tcp_v4_rcv     (net/ipv4/tcp_ipv4.c:2334) ip_protocol_deliver_rcu (net/ipv4/ip_input.c:205 (discriminator 1))     ip_local_deliver_finish (include/linux/rcupdate.h:813 net/ipv4/ip_input.c:234) ip_local_deliver     (include/linux/netfilter.h:314 include/linux/netfilter.h:308 net/ipv4/ip_input.c:254)     ip_sublist_rcv_finish (include/net/dst.h:461 net/ipv4/ip_input.c:580) ip_sublist_rcv     (net/ipv4/ip_input.c:640) ip_list_rcv (net/ipv4/ip_input.c:675) __netif_receive_skb_list_core     (net/core/dev.c:5583 net/core/dev.c:5631) netif_receive_skb_list_internal (net/core/dev.c:5685     net/core/dev.c:5774) napi_complete_done (include/linux/list.h:37 include/net/gro.h:449     include/net/gro.h:444 net/core/dev.c:6114) igb_poll (drivers/net/ethernet/intel/igb/igb_main.c:8244) igb
    __napi_poll (net/core/dev.c:6582) net_rx_action (net/core/dev.c:6653 net/core/dev.c:6787) handle_softirqs     (kernel/softirq.c:553) __irq_exit_rcu (kernel/softirq.c:588 kernel/softirq.c:427 kernel/softirq.c:636)     irq_exit_rcu (kernel/softirq.c:651) common_interrupt (arch/x86/kernel/irq.c:247 (discriminator 14)) </IRQ>     This problem seems particularly prevalent if the user advertises an endpoint that has a different external     vs internal address. In the case where the external address is advertised and multiple connections already     exist, multiple subflow SYNs arrive in parallel which tends to trigger the race during creation of the     first local_addr_list entries which have the internal address instead. Fix by skipping the replacement of     an existing implicit local address if called via mptcp_pm_nl_get_local_id. (CVE-2025-21938)

  - In the Linux kernel, the following vulnerability has been resolved: devlink: fix xa_alloc_cyclic() error     handling In case of returning 1 from xa_alloc_cyclic() (wrapping) ERR_PTR(1) will be returned, which will     cause IS_ERR() to be false. Which can lead to dereference not allocated pointer (rel). Fix it by checking     if err is lower than zero. This wasn't found in real usecase, only noticed. Credit to Pierre.
    (CVE-2025-22017)

  - In the Linux kernel, the following vulnerability has been resolved: drm/xe: Use local fence in error path     of xe_migrate_clear The intent of the error path in xe_migrate_clear is to wait on locally generated fence     and then return. The code is waiting on m->fence which could be the local fence but this is only stable     under the job mutex leading to a possible UAF. Fix code to wait on local fence. (cherry picked from commit     762b7e95362170b3e13a8704f38d5e47eca4ba74) (CVE-2025-37869)

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

ID	Name	Product	Family	Published	Updated	Severity
278559	Debian dla-4404 : ata-modules-5.10.0-35-armmp-di - security update	Nessus	Debian Local Security Checks	12/12/2025	9/18/2026	high
304789	Ubuntu 22.04 LTS : Linux kernel (Raspberry Pi) vulnerabilities (USN-8141-1)	Nessus	Ubuntu Local Security Checks	4/3/2026	4/3/2026	high
304015	Ubuntu 24.04 LTS : Linux kernel (Azure) vulnerabilities (USN-8125-1)	Nessus	Ubuntu Local Security Checks	3/27/2026	3/27/2026	high
271737	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2025-1254)	Nessus	Amazon Linux Local Security Checks	10/28/2025	9/18/2026	high
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	10/12/2026	10/12/2026	critical
364689	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1791800936)	Nessus	Alma Linux Local Security Checks	10/12/2026	10/12/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

critical

high