mtd: spi-nor: swp: Improve locking user experience
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e1d456b26bf23e30db305a6184e8abd9ab68bbf2, Kernel 12d4d69221159e6d0e72400ec81195d691169b53, Kernel 23c285be8f6fcde9088fe12bb69c701d46696be1 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: swp: Improve locking user experience In the case of the first block being locked (or the few first blocks), if the user want to fully unlock the device it has two possibilities: - either it asks to unlock the entire device, and this works; - or it asks to unlock just the block(s) that are currently locked, which fails. It fails because the conditions "can_be_top" and "can_be_bottom" are true. Indeed, in this case, we unlock everything, so the TB bit does not matter. However in the current implementation, use_top would be true (as this is the favourite option) and lock_len, which in practice should be reduced down to 0, is set to "nor->params->size - (ofs + len)" which is a positive number. This is wrong. An easy way is to simply add an extra condition. In the unlock() path, if we can achieve the same result from both sides, it means we unlock everything and lock_len must simply be 0. A comment is added to clarify that logic.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <e1d456b26bf23e30db305a6184e8abd9ab68bbf2, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <12d4d69221159e6d0e72400ec81195d691169b53, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <23c285be8f6fcde9088fe12bb69c701d46696be1, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <6110ab5ffd84e8daa654652446a03ce2f77580a7, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <a6fd2145c73b80bb6a5eed7355a4f63597d712d9, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <c0806df5cf806545160f3fdac3c888926ceac557, >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <dc341272cf8e15a2c511db3c4df5dab8adf70ad0, =4.6 | e1d456b26bf23e30db305a6184e8abd9ab68bbf2, 12d4d69221159e6d0e72400ec81195d691169b53, 23c285be8f6fcde9088fe12bb69c701d46696be1, 6110ab5ffd84e8daa654652446a03ce2f77580a7, 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a, a6fd2145c73b80bb6a5eed7355a4f63597d712d9, c0806df5cf806545160f3fdac3c888926ceac557, dc341272cf8e15a2c511db3c4df5dab8adf70ad0 |
| linux-kernel: Kernel | >=5.11.0 <5.15.217, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=4.6.0 <5.10.266 | 5.15.217, 6.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.10.266 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket