Possible use of unitialized socked address

[serhiy-storchaka]

Bug report

New Bluetooth tests added in #132023 fail on Fedora based platforms. It looks that the hci_channel member of the sockaddr_hci structure is not initialized. This may be a cause of the failure.

On NetBSD and DragonFly sockaddr_hci is an alias of sockaddr_bt which contain other fields. This also may be an issue.

If sockaddr_hci contains additional optional members, not initializing them with zeros also may cause troubles.

It is safer to always initialize sockaddr_hci and all other sockaddr_* structures with zeroes.

Linked PRs

• gh-132075: Fix possible use of sockaddr structures with uninitialized members #132076
• [3.13] gh-132075: Fix possible use of sockaddr structures with uninitialized members (GH-132076) #132086
• [3.12] gh-132075: Fix possible use of sockaddr structures with uninitialized members (GH-132076) #132087