Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use correct size for hci_filter type #384

Closed
wants to merge 1 commit into from

Conversation

sooda
Copy link

@sooda sooda commented May 11, 2024

This is for tag 0.5.5, not the master branch, but github doesn't let me create a PR with the tag as a base. Anyway... My proposed fix for issue 383.

Use 16 bytes for the filter structure in set_socket_filter(), not 14.

struct hci_filter unfortunately is not a packed struct:

https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/lib/hci.h

Hence, it has two bytes of padding at the end for correct stride of the 32-bit members.

This used to not be a problem until Linux kernel commit b2186061d6043 (Bluetooth: hci_sock: Fix not validating setsockopt user input) changed the behaviour of HCI_FILTER sockopt; before, the kernel would have truncated the read size but now the data supplied has to be at least the struct size, or we'd get -EINVAL.

Use 16 bytes for the filter structure in set_socket_filter(), not 14.

struct hci_filter unfortunately is not a packed struct:

    https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/lib/hci.h

Hence, it has two bytes of padding at the end for correct stride of the
32-bit members.

This used to not be a problem until Linux kernel commit b2186061d6043
(Bluetooth: hci_sock: Fix not validating setsockopt user input) changed
the behaviour of HCI_FILTER sockopt; before, the kernel would have
truncated the read size but now the data supplied has to be at least the
struct size, or we'd get -EINVAL.
@qdot
Copy link
Contributor

qdot commented May 11, 2024

That's not a version we're maintaining anymore, so I guess I'll let this hang out but I have nowhere to merge it.

@qdot qdot closed this Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants