From: Marcel Holtmann <marcel@holtmann.org>
To: Vladis Dronov <vdronov@redhat.com>
Cc: Balakrishna Godavarthi <bgodavar@codeaurora.org>,
Frederic Danis <frederic.danis@linux.intel.com>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Loic Poulain <loic.poulain@intel.com>,
Suraj Sumangala <suraj@atheros.com>,
syzkaller@googlegroups.com
Subject: Re: [PATCH v3] Bluetooth: hci_uart: check for missing tty operations
Date: Tue, 30 Jul 2019 11:34:11 +0200 [thread overview]
Message-ID: <F6BBC244-B565-4651-9EDD-8C1B8621392F@holtmann.org> (raw)
In-Reply-To: <20190729122215.9948-1-vdronov@redhat.com>
Hi Vladis,
> Certain ttys operations (pty_unix98_ops) lack tiocmget() and tiocmset()
> functions which are called by the certain HCI UART protocols (hci_ath,
> hci_bcm, hci_intel, hci_mrvl, hci_qca) via hci_uart_set_flow_control()
> or directly. This leads to an execution at NULL and can be triggered by
> an unprivileged user. Fix this by adding a helper function and a check
> for the missing tty operations in the protocols code.
>
> This fixes CVE-2019-10207. The Fixes: lines list commits where calls to
> tiocm[gs]et() or hci_uart_set_flow_control() were added to the HCI UART
> protocols.
>
> Link: https://syzkaller.appspot.com/bug?id=1b42faa2848963564a5b1b7f8c837ea7b55ffa50
> Reported-by: syzbot+79337b501d6aa974d0f6@syzkaller.appspotmail.com
> Cc: stable@vger.kernel.org # v2.6.36+
> Fixes: b3190df62861 ("Bluetooth: Support for Atheros AR300x serial chip")
> Fixes: 118612fb9165 ("Bluetooth: hci_bcm: Add suspend/resume PM functions")
> Fixes: ff2895592f0f ("Bluetooth: hci_intel: Add Intel baudrate configuration support")
> Fixes: 162f812f23ba ("Bluetooth: hci_uart: Add Marvell support")
> Fixes: fa9ad876b8e0 ("Bluetooth: hci_qca: Add support for Qualcomm Bluetooth chip wcn3990")
> Signed-off-by: Vladis Dronov <vdronov@redhat.com>
> ---
>
> out-of-commit-message-note:
>
> it is possible that a HCI UART protocol uses serial device's
> operations and not a tty ones. i made hci_uart_has_flow_control() to
> check this also, hence the name. serial device's code checks if
> the needed operations are present itself.
>
> i believe, hci_h5 does not need this check, as it uses serial device
> functions only (as of now):
>
> serdev_device_set_flow_control(h5->hu->serdev, false);
> serdev_device_set_baudrate(h5->hu->serdev, 115200);
>
> drivers/bluetooth/hci_ath.c | 3 +++
> drivers/bluetooth/hci_bcm.c | 3 +++
> drivers/bluetooth/hci_intel.c | 3 +++
> drivers/bluetooth/hci_ldisc.c | 7 +++++++
> drivers/bluetooth/hci_mrvl.c | 3 +++
> drivers/bluetooth/hci_qca.c | 3 +++
> drivers/bluetooth/hci_uart.h | 1 +
> 7 files changed, 23 insertions(+)
I changed the hci_uart_has_flow_control function into using more readable separate checks and then send the patch directly to Linus.
Regards
Marcel
prev parent reply other threads:[~2019-07-30 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 14:26 [PATCH v2] Bluetooth: hci_ldisc: " Vladis Dronov
2019-07-26 21:48 ` Marcel Holtmann
2019-07-29 12:22 ` [PATCH v3] Bluetooth: hci_uart: " Vladis Dronov
2019-07-30 9:34 ` Marcel Holtmann [this message]
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=F6BBC244-B565-4651-9EDD-8C1B8621392F@holtmann.org \
--to=marcel@holtmann.org \
--cc=bgodavar@codeaurora.org \
--cc=frederic.danis@linux.intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@intel.com \
--cc=suraj@atheros.com \
--cc=syzkaller@googlegroups.com \
--cc=vdronov@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®