I encountered the same bug on Ubuntu 22.04.3 LTS, the problem was due to obsolete /etc/apparmor.d/usr.sbin.chronyd.dpkg-dist, making the change as described in the bug description helped.
This system was also upgraded through do-release-upgrade. It might be that some upgrade script is not replacing these profiles with new(er) versions?
I encountered the same bug on Ubuntu 22.04.3 LTS, the problem was due to obsolete /etc/apparmor. d/usr.sbin. chronyd. dpkg-dist, making the change as described in the bug description helped.
This system was also upgraded through do-release-upgrade. It might be that some upgrade script is not replacing these profiles with new(er) versions?