CVE-2024-27022: fork: defer linking file vma until vma is fully initialized
fork: defer linking file vma until vma is fully initialized
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.8.8 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.9 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.90-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.8.9-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.134 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.8.8 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-27022?
CVE-2024-27022 is classified as a high severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-27022?
To fix CVE-2024-27022, update the kernel to the recommended versions specified in the vendor advisories.
Which versions of the Linux kernel are affected by CVE-2024-27022?
CVE-2024-27022 affects kernel versions before 6.8.8 and specific versions of the 5.10.x and 6.1.x branches.
Is there a workaround for CVE-2024-27022?
Currently, the recommended approach is to apply updates rather than relying on workarounds for CVE-2024-27022.
What systems are impacted by CVE-2024-27022?
CVE-2024-27022 impacts systems running affected versions of the Linux kernel distributed by Red Hat and Debian.