CVE-2020-29368: Race Condition
An issue was discovered in splithugepmd in mm/hugememory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
Other sources
An issue was discovered in splithugepmd in mm/hugememory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check.
Reference: https://bugs.chromium.org/p/project-zero/issues/detail?id=2045
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c444eb564fb16645c172d550359cb3d75fe8a040
— Red Hat
An issue was discovered in splithugepmd in mm/hugememory.c in the Linux kernel. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check.
Affected Software
Remediation
Information
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2020-29368?
CVE-2020-29368 has a medium severity rating due to the potential for unintended write access caused by a race condition.
How do I fix CVE-2020-29368?
To fix CVE-2020-29368, upgrade to the kernel versions 4.18.0-348.el8 or newer, or apply the recommended patches.
What systems are affected by CVE-2020-29368?
CVE-2020-29368 affects various versions of the Linux kernel prior to 5.7.5, including specific Red Hat and Debian releases.
Is CVE-2020-29368 exploitable remotely?
CVE-2020-29368 is not inherently exploitable remotely as it requires local access to the affected system for exploitation.
What components are involved in CVE-2020-29368?
CVE-2020-29368 is associated with the copy-on-write mechanism in the Linux kernel's memory management, specifically in the huge memory handling functions.