CVE-2026-80761: Bluetooth: ISO: zero the sockaddr before returning it in getname
Bluetooth: ISO: zero the sockaddr before returning it in getname
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.47 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.11 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.1.12-1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In the Linux kernel Bluetooth ISO getname path, zero-initialize the sockaddr_iso and sockaddr_iso_bc structures before returning them so all bytes copied by getsockname() or getpeername() are initialized.
Event History
Frequently Asked Questions
Who can trigger the information leak?
An unprivileged local process that can open a BTPROTO_ISO socket can trigger the one-byte padding leak through getsockname(). Leaking the larger broadcast-specific range requires an established BIS or PA connection.
Which interfaces expose the uninitialized data?
Both getsockname(2) and getpeername(2) reach the affected getname() implementation through do_getsockname(). The ordinary socket-address result leaks a trailing padding byte; broadcast peers can expose additional uninitialized broadcast address fields.
How can I determine whether a system may be affected?
Systems using the Linux kernel Bluetooth ISO (BTPROTO_ISO) socket implementation are in scope. The provided data does not include fixed kernel version numbers, so compare the running kernel's source or applied stable patches with the referenced fixes.