ARM: 9170/1: fix panic when kasan and kprobe are enabled in Kernel
Summary
GSD-2022-1000257: ARM: 9170/1: fix panic when kasan and kprobe are enabled. Affects Kernel versions >= 35aa1df4328340f38edc46f00837f08d33d49f63, < 1515e72aae803fc6b466adf918e71c4e4c9d5b3d. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It manages system resources, facilitates communication between processes, and ensures security and stability. The vulnerability in question affects the ARM architecture in the Kernel. Specifically, when both the Kernel Address Sanitizer (KASAN) and Kernel Probes (Kprobes) are enabled, a panic condition can occur, leading to a system crash. KASAN is a dynamic memory error detector, while Kprobes allows developers to insert breakpoints and execute code at specific locations in the Kernel.
Vulnerability Detail
The vulnerability arises from a panic condition triggered when KASAN and Kprobes are simultaneously enabled. This can be exploited by an attacker to crash the system, potentially leading to a denial-of-service (DoS) scenario. The exact attack vectors and impact of this vulnerability have not been proven yet. The vulnerability was introduced in version v2.6.25 of the Linux Kernel and has been fixed in version v5.15.19 by commit 1515e72aae803fc6b466adf918e71c4e4c9d5b3d.
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 ARM vulnerability in the Kernel, which causes a panic condition when KASAN and Kprobes are enabled, has been addressed in version v5.15.19 of the Linux Kernel. Users are advised to update their Kernel to the latest version to mitigate the risk of a system crash. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can potentially lead to a system crash, resulting in a denial-of-service (DoS) scenario.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and Vulert will analyze it in real-time.
At the time of this report, there is no known exploit for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate potential risks.
The exact attack vectors and potential for remote exploitation have not been proven yet. However, it is important to keep the system up to date with the latest security patches to minimize the risk of any potential remote attacks.
The primary mitigation for this vulnerability is to update the Linux Kernel to version v5.15.19 or later. Additionally, following security best practices, such as restricting access to privileged accounts and implementing network security measures, can help reduce the overall attack surface.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
