mtd: require write permissions for locking and badblock ioctls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f7e6b19bc76471ba03725fe58e0c218a3d6266c3 · < 7b6552719c0ccbbea29dde4be141da54fdb5877e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mtd: require write permissions for locking and badblock ioctls
MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require write permission. Depending on the hardware MEMLOCK might even be write-once, e.g. for SPI-NOR flashes with their WP# tied to GND. OTPLOCK is always write-once.
MEMSETBADBLOCK modifies the bad block table.
From the CVE record · Linux
Linux kernel MTD ioctls did not require write permission for operations that change flash protection bits or the bad-block table. A local user able to issue these ioctls without write permission could make those changes; some protection changes may be irreversible, depending on the hardware.
Anyone running a Linux kernel with the affected MTD ioctls should check their kernel version against the vendor advisory; affected versions were not provided.