Preventing Instrumentation of BP Hardening Callbacks in arm64
Summary
GSD-2022-1001893: arm64: prevent instrumentation of bp hardening callbacks. Affects Kernel versions >= ec82b567a74fbdffdf418d4bb381d55f6a9096af, < d362998e8df9ada2e9e1b5f5f154959df287402d. 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 Linux Kernel is an open-source software that serves as the core of the Linux operating system. It provides essential functionality and interfaces for various hardware devices and software components. The arm64 architecture is a widely used processor architecture for mobile devices, embedded systems, and server platforms. It is vulnerable to a specific issue related to the instrumentation of BP (Branch Prediction) hardening callbacks.
Vulnerability Detail
The vulnerability in arm64 architecture allows for the instrumentation of BP hardening callbacks. This means that an attacker could potentially manipulate the behavior of the branch predictor, leading to speculative execution of malicious code. The impact and attack plausibility of this vulnerability have not been proven yet, but it poses a potential security risk. The vulnerability was introduced in Linux Kernel version v4.16 and has been fixed in version v5.15.33.
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 arm64 architecture that allows for the instrumentation of BP hardening callbacks has been identified and fixed in Linux Kernel version v5.15.33. It is important to update the Linux Kernel to the latest version to ensure the security and integrity of the system. 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 is not yet proven, but it has the potential to allow attackers to manipulate the branch predictor and execute malicious code.
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 to the playground and it will alert you in real-time for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the moment. However, it is important to apply the recommended fix to mitigate any potential risks.
The remote exploitability of this vulnerability is not yet determined. Further analysis and testing are required to assess the actual risk.
There are no reported incidents related to this vulnerability at the moment. However, it is always recommended to stay updated with the latest security patches and fixes.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
