CVE-2026-80761

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

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 s

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References