m68k: mvme147,mvme16x: Don't wipe PCC timer config bits
Summary
GSD-2021-1000433: m68k: mvme147,mvme16x: Don't wipe PCC timer config bits. Affects Kernel versions >= 7529b90d051e4629884771ba2b1d3a87d2c6a9d7, < f6a90818a32058fca62cda3a2027a6a2364e1878. 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 m68k is a family of 16/32-bit microprocessors that were used in various systems, including the mvme147 and mvme16x. These systems utilize the m68k architecture and are part of the Linux Kernel ecosystem. The PCC (Processor Configuration Control) timer is a feature of these systems that allows for precise timing and synchronization. However, a vulnerability exists in the code that handles the PCC timer configuration, which can lead to unintended consequences.
Vulnerability Detail
The vulnerability in the mvme147 and mvme16x systems arises from a code implementation issue. Specifically, when configuring the PCC timer, certain bits related to the timer's configuration are inadvertently wiped, resulting in incorrect behavior. This can potentially lead to timing inaccuracies, synchronization problems, or other issues that rely on the proper functioning of the PCC timer. The impact and attack plausibility of this vulnerability have not been proven, but it is important to address it to ensure the correct operation of these systems.
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.4.119 or later. This update includes a commit (f6a90818a32058fca62cda3a2027a6a2364e1878) that addresses the issue. By applying this update, the code responsible for configuring the PCC timer in the mvme147 and mvme16x systems will no longer inadvertently wipe the necessary bits, ensuring proper functionality.
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 mvme147 and mvme16x systems, utilizing the m68k architecture, are affected by a vulnerability that can lead to unintended consequences when configuring the PCC timer. To address this issue, it is recommended to update the Linux Kernel to version v5.4.119 or later, which includes the necessary fix. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the specific use case and reliance on the PCC timer. It could potentially lead to timing inaccuracies, synchronization problems, or other issues that rely on the proper functioning of the timer.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
As of now, there is no known exploit for this vulnerability. However, it is still important to address it by applying the recommended update to ensure the correct operation of the mvme147 and mvme16x systems.
The recommended approach to mitigate this vulnerability is to update the Linux Kernel to the fixed version. While there may be alternative approaches or patches available, they may not provide the same level of assurance as the official update.
You can find more information about this vulnerability, including its fix and the specific commits in the Linux Kernel, in the vulnerability database maintained by the Cloud Security Alliance. The source link is provided in the database_specific field of the vulnerability details.
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.