Bluetooth: ISO: zero the sockaddr before returning it in getname
Summary
| CVE | CVE-2026-80761 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-04 16:18:01 UTC |
| Updated | 2026-09-04 16:18:01 UTC |
| 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 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.063450000 (date 2026-09-07)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 1f6d1f2611af0eb36b133a41d29ffd2cc2601615 git | Not specified |
| CNA | Linux | Linux | affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 9069be87c67f290783b332c4284e09fb89cb9ea7 git | Not specified |
| CNA | Linux | Linux | affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 190b719b787eb4ca6c25b12fab224806f9108b06 git | Not specified |
| CNA | Linux | Linux | affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 884cf2cc957da7ac178a0e6c6c69ddfec0481cc8 git | Not specified |
| CNA | Linux | Linux | affected 6.0 | Not specified |
| CNA | Linux | Linux | unaffected 6.0 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.47 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.11 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.1 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/884cf2cc957da7ac178a0e6c6c69ddfec0481cc8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9069be87c67f290783b332c4284e09fb89cb9ea7 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1f6d1f2611af0eb36b133a41d29ffd2cc2601615 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/190b719b787eb4ca6c25b12fab224806f9108b06 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.