mtd: Require Write Permissions for Locking and Badblock IOCTLs
Summary
UVI-2021-1000475: mtd: require write permissions for locking and badblock ioctls. Affects Kernel versions >= 389c74c218d3b182e9cd767e98cee0e0fd0dabaa, < f73b29819c6314c0ba8b7d5892dfb03487424bee. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel package in the Linux ecosystem is responsible for managing the core functionality of the operating system. It provides essential services and interfaces for hardware, software, and user applications. The MTD (Memory Technology Devices) subsystem within the Kernel is specifically designed to handle flash memory devices. It allows for efficient management and access to flash storage, including locking and badblock operations.
Vulnerability Detail
The vulnerability identified as UVI-2021-1000475 in the MTD subsystem of the Kernel allows unauthorized users to perform locking and badblock operations without requiring write permissions. This means that an attacker with read-only access to the flash memory device can manipulate its state, potentially leading to data corruption, denial of service, or other security breaches. The vulnerability was introduced in version v4.14.194 of the Linux Kernel and was fixed in version v4.14.233.
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
As a temporary workaround, users can restrict access to the flash memory device by modifying the permissions or access control settings. By ensuring that only trusted users or processes have write permissions to the device, the risk of unauthorized manipulation can be mitigated. Here is an example of how to modify permissions using the 'chmod' command:
chmod o-w /dev/mtdX
Replace '/dev/mtdX' with the actual device path of the flash memory.
Conclusion
The vulnerability in the MTD subsystem of the Linux Kernel allows unauthorized users to perform locking and badblock operations without requiring write permissions. To mitigate this risk, it is crucial to update the Kernel to version v4.14.233 or later. Additionally, restricting write access to the flash memory device can serve as a temporary workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability allows unauthorized users to manipulate the state of flash memory devices, potentially leading to data corruption, denial of service, or other security breaches.
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 in real-time.
Yes, as a temporary workaround, you can modify the permissions or access control settings of the flash memory device to restrict write access. Refer to the 'workaround' section for more details.
Yes, this vulnerability has been fixed in Linux Kernel version v4.14.233. It is recommended to update to this version or later to ensure the security of your system.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/UVI-2021-1000475.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
