No, the Anbox thing is the only failed unit. The rest of the output is unrelated to that.
If you want to chase down these errors and clean up your log a bit, do a web search for the journal message and try to figure out what it means. For example:
The very first result in a search query leads me to this thread, which provides an explanation and an additional thread you can follow for updates if you wish:
These kernel messages should be treated as warning, not error. You should not remove blacklisted hashes (i.e. do not clear secure boot keys), this is a security measure to protect against malicious signatures. These kernel messages now show because we hardened this security mechanism, and it now reveals issues with some firmwares. There is an ongoing kernel patch to update this error message: https://lore.kernel.org/lkml/3b997266-0 … gikod.net/
If you are no longer using Windows you can delete the secure boot keys and that will clear up the warning messages, but that guy says they are working on a kernel patch that will suppress the messages without deleting anything.
Long story short: the Anbox thing you should take care of as soon as you get a chance (I would just uninstall it/disable the service). The rest is not critical, but if you care and have time it’s worthy of investigation. Probably some of those would be easy to resolve.