The changes to the instructions performed by TLS relaxation and the errata patching are performed with relocations. As these are applied so late the errata scanning won't see the changes in the section data made by the TLS relaxation. This can lead to a TLS relaxed sequence being patched when it doesn't need to be.
The fix checks to see if there is a R_RELAX_TLS_IE_TO_LE instruction at the same address as the ADRP as this indicates the presence of a relaxation of a sequence that might get recognised as a patch. None of the other TLS code sequences that can be relaxed by LLD will match the erratum so I've not tested for them.
This fix was inspired by a recently reported GNU ld assertion failure https://sourceware.org/bugzilla/show_bug.cgi?id=23904 . I don't think that LLD's errata scanner will match any of the TLS code sequences in that PR as LLD checks that the 2nd instruction doesn't write to the destination register of the ADRP and ld.bfd does not. However as the fix is simple I've made the change to be safe.