The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - veth: more robust handing of race to avoid txq getting stuck Commit dc82a33297fc (veth: apply qdisc     backpressure on full ptr_ring to reduce TX drops) introduced a race condition that can lead to a     permanently stalled TXQ. This was observed in production on ARM64 systems (Ampere Altra Max). The race     occurs in veth_xmit(). The producer observes a full ptr_ring and stops the queue (netif_tx_stop_queue()).
    The subsequent conditional logic, intended to re-wake the queue if the consumer had just emptied it (if     (__ptr_ring_empty(...)) netif_tx_wake_queue()), can fail. This leads to a lost wakeup where the TXQ     remains stopped (QUEUE_STATE_DRV_XOFF) and traffic halts. This failure is caused by an incorrect use of     the __ptr_ring_empty() API from the producer side. As noted in kernel comments, this check is not     guaranteed to be correct if a consumer is operating on another CPU. The empty test is based on     ptr_ring->consumer_head, making it reliable only for the consumer. Using this check from the producer side     is fundamentally racy. This patch fixes the race by adopting the more robust logic from an earlier version     V4 of the patchset, which always flushed the peer: (1) In veth_xmit(), the racy conditional wake-up logic     and its memory barrier are removed. Instead, after stopping the queue, we unconditionally call
    __veth_xdp_flush(rq). This guarantees that the NAPI consumer is scheduled, making it solely responsible     for re-waking the TXQ. This handles the race where veth_poll() consumes all packets and completes NAPI
    *before* veth_xmit() on the producer side has called netif_tx_stop_queue. The __veth_xdp_flush(rq) will     observe rx_notify_masked is false and schedule NAPI. (2) On the consumer side, the logic for waking the     peer TXQ is moved out of veth_xdp_rcv() and placed at the end of the veth_poll() function. This placement     is part of fixing the race, as the netif_tx_queue_stopped() check must occur after rx_notify_masked is     potentially set to false during NAPI completion. This handles the race where veth_poll() consumes all     packets, but haven't finished (rx_notify_masked is still true). The producer veth_xmit() stops the TXQ and
    __veth_xdp_flush(rq) will observe rx_notify_masked is true, meaning not starting NAPI. Then veth_poll()     change rx_notify_masked to false and stops NAPI. Before exiting veth_poll() will observe TXQ is stopped     and wake it up. (CVE-2025-68232)

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

The remote Ubuntu 24.04 LTS / 25.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8094-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)

    It was discovered that some AMD Zen 5 processors supporting RDSEED instruction did not properly handle     entropy, potentially resulting in the consumption of insufficiently random values. A local attacker could     possibly use this issue to influence the values returned by the RDSEED instruction causing loss of     confidentiality and integrity. (CVE-2025-62626)

    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;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ATM drivers;

    - Network block device driver;

    - Bluetooth drivers;

    - Data acquisition framework and drivers;

    - Hardware crypto device drivers;

    - Device frequency scaling framework;

    - Intel Stratix 10 firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - Microsoft Hyper-V drivers;

    - CoreSight HW tracing drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Tablet) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Macintosh device drivers;

    - Multiple devices driver;

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

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Voltage and Current Regulator drivers;

    - Real Time Clock drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - Texas Instruments SoC drivers;

    - SPI subsystem;

    - Media Oriented Systems Transport (MOST) driver;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - UFS subsystem;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - Renesas USBHS Controller drivers;

    - USB Mass Storage drivers;

    - USB Type-C Connector System Software Interface driver;

    - Backlight driver;

    - Framebuffer layer;

    - AFS file system;

    - BFS file system;

    - BTRFS file system;

    - EROFS file system;

    - Ext4 file system;

    - FAT file system;

    - GFS2 file system;

    - Journaling layer for block devices (JBD2);

    - File systems infrastructure;

    - Network file system (NFS) client;

    - NTFS3 file system;

    - OCFS2 file system;

    - SMB network file system;

    - XFS file system;

    - BPF subsystem;

    - MediaTek SoC drivers;

    - Bluetooth subsystem;

    - io_uring subsystem;

    - Locking primitives;

    - Scheduler infrastructure;

    - Timer subsystem;

    - Tracing infrastructure;

    - Kexec HandOver (KHO);

    - Memory management;

    - Ceph Core library;

    - Networking core;

    - Devlink API;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver;

    - eXpress Data Path;

    - Integrity Measurement Architecture(IMA) framework;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - Turtle Beach Wavefront ALSA driver;

    - SoundWire (SDCA) ASoC drivers; (CVE-2025-40246, CVE-2025-40247, CVE-2025-40248, CVE-2025-40249,     CVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40255,     CVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40260, CVE-2025-40261, CVE-2025-40262,     CVE-2025-40263, CVE-2025-40264, CVE-2025-40265, CVE-2025-40266, CVE-2025-40290, CVE-2025-40345,     CVE-2025-68212, CVE-2025-68213, CVE-2025-68214, CVE-2025-68215, CVE-2025-68217, CVE-2025-68218,     CVE-2025-68219, CVE-2025-68220, CVE-2025-68221, CVE-2025-68222, CVE-2025-68223, CVE-2025-68225,     CVE-2025-68227, CVE-2025-68228, CVE-2025-68229, CVE-2025-68230, CVE-2025-68231, CVE-2025-68232,     CVE-2025-68233, CVE-2025-68234, CVE-2025-68235, CVE-2025-68236, CVE-2025-68237, CVE-2025-68238,     CVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257, CVE-2025-68258, CVE-2025-68259,     CVE-2025-68261, CVE-2025-68262, CVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,     CVE-2025-68281, 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-68292, CVE-2025-68293,     CVE-2025-68294, CVE-2025-68295, CVE-2025-68296, CVE-2025-68297, CVE-2025-68298, CVE-2025-68299,     CVE-2025-68300, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68304, CVE-2025-68305,     CVE-2025-68306, CVE-2025-68307, CVE-2025-68308, CVE-2025-68323, CVE-2025-68324, CVE-2025-68325,     CVE-2025-68326, CVE-2025-68327, CVE-2025-68328, CVE-2025-68329, CVE-2025-68330, CVE-2025-68331,     CVE-2025-68332, CVE-2025-68333, CVE-2025-68334, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,     CVE-2025-68338, CVE-2025-68339, CVE-2025-68340, CVE-2025-68341, CVE-2025-68342, CVE-2025-68343,     CVE-2025-68344, CVE-2025-68345, CVE-2025-68346, CVE-2025-68347, CVE-2025-68348, CVE-2025-68349,     CVE-2025-68352, CVE-2025-68354, CVE-2025-68356, CVE-2025-68358, CVE-2025-68359, CVE-2025-68360,     CVE-2025-68361, CVE-2025-68362, CVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,     CVE-2025-68369, CVE-2025-68370, CVE-2025-68371, CVE-2025-68372, CVE-2025-68373, CVE-2025-68374,     CVE-2025-68375, CVE-2025-68376, CVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,     CVE-2025-68726, CVE-2025-68727, CVE-2025-68728, CVE-2025-68729, CVE-2025-68730, CVE-2025-68732,     CVE-2025-68733, CVE-2025-68735, CVE-2025-68738, CVE-2025-68739, CVE-2025-68740, CVE-2025-68741,     CVE-2025-68742, CVE-2025-68743, CVE-2025-68744, CVE-2025-68746, CVE-2025-68747, CVE-2025-68748,     CVE-2025-68749, CVE-2025-68751, CVE-2025-68752, CVE-2025-68753, CVE-2025-68754, CVE-2025-68755,     CVE-2025-68756, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68760, CVE-2025-68762,     CVE-2025-68763, CVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-71128)

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.

ID	Name	Product	Family	Published	Updated	Severity
278797	Linux Distros Unpatched Vulnerability : CVE-2025-68232	Nessus	Misc.	12/16/2025	4/7/2026	medium
302766	Ubuntu 24.04 LTS / 25.10 : Linux kernel vulnerabilities (USN-8094-1)	Nessus	Ubuntu Local Security Checks	3/17/2026	3/26/2026	high

Detections

Analytics

Plugins Search

medium

high