Where do you have this table from?
I think these repos needs CIQ subscription.
It is not yet on official rocky linux repositories
That is, assuming a malevolent party has had privileged access to system â done âproperâ they have updated all tools that you would use to say: âwe are totally intact and nobody was hereâ
I think youâre right.
True. Hereâs hoping the trust weâve granted to our local users doesnât include actual malevolence. But it does likely include the naively curious.
And at least to that end I will answer my own question. Nothing AT ALL is logged in /var/log/secure or /var/log/audit/audit.log. BUT /var/log messages does end up with lines like this:
May 4 07:35:09 REDACTED kernel: alg: No test for authencesn(hmac(sha256),cbc(aes)) (authencesn(hmac(sha256-ni),cbc-aes-aesni))
May 4 07:35:09 REDACTED kernel: process 'su' launched '/bin/sh' with NULL argv: empty string added
Also worth nothing that, after the exploit has run, subsequent uses of âsuâ result in NO logging ANYWHERE.
This is it for me, I inly have a few rhel (rocky) instances left but all my other *nix instances have had new kernels pushed out days ago but not Rocky at least not for me running 8âŚnot sure why or the issue but I will start working on migrating the remaining ones that are left based on this reaponseâŚ
I completely agree, I was also advocating for Rocky in my company to migrate all the old Ubuntu 22 instances, but what my boss see is that Canonical had an instant response with a kmod update and a working temporary remediation, while our Rocky servers are still vulnerable and the temporary remediation do not even work.
This requires an immediate response, the more we wait the more people will move away from Rocky.
Alma Linux released a new patched kernel via test repo, Oracle Linux release a new patched kernel, just saying that other RHEL based distros released a temporary fix.
Hello,
I have Rocky Linux 8.10 Standard, I updated the kernel and reached to version 4.18.0-553.120.1.el8_10.x86_64.
Could someone tell me if this version already has the fix?
It does not. That was released on 4/25 and doesnât list the new CVE.
From the website posted above:
grep CONFIG_CRYPTO_USER_API_AEAD /boot/config-$(uname -r)
If the output is CONFIG_CRYPTO_USER_API_AEAD=y, the vulnerable algorithm family is built directly into the kernel image, not compiled as a loadable module.
Thanks for the info.
Does anyone know if thereâs any news about a patch for Rocky Linux 8.10? Or how to proceed?
It looks like Red Hat is releasing fixes so hopefully it wonât be long now.
RedHat hasnât released a fix yet, and as Rocky is downstream, it wonât have a patch either.
Alma is not downstream (and not 1:1 RHEL) so they can patch as they please.
Well, Rocky has previously released a patched package before RHEL as an interim solution. IIRC, that was for ssh, whose vulnerabilities are more serious as they may be exploited remotely.
Redhat has flagged RHEL 8-10 as âFixedâ now, so shouldnât be that long until it flows down to Rocky
Edit: Bugzilla is updated now with links to the specific fixes
There is a vote for how we can deal with this better in the future - rather than wait for RHEL.
See this vote post: Rocky Linux needs your input regarding urgent security updates! as your input will help shape this.
I agree with that. A company that earns money from its Linux distribution should be quicker to fix a vulnerability of this kind. This particular vulnerability has received quite a lot of public attention, and it is also one of the first to have been discovered with the help of AI.
Rocky Linux is closely tied to RHEL through its bug-for-bug compatibility approach, whereas Alpine Linux is free to react more quickly and independently. That said, Rocky Linux is apparently considering alternative approaches for handling urgent security bugs, which I think is a positive development (see https://forums.rockylinux.org/t/rocky-linux-needs-your-input-regarding-urgent-security-updates/20389)
This was what I was looking for. So, basically there is a published workaround for Rocky. I would suspect that everyone has followed this guide by now in the near term.
The reason I chose to use Rocky Linux in the first place is the bug-for-bug compatibility. I knew at that time that RedHat can be slower to release patches and that using Rocky would add some additional time.
While the survey seems to be leaning towards not waiting for RHEL patches. Please keep the focus of Rocky Linux in mind. If you want something different, there are plenty of options out there.
If you want to use Rocky Linux but get patches faster, donât force those on everyone. I for one donât want to be the Alpha/Beta tester for every security patch. If you donât know what I mean, reference the Alma Llinux patch release for this CVE. They published it and asked their users to test it. That is not the role I chose when I selected Rocky Linux. I still test before pushing updates but I donât want to be finding the little things.