Can someone explain what changes triggered the latest update in this bug which was initially released in February and updated on May 21s and 24, 2016. We upgraded our ASA codes to 9.1.6(11) because that seemed to be the most stable at the time. Based on the fixed releases, it appears we are still safe but would appreciate a confirmation and a more detailed reason for the update released on this bug.
