Is Circular Class References Bad?

I cant find any certain topic about it online, im mostly using languages with gc and im so oftenly having circular class references when im working with OOP. As some examples; - A class constructs B and holds B also B holds A - Character class constructs EntityMovementHandler and holds it also EntityMovementHandler holds Character class in here to make it more loose coupled if i create Entity interface there is still will be circular class refer