BLE Does not Schedule any Activity After Incorrect Reason Code for Link Termination Packet

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Urgent
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-3905
    • BLE_LOKI_9_11_01
    • Hide
      BLE_LOKI_9_14_02
      BLE_LOKI_9_14_02_RC3
      Show
      BLE_LOKI_9_14_02 BLE_LOKI_9_14_02_RC3
    • CC27xx

      Description: BLE chip becomes unresponsive after continuous GATT write flooding attack during cybersecurity testing. After approximately 10 minutes of continuous GATT write attempts, the BLE stack enters a stuck state where advertising stops and new connections cannot be established. Recovery requires a Power-On Reset (POR). The stack should remain responsive during continuous GATT write attempts. Expected behavior is the device should disconnect, device should then continue advertising, and device remains responsive to new connections. Fuzz tester sends 0xFE for connection termination. This code is used for successfully terminating connection handover in the stack as well. Added a flag to indicate if connection handover was active, to properly interpret the incoming 0xFE code.

       

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-6409 - BLE Does not Schedule any Activity ...
                SYNCHRONIZED
                • Last Sync Date: