CVE-2026-72155: Linux kernel · mtd: spi-nor: swp: Improve locking user experience
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e1d456b26bf23e30db305a6184e8abd9ab68bbf2 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:19 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in e1d456b26bf23e30db305a6184e8abd9ab68bbf2, dc341272cf8e15a2c511db3c4df5dab8adf70ad0, c0806df5cf806545160f3fdac3c888926ceac557 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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.
References
- git.kernel.org/stable/c/23c285be8f6fcde9088fe12bb69c701d46696be1 (opens in a new tab)
- git.kernel.org/stable/c/a6fd2145c73b80bb6a5eed7355a4f63597d712d9 (opens in a new tab)
- git.kernel.org/stable/c/9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a (opens in a new tab)
- git.kernel.org/stable/c/dc341272cf8e15a2c511db3c4df5dab8adf70ad0 (opens in a new tab)
- git.kernel.org/stable/c/6110ab5ffd84e8daa654652446a03ce2f77580a7 (opens in a new tab)
- git.kernel.org/stable/c/c0806df5cf806545160f3fdac3c888926ceac557 (opens in a new tab)
- git.kernel.org/stable/c/12d4d69221159e6d0e72400ec81195d691169b53 (opens in a new tab)
- git.kernel.org/stable/c/e1d456b26bf23e30db305a6184e8abd9ab68bbf2 (opens in a new tab)