This was also linked in the VirtualBox 7.2.2 change log as one of the issues fixed. I thought I would add it here. Seems to be an on again off again problem dealing with kernel versions and VirtualBox versions. I found the information in this issue thread helpful and informative.