Answer in brief
CVE-2026-72155 records a Unknown severity vulnerability in mtd: spi-nor: swp: Improve locking user experience. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <dc341272cf8e15a2c511db3c4df5dab8adf70ad0 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <6110ab5ffd84e8daa654652446a03ce2f77580a7 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <c0806df5cf806545160f3fdac3c888926ceac557 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <12d4d69221159e6d0e72400ec81195d691169b53 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <e1d456b26bf23e30db305a6184e8abd9ab68bbf2 | 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a, dc341272cf8e15a2c511db3c4df5dab8adf70ad0, 6110ab5ffd84e8daa654652446a03ce2f77580a7, c0806df5cf806545160f3fdac3c888926ceac557, 12d4d69221159e6d0e72400ec81195d691169b53, e1d456b26bf23e30db305a6184e8abd9ab68bbf2 |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72155 records a Unknown severity vulnerability in mtd: spi-nor: swp: Improve locking user experience. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <dc341272cf8e15a2c511db3c4df5dab8adf70ad0 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <6110ab5ffd84e8daa654652446a03ce2f77580a7 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <c0806df5cf806545160f3fdac3c888926ceac557 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <12d4d69221159e6d0e72400ec81195d691169b53 || >=3dd8012a8eeb3702fa17450ec1a16a3f38af138d <e1d456b26bf23e30db305a6184e8abd9ab68bbf2 | 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a, dc341272cf8e15a2c511db3c4df5dab8adf70ad0, 6110ab5ffd84e8daa654652446a03ce2f77580a7, c0806df5cf806545160f3fdac3c888926ceac557, 12d4d69221159e6d0e72400ec81195d691169b53, e1d456b26bf23e30db305a6184e8abd9ab68bbf2 |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.