CVE-2022-39188: Race Condition
An issue was discovered in include/asm-generic/tlb.h in the Linux kernel before 5.19. Because of a race condition (unmapmappingrange versus munmap), a device driver can free a page while it still has stale TLB entries. This only occurs in situations with VMPFNMAP VMAs.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1 - Upgrade
Upgrade
redhat/Kernelto a version that resolves this vulnerability.Fixed in 5.19 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Fixed in 5.19
Event History
Frequently Asked Questions
What is the severity of CVE-2022-39188?
CVE-2022-39188 has been classified as a high severity vulnerability due to the potential for a device driver to exploit a race condition.
How do I fix CVE-2022-39188?
To fix CVE-2022-39188, upgrade your Linux kernel to version 5.19 or later, or apply the relevant patches available for your distribution.
Which versions of Linux kernel are affected by CVE-2022-39188?
CVE-2022-39188 affects all versions of the Linux kernel prior to 5.19.
What causes the vulnerability CVE-2022-39188?
CVE-2022-39188 is caused by a race condition between unmap_mapping_range and munmap functions in the Linux kernel.
Is CVE-2022-39188 exploitable remotely?
CVE-2022-39188 is not remotely exploitable and typically requires local access to the affected system.