Taywooah Looking at the provided vulnerability description, it appears to be a run-of-the-mill use-after-free issue. While yes, it could potentially be an exploit attempt, I'd say it's overwhelmingly likely that the app simply encountered natural conditions that caused it to crash on its own. So I doubt it's related.
And to ease your mind, you should know that given the crash log indicates that the MTE caught the issue and terminated the process instead of allowing it proceed, it wouldn't really even matter if it was an exploit attempt (which it very like wasn't), since the app was killed when the improper access was detected. An attacker can't really exploit the process if it's killed the instance they attempt to do so.
So you can rest assured you're doing all good (in my opinion).