Unregister Virtual Clocks in ptp Package
Summary
GSD-2022-1001549: ptp: unregister virtual clocks when unregistering physical clock. Affects Kernel versions >= 73f37068d540eba5f93ba3a0019bf479d35ebd76, < 9c796a57cbb5daf124a665689f0b2bc9262e0ced. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The ptp package is a part of the Linux Kernel ecosystem. It provides support for the Precision Time Protocol (PTP), which is used for clock synchronization in networked systems. The package includes both physical and virtual clocks, with virtual clocks being registered alongside physical clocks. However, a vulnerability has been discovered where virtual clocks are not properly unregistered when the corresponding physical clock is unregistered.
Vulnerability Detail
The vulnerability in the ptp package allows for the improper handling of virtual clocks when unregistering a physical clock. This can lead to resource leaks and potential memory corruption. An attacker may be able to exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges. The vulnerability was introduced in version v5.14 of the Linux Kernel and has been fixed in version v5.16.19.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no known workaround for this vulnerability. It is necessary to update the Linux Kernel to the fixed version.
Conclusion
The vulnerability in the ptp package, which allows for the improper handling of virtual clocks when unregistering a physical clock, can lead to resource leaks and potential memory corruption. It is crucial to update the Linux Kernel to version v5.16.19 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource leaks and potential memory corruption. An attacker may be able to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to update to the fixed version of the Linux Kernel to mitigate any potential risks.
To exploit this vulnerability, an attacker would need to have access to a system running the affected version of the Linux Kernel and the ability to execute arbitrary code.
There are no known reports of this vulnerability being actively exploited in the wild. However, it is still important to update to the fixed version of the Linux Kernel to ensure system security.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
