There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing barriers when
    accessing stream->subrequests locklessly The list of subrequests attached to stream->subrequests is
    accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they
    access subreq->flags without taking a barrier after getting the subreq pointer from the list. Relatedly,
    the functions that build the list don't use any sort of write barrier when constructing the list to make
    sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by:
    (1) Add a new list_add_tail_release() function that uses a release barrier to set the pointer to the new
    member of the list. (2) Add a new list_first_entry_or_null_acquire() function that uses an acquire barrier
    to read the pointer to the first member in a list (or return NULL). (3) Use list_add_tail_release() when
    adding a subreq to ->subrequests. (4) Use list_first_entry_or_null_acquire() when initially accessing the
    front of the list (when an item is removed, the pointer to the new front iterm is obtained under the same
    lock). (CVE-2026-64067)

An update of the linux package has been released.

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

  - netfs: Fix missing barriers when accessing stream->subrequests locklessly The list of subrequests attached     to stream->subrequests is accessed without locks by netfs_collect_read_results() and     netfs_collect_write_results(), and then they access subreq->flags without taking a barrier after getting     the subreq pointer from the list. Relatedly, the functions that build the list don't use any sort of write     barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be     set first if no lock is taken. Fix this by: (1) Add a new list_add_tail_release() function that uses a     release barrier to set the pointer to the new member of the list. (2) Add a new     list_first_entry_or_null_acquire() function that uses an acquire barrier to read the pointer to the first     member in a list (or return NULL). (3) Use list_add_tail_release() when adding a subreq to ->subrequests.
    (4) Use list_first_entry_or_null_acquire() when initially accessing the front of the list (when an item is     removed, the pointer to the new front iterm is obtained under the same lock). (CVE-2026-64067)

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

ID	Name	Product	Family	Published	Updated	Severity
472563	Chainguard: linux-qemu-melange: security update to 6.18.49-r2	Tenable Cloud Security	Chainguard Local Security Checks	10/3/2026	10/13/2026	critical
472563	Chainguard: linux-qemu-melange: security update to 6.18.49-r2	Tenable Self-Hosted Container Security	Chainguard Local Security Checks	10/3/2026	10/13/2026	critical
339767	Photon OS 5.0: Linux PHSA-2026-5.0-92-0973	Nessus	PhotonOS Local Security Checks	8/26/2026	8/26/2026	critical
343532	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8728-1)	Nessus	Ubuntu Local Security Checks	9/7/2026	9/24/2026	high
327925	Linux Distros Unpatched Vulnerability : CVE-2026-64067	Nessus	Misc.	7/20/2026	10/6/2026	critical
340681	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel (NVIDIA) vulnerabilities (USN-8663-1)	Nessus	Ubuntu Local Security Checks	8/26/2026	10/14/2026	high
340045	Ubuntu 26.04 LTS : Linux kernel (NVIDIA BaseOS) vulnerabilities (USN-8664-1)	Nessus	Ubuntu Local Security Checks	8/26/2026	9/23/2026	high
339766	Photon OS 5.0: Linux PHSA-2026-5.0-91-0973	Nessus	PhotonOS Local Security Checks	8/26/2026	8/26/2026	critical

Detections

Analytics

Plugins Search

critical

critical

critical

high

critical

high

high

critical