arm64: extable: fix load_unaligned_zeropad() reg indices in Kernel
Summary
GSD-2022-1000613: arm64: extable: fix load_unaligned_zeropad() reg indices. Affects Kernel versions >= 753b32368705c396000f95f33c3b7018474e33ad, < 47fe7a1c5e3e011eeb4ab79f2d54a794fdd1c3eb. 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 crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The arm64 architecture is specifically designed for 64-bit ARM processors. The load_unaligned_zeropad() function in the Kernel is responsible for loading unaligned data and padding it with zeros. However, a vulnerability has been discovered in the reg indices used by this function.
Vulnerability Detail
The vulnerability in the arm64 Kernel's load_unaligned_zeropad() function arises from incorrect reg indices. This issue could potentially lead to memory corruption or information disclosure. An attacker may exploit this vulnerability to execute arbitrary code or gain unauthorized access to sensitive information. The vulnerability was introduced in version v5.16 of the Linux Kernel and has been fixed in version v5.16.5.
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. Updating the Kernel to the fixed version is the recommended solution.
Conclusion
In conclusion, the arm64 Kernel's load_unaligned_zeropad() function in the Linux Kernel version v5.16 is vulnerable to incorrect reg indices, which could lead to memory corruption or information disclosure. It is crucial to update the Kernel to version v5.16.5 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially lead to memory corruption or information disclosure. Attackers may exploit this issue to execute arbitrary code or gain unauthorized access to sensitive information.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze and alert you in real-time if any open-source vulnerabilities, including this one, are detected.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if an attacker can gain access to the affected system.
If you cannot immediately update the Kernel, it is recommended to implement other security measures such as network segmentation, access controls, and monitoring to reduce the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
