[Bug 219458] bluetooth connection fails after L2CAP: Fix uaf in l2cap_connect patch

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=219458

--- Comment #4 from Giuseppe Ghibò (ghibo@mageia.org) ---
btmon output added. As you can see in the working case the behaviour diverges
from packet #16 (in the first case, working) and after packet #94 in the "not
working" case, both calls ACL Data RX with L2CAP: Information Request:, but in
the working case it's followed by HCI Event: Read Remote... and other commands,
while in the not working case it's immediately followed by "MGMT Event: Device
Connected", like if something was truncated.

[working]
> ACL Data RX: Handle 256 flags 0x02 dlen 10              #16 [hci0] 413.700565
      L2CAP: Information Request (0x0a) ident 1 len 2
        Type: Extended features supported (0x0002)
> HCI Event: Read Remote Extended Featu.. (0x23) plen 13  #17 [hci0] 413.700588


[not working]
> ACL Data RX: Handle 256 flags 0x02 dlen 10               #94 [hci0] 20.205711
      L2CAP: Information Request (0x0a) ident 7 len 2
        Type: Extended features supported (0x0002)
@ MGMT Event: Device Connected (0x000b) plen 13       {0x0001} [hci0] 20.205764
        BR/EDR Address: AA:BB:CC:DD:EE:FF (Company)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.