m68k: mvme147,mvme16x: Don't wipe PCC timer config bits
Summary
GSD-2021-1000384: m68k: mvme147,mvme16x: Don't wipe PCC timer config bits. Affects Kernel versions >= 7529b90d051e4629884771ba2b1d3a87d2c6a9d7, < 1dfb26df15fc7036a74221d43de7427f74293dae. 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 developed by Motorola. The mvme147 and mvme16x are specific models within this family. These microprocessors are commonly used in embedded systems and industrial applications. The PCC (Processor Configuration Control) timer is a hardware component that provides timing functionality. It is crucial for accurate timekeeping and synchronization in these systems.
Vulnerability Detail
The vulnerability identified in the mvme147 and mvme16x models of the m68k microprocessors involves the wiping of PCC timer configuration bits. This issue can lead to incorrect timer settings, resulting in inaccurate timekeeping and synchronization. An attacker could potentially exploit this vulnerability to manipulate timing-related operations, leading to various security and operational risks in affected systems.
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 specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the mvme147 and mvme16x models of the m68k microprocessors, which involves the wiping of PCC timer configuration bits, can lead to inaccurate timekeeping and synchronization. It is crucial for users to update their Linux Kernel to version v5.10.37 or a later version that includes the fix. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in inaccurate timekeeping and synchronization in systems utilizing the mvme147 and mvme16x models of the m68k microprocessors. This can lead to various security and operational risks.
An attacker could potentially manipulate timing-related operations by exploiting the wiped PCC timer configuration bits, leading to security vulnerabilities and operational disruptions.
Yes, the vulnerability has been fixed in the Linux Kernel version v5.10.37 by commit 1dfb26df15fc7036a74221d43de7427f74293dae. Users should update their Linux Kernel to this version or a later version that includes the fix.
The vulnerability was introduced in version v5.2 of the Linux Kernel by commit 7529b90d051e4629884771ba2b1d3a87d2c6a9d7. Therefore, all versions of the mvme147 and mvme16x models utilizing the affected Linux Kernel versions are potentially vulnerable.
For more details about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
