We are encountering this bug and are able to reproduce, and if we were in production with this device we would have been taken fully down.  The claim in the BST says version 8.4(9) (and presumably the later 8.4(10)) contains the fix.  Rest assured it...