Executive summary
A vulnerability, known as "Copy Fail", has been identified in the Linux kernel's cryptographic interface. A user with a local account could trigger the flaw to gain root privileges, such as that of a system administrator.
This issue has been assigned CVE-2026-31431 and has a severity impact of Important. Configuration settings can be used to further mitigate the impact.
Even though the severity is less than Critical, Red Hat has expedited the release of fixes. Many fixes are available with more coming soon. For the most current information, including a complete list of impacted Red Hat products, please refer to the vulnerability's CVE page.
The copy fail advisory relating to Rocky 8 is resolved by updating the kernel to the release which includes the patches for CVE-31431
Printing the changelog for the kernel to confirm the CVE is patched, confirms that:
kernel-4.18.0-553.120.1.el8_10 is patched
[root@rocky ~]# rpm -q --changelog kernel-4.18.0-553.123.1.el8_10 | grep -i 31431
- crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption (Herbert Xu) [RHEL-172187] {CVE-2026-31431}
- crypto: algif_aead - Revert to operating out-of-place (Herbert Xu) [RHEL-172187] {CVE-2026-31431}
How to Update the Kernel to the Patched Release
The first step is to enable kernel updates in the ScopTEL Packages Manager.
By default kernel updates are disabled to avoid recompiling dahdi/wanpipe drivers each time there is an updated kernel.
This also helps to avoid running out of drive space on the partition by caused by multiple kernel images.
To update the kernel then the Option must be changed to 'Yes' and it is recommended to disable kernel updates after updating the kernel until the next need arises.
Edit the Packages Manager|Packages tab and change the option to Yes
Save
Then it is recommended to use ssh to update the kernel.
scopserv_yum update kernel
Watch closely for any issues and when complete, reboot the Operating System to load the patched kernel.
Confirm your kernel version is updated by printing your installed kernel version:
uname -a
If the version is correct then you can run these commands to check dahdi is properly compiled:
rpm -qa |grep dahdi
dkms status
timertest