Potential Memory Leak while Running Fuzz Test with L2CAP Connection, Configuration and Disconnection Packets

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • SimpleLink Lowpower SDK F3 BLE5 Stack
    • BLE_LOKI-3209
    • Hide
      BLE_LOKI_9_10_00_RC17
      BLE_LOKI_9_10_00
      Show
      BLE_LOKI_9_10_00_RC17 BLE_LOKI_9_10_00
    • Hide
      BLE_LOKI_9_14_00
      BLE_LOKI_9_14_00_RC5
      Show
      BLE_LOKI_9_14_00 BLE_LOKI_9_14_00_RC5
    • Hide
      CC23XX
      CC27XX
      Show
      CC23XX CC27XX
    • Free the pointer in LL that might hold uncompleted packet to L2CAP

      Description: Running fuzz tests with BLE L2CAP connection creation and disconnection robustness using LE Credit-Based Flow Control mode. When anomalies are introduced via fuzz testing, such as an extra connection request, extra connection response, extra configuration request, extra configuration response, extra disconnection request, extra disconnection response, a potential memory leak is observed.

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

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-5498 - Potential Memory Leak while Running...
                SYNCHRONIZED
                • Last Sync Date: