Unregister Virtual Clocks in ptp Package
Summary
GSD-2022-1001861: ptp: unregister virtual clocks when unregistering physical clock. Affects Kernel versions >= 73f37068d540eba5f93ba3a0019bf479d35ebd76, < b2dea2a696d09163da4cd33cb598ce1f73e86597. 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 functionality for Precision Time Protocol (PTP) synchronization, which is used for accurate timekeeping in computer systems. The package includes both physical and virtual clocks, with virtual clocks being dependent on the physical clock. This vulnerability relates to the unregistering of virtual clocks when unregistering the physical clock.
Vulnerability Detail
The vulnerability in the ptp package occurs when virtual clocks are not properly unregistered during the process of unregistering the physical clock. This can lead to resource leaks and potential security issues. Attackers may be able to exploit this vulnerability to gain unauthorized access, manipulate time-sensitive operations, or disrupt system functionality. The vulnerability was introduced in version v5.14 of the Linux Kernel and was fixed in version v5.15.33.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.15.33 or later. This update includes the necessary commit (b2dea2a696d09163da4cd33cb598ce1f73e86597) that addresses the issue. Updating the Kernel will ensure that virtual clocks are properly unregistered when unregistering the physical clock.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the ptp package, which relates to the improper unregistering of virtual clocks when unregistering the physical clock, can lead to resource leaks and potential security issues. It is recommended to update the Linux Kernel to version v5.15.33 or later to fix 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 security issues. Attackers may be able to gain unauthorized access, manipulate time-sensitive operations, or disrupt system functionality.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for open-source vulnerabilities, including this one.
Yes, a patch is available in version v5.15.33 of the Linux Kernel. Updating to this version will fix the vulnerability.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the patch as soon as possible to mitigate any potential risks.
The exact attack vector for this vulnerability is not specified. However, if an attacker gains access to the system, they may be able to exploit this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.