CVE-2026-72155: mtd: spi-nor: swp: Improve locking user experience

Received
AliasesUBUNTU-CVE-2026-72155DEBIAN-CVE-2026-72155
Published 15-08-2026Last modified 23-08-2026

Vulnerability summary

CVE-2026-72155 is a vulnerability in linux with no CVSS score yet. EPSS estimates a 0.22% chance of exploitation in the next 30 days, higher than 12.1% of scored vulnerabilities.

Priority
Insufficient evidence

No CVSS vector published; no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
Not scored
010
No CVSS score recorded
EPSS score
0.22%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 11 · Related 11
SUSE-SU-2026:5091-1USN-8887-1USN-8887-2USN-8887-3USN-8888-1USN-8888-2

Timeline

  1. 15-08-2026
    PublishedVulnerability first disclosed.
  2. 23-08-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

Risk metrics not yet published.

EPSS trend

Probability

0.22%

Chance of exploitation in the next 30 days

Percentile

12%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.22% on 06-10-2026

06-10-202605-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: not stated in public data.

Ubuntu168 products
  • linuxAll versions (No fix recorded) | < 5.15.0-202.212 | < 6.8.0-147.147 | < 7.0.0-38.38
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 5.15.0-1119.126 | < 6.8.0-1067.70 | < 7.0.0-1014.14
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian1 product
  • linux< 6.1.180-1 | < 6.12.100-1 | < 7.1.5-1
Linux1 product
  • linux≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < 23c285be8f6fcde9088fe12bb69c701d46696be1 | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < a6fd2145c73b80bb6a5eed7355a4f63597d712d9 | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < dc341272cf8e15a2c511db3c4df5dab8adf70ad0 | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < 6110ab5ffd84e8daa654652446a03ce2f77580a7 | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < c0806df5cf806545160f3fdac3c888926ceac557 | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < 12d4d69221159e6d0e72400ec81195d691169b53 | ≥ 3dd8012a8eeb3702fa17450ec1a16a3f38af138d, < e1d456b26bf23e30db305a6184e8abd9ab68bbf2 | 4.6

3 vendors · 170 products

References

22 links
Show all 22 references