From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218199] New: Bluetooth: HCI_EV_REMOTE_EXT_FEATURES loss prevents connection abort
Date: Tue, 28 Nov 2023 08:19:20 +0000 [thread overview]
Message-ID: <bug-218199-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218199
Bug ID: 218199
Summary: Bluetooth: HCI_EV_REMOTE_EXT_FEATURES loss prevents
connection abort
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: sy2239101@buaa.edu.cn
Regression: No
Our fuzzing tool finds a possible semantic bug in the Bluetooth system in Linux
6.7-rc2:
When establishing a connection, the loss of HCI_EV_CONN_COMPLETE results in a
connection failure, and the controller sends HCI_EV_DISCONN_COMPLETE to abort
the connection.
Even if HCI_EV_DISCONN_COMPLETE is lost, functions such as hci_conn_timeout
(/net/bluetooth/hci_conn.c: 612), hci_abort_conn (/net/bluetooth/hci_conn.c:
2960), and hci_abort_conn_sync (/net/bluetooth/hci_sync.c: 5379) ensure that
the connection is aborted.
However, in our testing, when both HCI_EV_REMOTE_EXT_FEATURES and
HCI_EV_DISCONN_COMPLETE are lost, it seems that hci_conn_timeout,
hci_abort_conn, and hci_abort_conn_sync are not invoked, leading to the
connection remaining un-aborted.
We are not sure whether this is a semantic bug or an implementation feature in
the Linux kernel. Any feedback would be appreciated, thanks!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-11-28 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 8:19 bugzilla-daemon [this message]
2023-11-28 8:21 ` [Bug 218199] Bluetooth: HCI_EV_REMOTE_EXT_FEATURES loss prevents connection abort bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218199-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.