Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 6619] Wrong bluetooth PSM detected when parse the L2CAP pa

Date: Mon, 28 Nov 2011 15:14:12 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6619

Michal Labedzki <michal.labedzki@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.labedzki@xxxxxxxxx

--- Comment #2 from Michal Labedzki <michal.labedzki@xxxxxxxxx> 2011-11-28 15:14:11 PST ---
After initial investigation seems that this is problem with reusing L2CAP CIDs.
Check results for "btl2cap.cmd_code=="Connection Request"". There are:
--
SDP SCID 0x40
SDP SCID 0x40 (first resusing)
AVDTP SCID 0x40 (last reusing)
AVCTP-Control SCID 0x41
SDP SCID 0x42
--

This is issue related to "cid_to_psm_table" and se_tree_insert32(table, cid)
and se_tree_lookup32(table, cid); which are not enought to correct identify
item in "cid_to_psm_table".

Propose solution:
add field "start_frame_number" and "end_frame_number" into "psm_data_t" and
check frame number on each se_tree_lookup32(). "end_frame_number" equals 0
means there is no "Disconnect" on specified CID, so psm_data is still valid.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.