In the Linux kernel, the following vulnerability has been resolved: ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and pending-delete state in ksmbd_inode->m_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read and modify m_flags under ci->m_lock while others do so without taking the lock at all. Examples: - ksmbd_query_inode_status() and __ksmbd_inode_close() use ci->m_lock when checking or updating m_flags. - ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete() and ksmbd_fd_set_delete_on_close() used to read and modify m_flags without ci->m_lock. This creates a potential data race on m_flags when multiple threads open, close and delete the same file concurrently. In the worst case delete-on-close and pending-delete bits can be lost or observed in an inconsistent state, leading to confusing delete semantics (files that stay on disk after delete-on-close, or files that disappear while still in use). Fix it by: - Making ksmbd_query_inode_status() look at m_flags under ci->m_lock after dropping inode_hash_lock. - Adding ci->m_lock protection to all helpers that read or modify m_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()). - Keeping the existing ci->m_lock protection in __ksmbd_inode_close(), and moving the actual unlink/xattr removal outside the lock. This unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close behaviour.

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

    Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo Rizzo discovered that some AMD     Zen processors did not properly verify the signature of CPU microcode. This flaw is known as EntrySign. A     privileged attacker could possibly use this issue to cause load malicious CPU microcode causing loss of     integrity and confidentiality. (CVE-2024-36347)

    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:

    - MIPS architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - Network block device driver;

    - Bluetooth drivers;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Hardware crypto device drivers;

    - GPU drivers;

    - Hardware monitoring drivers;

    - InfiniBand drivers;

    - Input Device core drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Macintosh device drivers;

    - Multiple devices driver;

    - Media drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - Ethernet team driver;

    - MediaTek network drivers;

    - NVME drivers;

    - PA-RISC drivers;

    - Chrome hardware platform drivers;

    - x86 platform drivers;

    - Voltage and Current Regulator drivers;

    - SCSI subsystem;

    - SPI subsystem;

    - Media Oriented Systems Transport (MOST) driver;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - USB Host Controller drivers;

    - USB Type-C Connector System Software Interface driver;

    - Backlight driver;

    - Watchdog drivers;

    - BFS file system;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - HFS+ file system;

    - File systems infrastructure;

    - Journaling layer for block devices (JBD2);

    - Network file system (NFS) client;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - SMB network file system;

    - BPF subsystem;

    - Ethernet bridge;

    - io_uring subsystem;

    - Locking primitives;

    - Scheduler infrastructure;

    - Shadow Call Stack mechanism;

    - Tracing infrastructure;

    - Memory management;

    - CAIF protocol;

    - Ceph Core library;

    - Networking core;

    - Ethtool driver;

    - Handshake API;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NET/ROM layer;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Network sockets;

    - Sun RPC protocol;

    - Integrity Measurement Architecture(IMA) framework;

    - Key management;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - Turtle Beach Wavefront ALSA driver;

    - STMicroelectronics SoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022, CVE-2025-38234,     CVE-2025-40164, CVE-2025-40325, CVE-2025-68206, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,     CVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263, CVE-2025-68264,     CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68325, CVE-2025-68332, CVE-2025-68335,     CVE-2025-68336, CVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346, CVE-2025-68347,     CVE-2025-68349, CVE-2025-68354, CVE-2025-68362, CVE-2025-68363, CVE-2025-68364, CVE-2025-68366,     CVE-2025-68367, CVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374, CVE-2025-68378,     CVE-2025-68379, CVE-2025-68380, CVE-2025-68724, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,     CVE-2025-68733, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744, CVE-2025-68746,     CVE-2025-68753, CVE-2025-68755, CVE-2025-68756, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759,     CVE-2025-68763, CVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767, CVE-2025-68769,     CVE-2025-68770, CVE-2025-68771, CVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,     CVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,     CVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788, CVE-2025-68794, CVE-2025-68795,     CVE-2025-68796, CVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800, CVE-2025-68801,     CVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809, CVE-2025-68810, CVE-2025-68811,     CVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,     CVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-71064, CVE-2025-71065, CVE-2025-71066,     CVE-2025-71067, CVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072, 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-71088, CVE-2025-71089,     CVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71095, CVE-2025-71096, CVE-2025-71097,     CVE-2025-71098, CVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105, CVE-2025-71107,     CVE-2025-71108, CVE-2025-71109, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,     CVE-2025-71116, CVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121, CVE-2025-71122,     CVE-2025-71123, CVE-2025-71125, CVE-2025-71126, CVE-2025-71127, CVE-2025-71130, CVE-2025-71131,     CVE-2025-71132, CVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,     CVE-2025-71140, CVE-2025-71141, CVE-2025-71143, CVE-2025-71144, CVE-2025-71147, CVE-2025-71148,     CVE-2025-71149, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2026-23209)

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 25.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8177-1 advisory.

    Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo Rizzo discovered that some AMD     Zen processors did not properly verify the signature of CPU microcode. This flaw is known as EntrySign. A     privileged attacker could possibly use this issue to cause load malicious CPU microcode causing loss of     integrity and confidentiality. (CVE-2024-36347)

    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:

    - MIPS architecture;

    - PowerPC architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - Ublk userspace block driver;

    - Bluetooth drivers;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - GPU drivers;

    - Hardware monitoring drivers;

    - Intel Trace Hub HW tracing drivers;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - Ethernet team driver;

    - PA-RISC drivers;

    - Chrome hardware platform drivers;

    - x86 platform drivers;

    - SCSI subsystem;

    - SPI subsystem;

    - TCM subsystem;

    - Freescale USB OTG Transceiver Driver;

    - USB Type-C Connector System Software Interface driver;

    - Watchdog drivers;

    - BTRFS file system;

    - exFAT file system;

    - Ext4 file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - HFS+ file system;

    - File systems infrastructure;

    - Network file system (NFS) server daemon;

    - File system notification infrastructure;

    - NTFS3 file system;

    - OCFS2 file system;

    - SMB network file system;

    - XFS file system;

    - User-space API (UAPI);

    - io_uring subsystem;

    - Scheduler infrastructure;

    - Shadow Call Stack mechanism;

    - Tracing infrastructure;

    - Memory management;

    - BPF subsystem;

    - CAIF protocol;

    - Ceph Core library;

    - Networking core;

    - Ethtool driver;

    - Handshake API;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NET/ROM layer;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Sun RPC protocol;

    - Key management;

    - Landlock security;

    - STMicroelectronics SoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2025-68351, CVE-2025-68353, CVE-2025-68365, CVE-2025-68368, CVE-2025-68725,     CVE-2025-68736, CVE-2025-68745, CVE-2025-68767, CVE-2025-68768, CVE-2025-68769, CVE-2025-68770,     CVE-2025-68771, CVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,     CVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68781, CVE-2025-68782, CVE-2025-68783,     CVE-2025-68784, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788, CVE-2025-68791,     CVE-2025-68792, CVE-2025-68793, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,     CVE-2025-68798, CVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68802, CVE-2025-68803,     CVE-2025-68804, CVE-2025-68805, CVE-2025-68806, CVE-2025-68807, CVE-2025-68808, CVE-2025-68809,     CVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,     CVE-2025-68817, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-68822,     CVE-2025-68823, CVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067, CVE-2025-71068,     CVE-2025-71069, CVE-2025-71070, CVE-2025-71071, CVE-2025-71072, CVE-2025-71073, CVE-2025-71075,     CVE-2025-71076, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71080, CVE-2025-71081,     CVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,     CVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71095, CVE-2025-71096,     CVE-2025-71097, CVE-2025-71098, CVE-2025-71099, CVE-2025-71100, CVE-2025-71101, CVE-2025-71102,     CVE-2025-71104, CVE-2025-71105, CVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,     CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71115, CVE-2025-71116, CVE-2025-71117,     CVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121, CVE-2025-71122, CVE-2025-71123,     CVE-2025-71124, CVE-2025-71125, CVE-2025-71126, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,     CVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138, CVE-2025-71140,     CVE-2025-71143, CVE-2025-71146, CVE-2025-71147, CVE-2025-71148, CVE-2025-71149, CVE-2025-71150,     CVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2025-71156, CVE-2025-71157, CVE-2026-23091,     CVE-2026-23209)

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

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

The remote Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6126 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6126-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     February 09, 2026                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2024-58096 CVE-2024-58097 CVE-2025-22111 CVE-2025-38234                      CVE-2025-38248 CVE-2025-38591 CVE-2025-39872 CVE-2025-40149                      CVE-2025-40164 CVE-2025-40170 CVE-2025-40276 CVE-2025-40325                      CVE-2025-68206 CVE-2025-68333 CVE-2025-68345 CVE-2025-68351                      CVE-2025-68357 CVE-2025-68358 CVE-2025-68365 CVE-2025-68725                      CVE-2025-68749 CVE-2025-68767 CVE-2025-68769 CVE-2025-68770                      CVE-2025-68771 CVE-2025-68772 CVE-2025-68773 CVE-2025-68774                      CVE-2025-68775 CVE-2025-68776 CVE-2025-68777 CVE-2025-68778                      CVE-2025-68780 CVE-2025-68781 CVE-2025-68782 CVE-2025-68783                      CVE-2025-68784 CVE-2025-68785 CVE-2025-68786 CVE-2025-68787                      CVE-2025-68788 CVE-2025-68789 CVE-2025-68792 CVE-2025-68794                      CVE-2025-68795 CVE-2025-68796 CVE-2025-68797 CVE-2025-68798                      CVE-2025-68799 CVE-2025-68800 CVE-2025-68801 CVE-2025-68802                      CVE-2025-68803 CVE-2025-68804 CVE-2025-68806 CVE-2025-68808                      CVE-2025-68809 CVE-2025-68810 CVE-2025-68811 CVE-2025-68813                      CVE-2025-68814 CVE-2025-68815 CVE-2025-68816 CVE-2025-68817                      CVE-2025-68818 CVE-2025-68819 CVE-2025-68820 CVE-2025-68821                      CVE-2025-68822 CVE-2025-71064 CVE-2025-71065 CVE-2025-71066                      CVE-2025-71067 CVE-2025-71068 CVE-2025-71069 CVE-2025-71071                      CVE-2025-71072 CVE-2025-71073 CVE-2025-71075 CVE-2025-71076                      CVE-2025-71077 CVE-2025-71078 CVE-2025-71079 CVE-2025-71080                      CVE-2025-71081 CVE-2025-71082 CVE-2025-71083 CVE-2025-71084                      CVE-2025-71085 CVE-2025-71086 CVE-2025-71087 CVE-2025-71088                      CVE-2025-71089 CVE-2025-71091 CVE-2025-71093 CVE-2025-71094                      CVE-2025-71095 CVE-2025-71096 CVE-2025-71097 CVE-2025-71098                      CVE-2025-71099 CVE-2025-71100 CVE-2025-71101 CVE-2025-71102                      CVE-2025-71104 CVE-2025-71105 CVE-2025-71107 CVE-2025-71108                      CVE-2025-71109 CVE-2025-71111 CVE-2025-71112 CVE-2025-71113                      CVE-2025-71114 CVE-2025-71116 CVE-2025-71118 CVE-2025-71119                      CVE-2025-71120 CVE-2025-71121 CVE-2025-71122 CVE-2025-71123                      CVE-2025-71125 CVE-2025-71126 CVE-2025-71127 CVE-2025-71129                      CVE-2025-71130 CVE-2025-71131 CVE-2025-71132 CVE-2025-71133                      CVE-2025-71134 CVE-2025-71135 CVE-2025-71136 CVE-2025-71137                      CVE-2025-71138 CVE-2025-71140 CVE-2025-71143 CVE-2025-71144                      CVE-2025-71146 CVE-2025-71147 CVE-2025-71148 CVE-2025-71149                      CVE-2025-71150 CVE-2025-71151 CVE-2025-71153 CVE-2025-71154                      CVE-2025-71156 CVE-2025-71157 CVE-2025-71160 CVE-2025-71162                      CVE-2025-71163 CVE-2025-71180 CVE-2025-71182 CVE-2025-71183                      CVE-2025-71184 CVE-2025-71185 CVE-2025-71186 CVE-2025-71189                      CVE-2025-71190 CVE-2025-71191 CVE-2025-71192 CVE-2025-71193                      CVE-2025-71194 CVE-2025-71195 CVE-2025-71196 CVE-2025-71197                      CVE-2025-71198 CVE-2025-71199 CVE-2026-22976 CVE-2026-22977                      CVE-2026-22978 CVE-2026-22979 CVE-2026-22980 CVE-2026-22982                      CVE-2026-22984 CVE-2026-22989 CVE-2026-22990 CVE-2026-22991                      CVE-2026-22992 CVE-2026-22994 CVE-2026-22996 CVE-2026-22997                      CVE-2026-22998 CVE-2026-22999 CVE-2026-23000 CVE-2026-23001                      CVE-2026-23002 CVE-2026-23003 CVE-2026-23005 CVE-2026-23006                      CVE-2026-23010 CVE-2026-23011 CVE-2026-23013 CVE-2026-23019                      CVE-2026-23020 CVE-2026-23021 CVE-2026-23023 CVE-2026-23025                      CVE-2026-23026 CVE-2026-23030 CVE-2026-23031 CVE-2026-23032                      CVE-2026-23033 CVE-2026-23035 CVE-2026-23037 CVE-2026-23038                      CVE-2026-23047 CVE-2026-23049 CVE-2026-23050 CVE-2026-23053                      CVE-2026-23054 CVE-2026-23055 CVE-2026-23056 CVE-2026-23057                      CVE-2026-23058 CVE-2026-23059 CVE-2026-23060 CVE-2026-23061                      CVE-2026-23062 CVE-2026-23063 CVE-2026-23064 CVE-2026-23065                      CVE-2026-23068 CVE-2026-23069 CVE-2026-23071 CVE-2026-23072                      CVE-2026-23073 CVE-2026-23074 CVE-2026-23075 CVE-2026-23076                      CVE-2026-23078 CVE-2026-23080 CVE-2026-23083 CVE-2026-23084                      CVE-2026-23085 CVE-2026-23086 CVE-2026-23087 CVE-2026-23088                      CVE-2026-23089 CVE-2026-23090 CVE-2026-23091 CVE-2026-23093                      CVE-2026-23094 CVE-2026-23095 CVE-2026-23096 CVE-2026-23097                      CVE-2026-23098 CVE-2026-23099 CVE-2026-23101 CVE-2026-23103                      CVE-2026-23105 CVE-2026-23107 CVE-2026-23108 CVE-2026-23110

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

    For the stable distribution (trixie), these problems have been fixed in     version 6.12.69-1.

    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 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and pending-delete state in     ksmbd_inode->m_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read     and modify m_flags under ci->m_lock while others do so without taking the lock at all. Examples: -     ksmbd_query_inode_status() and __ksmbd_inode_close() use ci->m_lock when checking or updating m_flags. -     ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete() and     ksmbd_fd_set_delete_on_close() used to read and modify m_flags without ci->m_lock. This creates a     potential data race on m_flags when multiple threads open, close and delete the same file concurrently. In     the worst case delete-on-close and pending-delete bits can be lost or observed in an inconsistent state,     leading to confusing delete semantics (files that stay on disk after delete-on-close, or files that     disappear while still in use). Fix it by: - Making ksmbd_query_inode_status() look at m_flags under     ci->m_lock after dropping inode_hash_lock. - Adding ci->m_lock protection to all helpers that read or     modify m_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(),     ksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()). - Keeping the existing ci->m_lock     protection in __ksmbd_inode_close(), and moving the actual unlink/xattr removal outside the lock. This     unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close     behaviour. (CVE-2025-68809)

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

ID	Name	Product	Family	Severity
307007	Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel vulnerabilities (USN-8179-1)	Nessus	Ubuntu Local Security Checks	high
307005	Ubuntu 25.10 : Linux kernel vulnerabilities (USN-8177-1)	Nessus	Ubuntu Local Security Checks	high
298403	Debian dsa-6126 : ata-modules-6.12.31-armmp-di - security update	Nessus	Debian Local Security Checks	high
283636	Linux Distros Unpatched Vulnerability : CVE-2025-68809	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-68809

high

Tenable Plugins

high

high

high

medium