Unintentional Stack Access in mtd: physmap-bt1-rom
Summary
GSD-2021-1000082: mtd: physmap: physmap-bt1-rom: Fix unintentional stack access. Affects Kernel versions >= b3e79e7682e075326df8041b826b03453acacd0a, < 4d786870e3262ec098a3b4ed10b895176bc66ecb. 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 mtd (Memory Technology Devices) subsystem in the Linux Kernel provides an abstraction layer for various flash memory devices. One of the components in this subsystem is the physmap driver, which handles the mapping of physical flash memory to logical addresses. The physmap-bt1-rom driver is a specific implementation of the physmap driver for the BT1 ROM chip. This vulnerability affects the physmap-bt1-rom driver in the Linux Kernel.
Vulnerability Detail
The vulnerability in the physmap-bt1-rom driver is due to an unintentional stack access. This means that the driver may access data on the stack that it should not have access to, potentially leading to information disclosure or arbitrary code execution. The exact impact and attack plausibility of this vulnerability have not yet been proven. The vulnerability was introduced in version v5.10 of the Linux Kernel and is fixed in version v5.12.3.
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 mtd: physmap-bt1-rom driver of the Linux Kernel could potentially lead to information disclosure or arbitrary code execution. It is recommended to update the Linux Kernel to version v5.12.3 or later to fix this vulnerability. If you need further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to information disclosure or arbitrary code execution.
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 and Vulert will analyze it for open-source vulnerabilities, including this one.
Yes, a patch is available in version v5.12.3 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.
The best way to mitigate the risk is to update the Linux Kernel to the fixed version. However, if updating is not possible, you can consider implementing additional security measures, such as restricting access to the affected driver or monitoring for any suspicious activity.
You can find more information about this vulnerability in the GSD-2021-1000082.json file in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000082.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
