In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix zerocopy completion for multi-skb sends When a large message is fragmented into multiple skbs, the zerocopy uarg is only allocated and attached to the last skb in the loop. Non-final skbs carry pinned user pages with no completion tracking, so the kernel has no way to notify userspace when those pages are safe to reuse. If the loop breaks early the uarg is never allocated at all, leaking pinned pages with no completion notification. Fix this by following the approach used by TCP: allocate the zerocopy uarg (if not provided by the caller) before the send loop and attach it to every skb via skb_zcopy_set(), which takes a reference per skb. Each skb's completion properly decrements the refcount, and the notification only fires after the last skb is freed. On failure, if no data was sent, the uarg is cleanly aborted via net_zcopy_put_abort(). This issue was initially discovered by sashiko while reviewing commit 1cb36e252211 ("vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting") but was pre-existing.

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

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6405-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     July 31, 2026                         https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2026-45944 CVE-2026-53005 CVE-2026-53260 CVE-2026-53365                      CVE-2026-63970 CVE-2026-64192 CVE-2026-64206 CVE-2026-64227                      CVE-2026-64286 CVE-2026-64287 CVE-2026-64307 CVE-2026-64341                      CVE-2026-64352 CVE-2026-64361 CVE-2026-64363 CVE-2026-64364                      CVE-2026-64369 CVE-2026-64371 CVE-2026-64375 CVE-2026-64390                      CVE-2026-64401 CVE-2026-64405 CVE-2026-64413 CVE-2026-64416                      CVE-2026-64421 CVE-2026-64428 CVE-2026-64434 CVE-2026-64438                      CVE-2026-64441 CVE-2026-64461 CVE-2026-64462 CVE-2026-64472                      CVE-2026-64481 CVE-2026-64488 CVE-2026-64493 CVE-2026-64507                      CVE-2026-64508 CVE-2026-64509 CVE-2026-64510 CVE-2026-64530                      CVE-2026-64531 CVE-2026-64532 CVE-2026-64533 CVE-2026-64534                      CVE-2026-64535 CVE-2026-64537 CVE-2026-64538 CVE-2026-64539                      CVE-2026-64540 CVE-2026-64541 CVE-2026-64542 CVE-2026-64543                      CVE-2026-64544 CVE-2026-64545 CVE-2026-64546 CVE-2026-64547                      CVE-2026-64548 CVE-2026-64549 CVE-2026-64550 CVE-2026-64551                      CVE-2026-64552 CVE-2026-64553 CVE-2026-64554 CVE-2026-64555                      CVE-2026-64557 CVE-2026-64558 CVE-2026-64559 CVE-2026-64560     Debian Bug     : 1130336

    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.100-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.

  - vsock/virtio: fix zerocopy completion for multi-skb sends When a large message is fragmented into multiple     skbs, the zerocopy uarg is only allocated and attached to the last skb in the loop. Non-final skbs carry     pinned user pages with no completion tracking, so the kernel has no way to notify userspace when those     pages are safe to reuse. If the loop breaks early the uarg is never allocated at all, leaking pinned pages     with no completion notification. Fix this by following the approach used by TCP: allocate the zerocopy     uarg (if not provided by the caller) before the send loop and attach it to every skb via skb_zcopy_set(),     which takes a reference per skb. Each skb's completion properly decrements the refcount, and the     notification only fires after the last skb is freed. On failure, if no data was sent, the uarg is cleanly     aborted via net_zcopy_put_abort(). This issue was initially discovered by sashiko while reviewing commit     1cb36e252211 (vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting) but was pre-existing.
    (CVE-2026-53365)

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

ID	Name	Product	Family	Severity
331409	Debian dsa-6405 : ata-modules-6.12.100+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	medium
326564	Linux Distros Unpatched Vulnerability : CVE-2026-53365	Nessus	Misc.	medium
322087	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1881)	Nessus	Amazon Linux Local Security Checks	medium

Detections

Analytics

CVE-2026-53365

medium

Tenable Plugins

medium

medium

medium