I suspect that an upgrade since rebooting 25 days ago may be the problem - the one machine I rebooted last night to test a different OS and disk is not doing that after I put the original disk back and rebooted.
Same thing here after I did zypper up on Jul 17 00:11:24 without reboot (was not required):
lost:~ # journalctl -b -u cron.service
-- Logs begin at Thu 2022-05-19 16:21:23 EEST, end at Mon 2022-07-18 12:20:32 EEST. --
Jul 07 14:43:57 lost systemd[1]: Started Command Scheduler.
Jul 07 14:43:57 lost cron[7004]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 91% if used.)
Jul 07 14:43:58 lost cron[7004]: (CRON) INFO (running with inotify support)
Jul 17 00:33:02 lost cron[30104]: *** stack smashing detected ***: terminated
Jul 17 01:33:01 lost cron[10364]: *** stack smashing detected ***: terminated
Jul 17 02:33:01 lost cron[19327]: *** stack smashing detected ***: terminated
…