In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata maps in the signed loader The loader verifies map->sha against the metadata hash in its instructions. map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now refuses to move on with map->sha validation if the host set it up wrongly.

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: libbpf: Reject non-exclusive metadata
    maps in the signed loader The loader verifies map->sha against the metadata hash in its instructions.
    map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen,
    the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host
    could just omit when loading the loader), another BPF program with map access can mutate the contents
    afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now
    refuses to move on with map->sha validation if the host set it up wrongly. (CVE-2026-80675)

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

  - In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata     maps in the signed loader The loader verifies map->sha against the metadata hash in its instructions.
    map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen,     the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host     could just omit when loading the loader), another BPF program with map access can mutate the contents     afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now     refuses to move on with map->sha validation if the host set it up wrongly. (CVE-2026-80675)

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

ID	Name	Product	Family	Type	Severity
365768	Ubuntu 26.04 LTS : Linux kernel (Azure) vulnerabilities (USN-8888-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365767	Ubuntu 26.04 LTS : Linux kernel vulnerabilities (USN-8887-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365463	Ubuntu 26.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8889-1)	Nessus	Ubuntu Local Security Checks	Local	medium
470655	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.21	Tenable Cloud Security	Google COS Security Checks	Local	high
470655	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.21	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	high
341918	Linux Distros Unpatched Vulnerability : CVE-2026-80675	Nessus	Misc.	Local	high
341880	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-2071)	Nessus	Amazon Linux Local Security Checks	Local	high

Detections

Analytics

CVE-2026-80675

high

Tenable Plugins

medium

medium

medium

high

high

high

high