I'm not sure what you're saying here. I can see this being a problem when you have cross-team dependencies and your roll-back requires coordination.

Even then it's manageable if your production deployments are version pinned, it only becomes a problem if schemas in your database or messaging have had non compatible changes and data has been written (i.e you have binary and data dependencies in a release)

All this being said with the assumption that the CI/CD pipeline has been designed to best practices.