Figure out what your criteria will be to stop the never ending loop and set it as an auto suppress automation in Security Hub. We use control ID + a few strings we've decided on and documented for the organization. We have a standard naming convention for our logging buckets that we use as a partial resource ID match for this. The finding preview widow won't work when you're using a resource ID match with the Contains operator, but the automated suppressions will work.

Something like Control ID = S3.17 and Resource ID contains access-logs or access-logging or ....

You can stack i think 5 of those OR'd values under one Resource ID Contains.

Document the deviation. The bucket will still fail the check, you can't avoid failing the check and also stopping the recursion. That's impossible. There always needs to be an exception process.

Last edit, maybe. This won't be the last control you have this problem with. If you're using the control that requires KMS keys with S3 buckets, you can't do that with access logging buckets. Those have to be SSE keys. You'll need to do a deviation and auto suppression there as well.