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

  - Bluetooth: ISO: zero the sockaddr before returning it in getname iso_sock_getname() fills a struct     sockaddr_iso in place and returns its size without clearing it first, so bytes it does not write are     copied to user space from the kernel stack. The getsockname(2) and getpeername(2) paths both run through     do_getsockname(), which hands getname() an uninitialized sockaddr_storage on the stack and copies back up     to the number of bytes getname() returns, so the driver has to initialize every byte it accounts for. Two     ranges are left uninitialized: - struct sockaddr_iso is 10 bytes but only 9 are written (family,     iso_bdaddr, iso_bdaddr_type), leaking the trailing pad byte on every call. - for a broadcast peer     (BIS_LINK or PA_LINK) the returned length grows by sizeof(struct sockaddr_iso_bc), but only bc_sid,     bc_num_bis and bc_bis are filled; bc_bdaddr and bc_bdaddr_type, the first 7 bytes of that structure, are     never written. An unprivileged process can open a BTPROTO_ISO socket and reach the pad leak with     getsockname(); the broadcast leak needs an established BIS/PA connection. l2cap and rfcomm already memset     their sockaddr in getname for the same reason; do the same here. (CVE-2026-80761)

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

ID	Name	Product	Family	Published	Updated	Severity
376443	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel vulnerabilities (USN-8959-1)	Nessus	Ubuntu Local Security Checks	11/5/2026	11/5/2026	high
342982	Linux Distros Unpatched Vulnerability : CVE-2026-80761	Nessus	Misc.	9/4/2026	11/6/2026	low

Detections

Analytics

Plugins Search

high

low