Issue: When using GPIOCC26xx_release(), it is assumed that each GPIO entry has a corresponding callback in the callback table. As the GPIO callback table does not need to contain an entry for each entry (as suggested by the comment in the board file), GPIOCC26xx_release also need to take this into consideration to avoid writing out of bounds. This will issue will occur in our current SDK if GPIOCC26xx_release() is used on one of the GPIO indexes that do not have a corresponding callback entry. Solution: Add a check of GPIO index and GPIO callback array size before "removing" a callback from the table.