# CVE-2026-31431 - Copy Fail - Linux kernel crypto vulnerability

**URL:** <https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375>\
**Category:** Rocky Linux Help & Support\
**Created:** [April 30, 2026, 3:06am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375 "2026-04-30T03:06:49Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![bolind](https://avatars.discourse-cdn.com/v4/letter/b/f04885/32.png) [@bolind](https://forums.rockylinux.org/u/bolind)\
**Post date:** [May 4, 2026, 11:21am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/41 "2026-05-04T11:21:20Z")

</div>

Where do you have this table from?

---

<div class="post-metadata">

**Author:** ![henri9813](https://avatars.discourse-cdn.com/v4/letter/h/e36b37/32.png) [@henri9813](https://forums.rockylinux.org/u/henri9813)\
**Post date:** [May 4, 2026, 11:32am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/42 "2026-05-04T11:32:02Z")

</div>

From there [Mitigating CVE-2026-31431 on Rocky Linux 8, 9, 10, and LTS Variants | CIQ Knowledge Base](https://kb.ciq.com/article/rocky-linux/rl-cve-2026-31431-mitigation)

---

<div class="post-metadata">

**Author:** ![mneveu](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mneveu](https://forums.rockylinux.org/u/mneveu)\
**Post date:** [May 4, 2026, 11:38am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/43 "2026-05-04T11:38:57Z")

</div>

I think these repos needs CIQ subscription.

It is not yet on official rocky linux repositories

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [May 4, 2026, 11:40am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/44 "2026-05-04T11:40:28Z")

</div>

> [@thomasafine](#):
>
> Is there a way to audit systems to see if the exploit has been run?

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”

---

<div class="post-metadata">

**Author:** ![bolind](https://avatars.discourse-cdn.com/v4/letter/b/f04885/32.png) [@bolind](https://forums.rockylinux.org/u/bolind)\
**Post date:** [May 4, 2026, 11:46am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/45 "2026-05-04T11:46:24Z")

</div>

I think you’re right.

---

<div class="post-metadata">

**Author:** ![thomasafine](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/thomasafine/32/6100_2.png) [@thomasafine](https://forums.rockylinux.org/u/thomasafine)\
**Post date:** [May 4, 2026, 11:52am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/46 "2026-05-04T11:52:42Z")

</div>

> [@jlehtone](#):
>
> 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”

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:

```auto
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.

---

<div class="post-metadata">

**Author:** ![bishoptf](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@bishoptf](https://forums.rockylinux.org/u/bishoptf)\
**Post date:** [May 4, 2026, 12:20pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/47 "2026-05-04T12:20:03Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![Tasslehoff](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@Tasslehoff](https://forums.rockylinux.org/u/Tasslehoff)\
**Post date:** [May 4, 2026, 1:14pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/48 "2026-05-04T13:14:57Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![camaronh](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@camaronh](https://forums.rockylinux.org/u/camaronh)\
**Post date:** [May 4, 2026, 6:52pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/49 "2026-05-04T18:52:37Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![StatiC](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@StatiC](https://forums.rockylinux.org/u/StatiC)\
**Post date:** [May 4, 2026, 7:13pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/50 "2026-05-04T19:13:51Z")

</div>

It does not. That was released on 4/25 and doesn’t list the new CVE.

> **[Rocky Enterprise Software Foundation Product Errata](https://errata.rockylinux.org/RLSA-2026:9131)**

---

<div class="post-metadata">

**Author:** ![FrankCox](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/frankcox/32/1572_2.png) [@FrankCox](https://forums.rockylinux.org/u/FrankCox)\
**Post date:** [May 4, 2026, 7:13pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/51 "2026-05-04T19:13:56Z")

</div>

From the website posted above:

```auto
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.

---

<div class="post-metadata">

**Author:** ![camaronh](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@camaronh](https://forums.rockylinux.org/u/camaronh)\
**Post date:** [May 4, 2026, 7:44pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/52 "2026-05-04T19:44:44Z")

</div>

Thanks for the info.  
Does anyone know if there’s any news about a patch for Rocky Linux 8.10? Or how to proceed?

---

<div class="post-metadata">

**Author:** ![StatiC](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@StatiC](https://forums.rockylinux.org/u/StatiC)\
**Post date:** [May 4, 2026, 9:41pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/53 "2026-05-04T21:41:46Z")

</div>

It looks like Red Hat is releasing fixes so hopefully it won’t be long now.

[https://access.redhat.com/errata/RHSA-2026:13565](https://access.redhat.com/errata/RHSA-2026:13565)

---

<div class="post-metadata">

**Author:** ![stone](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@stone](https://forums.rockylinux.org/u/stone)\
**Post date:** [May 4, 2026, 10:15pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/54 "2026-05-04T22:15:25Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [May 5, 2026, 4:42am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/55 "2026-05-05T04:42:07Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![filuur](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/filuur/32/6106_2.png) [@filuur](https://forums.rockylinux.org/u/filuur)\
**Post date:** [May 5, 2026, 7:36am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/56 "2026-05-05T07:36:01Z")

</div>

Redhat has flagged RHEL 8-10 as “Fixed” now, so shouldn’t be that long until it flows down to Rocky

> **[cve-details](https://access.redhat.com/security/cve/cve-2026-31431)**

Edit: Bugzilla is updated now with links to the specific fixes

> **[2460538 – (CVE-2026-31431) CVE-2026-31431 kernel: crypto: algif\_aead - Revert...](https://bugzilla.redhat.com/show_bug.cgi?id=2460538)**

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [May 5, 2026, 7:50am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/57 "2026-05-05T07:50:48Z")

</div>

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!](https://forums.rockylinux.org/t/rocky-linux-needs-your-input-regarding-urgent-security-updates/20389) as your input will help shape this.

---

<div class="post-metadata">

**Author:** ![frank.wettstein](https://avatars.discourse-cdn.com/v4/letter/f/bb73d2/32.png) [@frank.wettstein](https://forums.rockylinux.org/u/frank.wettstein)\
**Post date:** [May 5, 2026, 9:46am UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/58 "2026-05-05T09:46:58Z")

</div>

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](https://forums.rockylinux.org/t/rocky-linux-needs-your-input-regarding-urgent-security-updates/20389))

---

<div class="post-metadata">

**Author:** ![TheWitness](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/thewitness/32/2332_2.png) [@TheWitness](https://forums.rockylinux.org/u/TheWitness)\
**Post date:** [May 5, 2026, 2:09pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/59 "2026-05-05T14:09:47Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![mashcraft](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@mashcraft](https://forums.rockylinux.org/u/mashcraft)\
**Post date:** [May 5, 2026, 7:37pm UTC](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375/60 "2026-05-05T19:37:33Z")

</div>

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.

[Previous page](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375.md?page=2)

[Next page](https://forums.rockylinux.org/t/cve-2026-31431-copy-fail-linux-kernel-crypto-vulnerability/20375.md?page=4)
