CVE-2026-72155
mtd: spi-nor: swp: Improve locking user experience
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < 23c285be8f6fcde9088fe12bb69c701d46696be1 (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < a6fd2145c73b80bb6a5eed7355a4f63597d712d9 (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < dc341272cf8e15a2c511db3c4df5dab8adf70ad0 (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < 6110ab5ffd84e8daa654652446a03ce2f77580a7 (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < c0806df5cf806545160f3fdac3c888926ceac557 (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < 12d4d69221159e6d0e72400ec81195d691169b53 (affected, git) ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d; < e1d456b26bf23e30db305a6184e8abd9ab68bbf2 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.6 (affected) ≥ 0; < 4.6 (unaffected, semver) ≥ 5.10.266; ≤ 5.10.* (unaffected, semver) ≥ 5.15.217; ≤ 5.15.* (unaffected, semver) ≥ 6.1.178; ≤ 6.1.* (unaffected, semver) ≥ 6.6.145; ≤ 6.6.* (unaffected, semver) ≥ 6.12.97; ≤ 6.12.* (unaffected, semver) ≥ 6.18.40; ≤ 6.18.* (unaffected, semver) ≥ 7.1.5; ≤ 7.1.* (unaffected, semver) ≥ 7.2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/23c285be8f6fcde9088fe12bb69c701d46696be1CNA: Linux
- https://git.kernel.org/stable/c/a6fd2145c73b80bb6a5eed7355a4f63597d712d9CNA: Linux
- https://git.kernel.org/stable/c/9a0d8dec3d11ca95d67537ea8fa6ee2730a5038aCNA: Linux
- https://git.kernel.org/stable/c/dc341272cf8e15a2c511db3c4df5dab8adf70ad0CNA: Linux
- https://git.kernel.org/stable/c/6110ab5ffd84e8daa654652446a03ce2f77580a7CNA: Linux
- https://git.kernel.org/stable/c/c0806df5cf806545160f3fdac3c888926ceac557CNA: Linux
- https://git.kernel.org/stable/c/12d4d69221159e6d0e72400ec81195d691169b53CNA: Linux
- https://git.kernel.org/stable/c/e1d456b26bf23e30db305a6184e8abd9ab68bbf2CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.