> it seems plausible to hit by mistake

The report seems to claim the opposite:

> Looking at the bug itself, it is also very likely that this unsoundness has not caused memory unsafety by accident. While it looks easy to trigger, to exploit this you need an intentionally malicious Drop implementation.

This edit is newer than my comment (and its writer is an experienced T-types member, so I take back my words).