CA certificates errors after update to kernel 5.14.0-50.19.1

I use Almalinux 9.6. After (successful) update via dnf to kernel 5.14.0-570.19.1
(3 days ago) dnf check-update started informing about errors with CA certificates:

How can this be related to the kernel version ? And what, can this be fixed by adjusting the kernel configuration?

update-crypto-policies --set LEGACY

  • reboot don’t help.

Is it?
Does this happen only when you run the 5.14.0-570.19.1? (You can still boot with the previous kernel?)
Were it only the kernel packages that did update? (See dnf history)


Those error messages do have “8” in the URLs?
AlmaLinux 8 does use “8”, but URLs of Almalinux 9 should have “9”.

Does this happen only when you run the 5.14.0-570.19.1? (You can still boot with > the previous kernel?)
Were it only the kernel packages that did update? (See dnf history)

This does not seem to be a kernel problem. I checked by booting with the previous kernel version, and the previous version NOW has these problems too. However, its update PREVIOUSLY passed in dnf normally, and this was the last normal update with dnf.

This can be seen from dnf.log (‘dnf history’ showed only total update).
This successful update included kernel, kernel-*, perf, python3-perf. This was performed at June 7, 2025, and on June 8, dnf started giving CA certificates errors.

dnf.log shows that everything is related to Almalinux “9” - I originally installed Almalinux 9 before, I never worked with version 8.

So I don’t understand how anything could have changed in one day.

My both Almalinux 9.6 browsers (Firefox&Chrome) blocking access via https://mirrors.almalinux.org - with messages like
mirrors.almalinux.org normally uses encryption to protect your data. However, the credentials we received from mirrors.almalinux.org now are different from what it normally sends.”

Doesn’t this provide additional information?