Vulnerability in arm64 Kernel: Fix for Concurrently Setting insn_emulation Sysctls
Summary
GSD-2022-1005903: arm64: fix oops in concurrently setting insn_emulation sysctls. Affects Kernel versions < 353b4673d01c512303c45cf2346f630cda73b5c9. 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 arm64 kernel is a component of the Linux operating system that supports the ARMv8-A architecture. It provides the necessary functionality for running applications on ARM-based devices. The vulnerability in question relates to the concurrent setting of insn_emulation sysctls, which are system control variables used for instruction emulation. These sysctls allow users to enable or disable specific instruction emulation modes. However, a flaw in the arm64 kernel allows for a potential oops (kernel panic) when these sysctls are concurrently set by multiple processes.
Vulnerability Detail
The vulnerability arises due to a race condition in the arm64 kernel's handling of concurrent sysctl updates. When multiple processes attempt to set the insn_emulation sysctls simultaneously, it can lead to inconsistent state changes and trigger an oops. This oops can result in a denial-of-service condition or potentially be exploited by an attacker to gain elevated privileges or execute arbitrary code. The impact and attack plausibility of this vulnerability have not been proven yet.
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
No specific workaround has been mentioned for this vulnerability.
Conclusion
The vulnerability in the arm64 kernel related to concurrently setting insn_emulation sysctls can lead to a denial-of-service condition or potential privilege escalation. It is crucial to update the Linux Kernel to version v5.10.137 or a later release to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a denial-of-service condition to potential privilege escalation or arbitrary code execution.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
No known exploit has been reported for this vulnerability at the time of this report.
The recommended mitigation is to update the Linux Kernel to version v5.10.137 or a later release that includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD-2022-1005903 entry of the GSD database maintained by the Cloud Security Alliance. The link to the specific entry is provided in the references section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
