{"api_version":"1","generated_at":"2026-09-11T16:17:15+00:00","cve":"CVE-2026-80761","urls":{"html":"https://cve.report/CVE-2026-80761","api":"https://cve.report/api/cve/CVE-2026-80761.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80761","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80761"},"summary":{"title":"Bluetooth: ISO: zero the sockaddr before returning it in getname","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: zero the sockaddr before returning it in getname\n\niso_sock_getname() fills a struct sockaddr_iso in place and returns its\nsize without clearing it first, so bytes it does not write are copied to\nuser space from the kernel stack. The getsockname(2) and getpeername(2)\npaths both run through do_getsockname(), which hands getname() an\nuninitialized sockaddr_storage on the stack and copies back up to the\nnumber of bytes getname() returns, so the driver has to initialize every\nbyte it accounts for.\n\nTwo ranges are left uninitialized:\n\n  - struct sockaddr_iso is 10 bytes but only 9 are written (family,\n    iso_bdaddr, iso_bdaddr_type), leaking the trailing pad byte on every\n    call.\n\n  - for a broadcast peer (BIS_LINK or PA_LINK) the returned length grows\n    by sizeof(struct sockaddr_iso_bc), but only bc_sid, bc_num_bis and\n    bc_bis are filled; bc_bdaddr and bc_bdaddr_type, the first 7 bytes of\n    that structure, are never written.\n\nAn unprivileged process can open a BTPROTO_ISO socket and reach the pad\nleak with getsockname(); the broadcast leak needs an established BIS/PA\nconnection. l2cap and rfcomm already memset their sockaddr in getname\nfor the same reason; do the same here.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-04 16:18:01","updated_at":"2026-09-04 16:18:01"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/884cf2cc957da7ac178a0e6c6c69ddfec0481cc8","name":"https://git.kernel.org/stable/c/884cf2cc957da7ac178a0e6c6c69ddfec0481cc8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9069be87c67f290783b332c4284e09fb89cb9ea7","name":"https://git.kernel.org/stable/c/9069be87c67f290783b332c4284e09fb89cb9ea7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1f6d1f2611af0eb36b133a41d29ffd2cc2601615","name":"https://git.kernel.org/stable/c/1f6d1f2611af0eb36b133a41d29ffd2cc2601615","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/190b719b787eb4ca6c25b12fab224806f9108b06","name":"https://git.kernel.org/stable/c/190b719b787eb4ca6c25b12fab224806f9108b06","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80761","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80761","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 1f6d1f2611af0eb36b133a41d29ffd2cc2601615 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 9069be87c67f290783b332c4284e09fb89cb9ea7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 190b719b787eb4ca6c25b12fab224806f9108b06 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ccf74f2390d60a2f9a75ef496d2564abb478f46a 884cf2cc957da7ac178a0e6c6c69ddfec0481cc8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.47 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.11 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.1 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80761","cve":"CVE-2026-80761","epss":"0.001680000","percentile":"0.063450000","score_date":"2026-09-07","updated_at":"2026-09-08 00:05:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/bluetooth/iso.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"1f6d1f2611af0eb36b133a41d29ffd2cc2601615","status":"affected","version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","versionType":"git"},{"lessThan":"9069be87c67f290783b332c4284e09fb89cb9ea7","status":"affected","version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","versionType":"git"},{"lessThan":"190b719b787eb4ca6c25b12fab224806f9108b06","status":"affected","version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","versionType":"git"},{"lessThan":"884cf2cc957da7ac178a0e6c6c69ddfec0481cc8","status":"affected","version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/bluetooth/iso.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.0"},{"lessThan":"6.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.47","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.11","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.1","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.47","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.11","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.1","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: zero the sockaddr before returning it in getname\n\niso_sock_getname() fills a struct sockaddr_iso in place and returns its\nsize without clearing it first, so bytes it does not write are copied to\nuser space from the kernel stack. The getsockname(2) and getpeername(2)\npaths both run through do_getsockname(), which hands getname() an\nuninitialized sockaddr_storage on the stack and copies back up to the\nnumber of bytes getname() returns, so the driver has to initialize every\nbyte it accounts for.\n\nTwo ranges are left uninitialized:\n\n  - struct sockaddr_iso is 10 bytes but only 9 are written (family,\n    iso_bdaddr, iso_bdaddr_type), leaking the trailing pad byte on every\n    call.\n\n  - for a broadcast peer (BIS_LINK or PA_LINK) the returned length grows\n    by sizeof(struct sockaddr_iso_bc), but only bc_sid, bc_num_bis and\n    bc_bis are filled; bc_bdaddr and bc_bdaddr_type, the first 7 bytes of\n    that structure, are never written.\n\nAn unprivileged process can open a BTPROTO_ISO socket and reach the pad\nleak with getsockname(); the broadcast leak needs an established BIS/PA\nconnection. l2cap and rfcomm already memset their sockaddr in getname\nfor the same reason; do the same here."}],"providerMetadata":{"dateUpdated":"2026-09-04T15:12:33.345Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/1f6d1f2611af0eb36b133a41d29ffd2cc2601615"},{"url":"https://git.kernel.org/stable/c/9069be87c67f290783b332c4284e09fb89cb9ea7"},{"url":"https://git.kernel.org/stable/c/190b719b787eb4ca6c25b12fab224806f9108b06"},{"url":"https://git.kernel.org/stable/c/884cf2cc957da7ac178a0e6c6c69ddfec0481cc8"}],"title":"Bluetooth: ISO: zero the sockaddr before returning it in getname","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80761","datePublished":"2026-09-04T15:12:33.345Z","dateReserved":"2026-08-26T14:34:25.791Z","dateUpdated":"2026-09-04T15:12:33.345Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 16:18:01","lastModifiedDate":"2026-09-04 16:18:01","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80761","Ordinal":"1","Title":"Bluetooth: ISO: zero the sockaddr before returning it in getname","CVE":"CVE-2026-80761","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80761","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: zero the sockaddr before returning it in getname\n\niso_sock_getname() fills a struct sockaddr_iso in place and returns its\nsize without clearing it first, so bytes it does not write are copied to\nuser space from the kernel stack. The getsockname(2) and getpeername(2)\npaths both run through do_getsockname(), which hands getname() an\nuninitialized sockaddr_storage on the stack and copies back up to the\nnumber of bytes getname() returns, so the driver has to initialize every\nbyte it accounts for.\n\nTwo ranges are left uninitialized:\n\n  - struct sockaddr_iso is 10 bytes but only 9 are written (family,\n    iso_bdaddr, iso_bdaddr_type), leaking the trailing pad byte on every\n    call.\n\n  - for a broadcast peer (BIS_LINK or PA_LINK) the returned length grows\n    by sizeof(struct sockaddr_iso_bc), but only bc_sid, bc_num_bis and\n    bc_bis are filled; bc_bdaddr and bc_bdaddr_type, the first 7 bytes of\n    that structure, are never written.\n\nAn unprivileged process can open a BTPROTO_ISO socket and reach the pad\nleak with getsockname(); the broadcast leak needs an established BIS/PA\nconnection. l2cap and rfcomm already memset their sockaddr in getname\nfor the same reason; do the same here.","Type":"Description","Title":"Bluetooth: ISO: zero the sockaddr before returning it in getname"}]}}}