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

  - xsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx This patch is inspired by the check[1]     from sashiko. It says when overflow happens, the address of cq to be published is invalid. Actually the     severer thing is the whole process of publishing the address of cq in this particular case is not right:
    it should truely publish the address and advance the cached_prod in cq as long as it reads descriptors     from txq. The following is the full analysis. xsk_drop_skb() is called in three places, which all discard     a partially built multi-buffer skb: 1) xsk_build_skb() -EOVERFLOW error path: packet exceeds MAX_SKB_FRAGS     2) __xsk_generic_xmit() post-loop cleanup: an invalid descriptor in the TX ring prevents the partial     packet from completing 3) xsk_release(): socket close while xs->skb holds an incomplete packet In all     three cases, the TX descriptors for the already-processed frags have been consumed from the TX ring     (xskq_cons_release), and CQ slots have been reserved. However, xsk_drop_skb() calls xsk_consume_skb()     which cancels the CQ reservations via xsk_cq_cancel_locked(). Since the buffer addresses never appear in     the completion queue, userspace permanently loses track of these buffers. Fix this by letting     consume_skb() trigger the existing xsk_destruct_skb destructor, which already submits buffer addresses to     the CQ via xsk_cq_submit_addr_locked(). Note that cancelling the descriptors back to the TX ring (via     xskq_cons_cancel_n) is not a appropriate option because an oversized packet that always exceeds     MAX_SKB_FRAGS would be retried indefinitely, which is an obviously deadlock bug in the TX path. Also move     the desc->addr assignment in xsk_build_skb() above the overflow check so that the current descriptor's     address is recorded before a potential -EOVERFLOW jump to free_err, consistent with the zerocopy path in     xsk_build_skb_zerocopy(). [1]: https://lore.kernel.org/all/20260425041726.85FB3C2BCB2@smtp.kernel.org/     (CVE-2026-74560)

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

ID	Name	Product	Family	Published	Updated	Severity
335832	Linux Distros Unpatched Vulnerability : CVE-2026-74560	Nessus	Misc.	8/15/2026	9/1/2026	medium
341888	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-2106)	Nessus	Amazon Linux Local Security Checks	8/31/2026	9/1/2026	high

Detections

Analytics

Plugins Search

medium

high