CVE-2020-10690: Use After Free
Last updated 14 August 2026
Other sources
There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptpclock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.
There is a use-after-free problem seen due to a race condition between the release of ptpclock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.
There was a use-after-free problem seen due to a race condition between the release of ptpclock and cdev at the time of resource deallocation.
When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed (a potential privilege escalation) by the user with administrator privilege, it can cause a denial of service (DoS) problem as the process wakes up to terminate and cleanup all attached files/resources.
The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.
Refer: https://lore.kernel.org/linux-fsdevel/20191125125342.6189-1-vdronov@redhat.com/T/#u
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/kernel-rtto a version that resolves this vulnerability.Fixed in 0:3.10.0-1160.rt56.1131.el7 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 0:3.10.0-1160.el7 - Upgrade
Upgrade
redhat/kernel-rtto a version that resolves this vulnerability.Fixed in 0:4.18.0-193.rt13.51.el8 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 0:4.18.0-193.el8 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 5.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.8-1Fixed in 7.1.8-2
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2020-10690?
CVE-2020-10690 has a high severity rating due to the potential for exploitation by privileged processes.
How do I fix CVE-2020-10690?
To fix CVE-2020-10690, upgrade to kernel versions 5.5 or higher, or the specific kernel packages mentioned in the vulnerability report.
Which software versions are affected by CVE-2020-10690?
CVE-2020-10690 affects specific versions of the Linux kernel prior to 5.5 and various Red Hat and Debian kernel packages.
What systems are impacted by CVE-2020-10690?
CVE-2020-10690 impacts Linux systems running vulnerable versions of the kernel, particularly Red Hat Enterprise Linux and Debian distributions.
Is a workaround available for CVE-2020-10690?
There is no confirmed workaround for CVE-2020-10690; the recommended action is to apply the available updates.