Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1360802 > unrolled thread

Re: bluetooth: use-after-free in vhci_send_frame

Started byJiri Slaby <jslaby@suse.cz>
First post2016-03-18 18:00 +0100
Last post2016-03-18 18:00 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: bluetooth: use-after-free in vhci_send_frame Jiri Slaby <jslaby@suse.cz> - 2016-03-18 18:00 +0100

#1360802 — Re: bluetooth: use-after-free in vhci_send_frame

FromJiri Slaby <jslaby@suse.cz>
Date2016-03-18 18:00 +0100
SubjectRe: bluetooth: use-after-free in vhci_send_frame
Message-ID<re5UK-2fQ-7@gated-at.bofh.it>
On 03/08/2016, 07:32 PM, Marcel Holtmann wrote:
> that means very little to me actually. So is the real issue caused by opening /dev/vhci or is that theoretical one via some internal kernel compile time feature.

Hi, what do you think about this one?

--- a/drivers/bluetooth/hci_vhci.c
+++ b/drivers/bluetooth/hci_vhci.c
@@ -196,6 +196,11 @@ static inline ssize_t vhci_get_user(stru

                cancel_delayed_work_sync(&data->open_timeout);

+               if (data->hdev) {
+                       kfree_skb(skb);
+                       return -EBADFD;
+               }
+
                opcode = *((__u8 *) skb->data);
                skb_pull(skb, 1);


open_timeout could be in progress (raced with us) and _sync cancel
waited for vhci_create_device to actually finish and create the device
the second time.

thanks,
-- 
js
suse labs

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web