Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < 23c285be8f6fcde9088fe12bb69c701d46696be1
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < a6fd2145c73b80bb6a5eed7355a4f63597d712d9
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < dc341272cf8e15a2c511db3c4df5dab8adf70ad0
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < 6110ab5ffd84e8daa654652446a03ce2f77580a7
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < c0806df5cf806545160f3fdac3c888926ceac557
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < 12d4d69221159e6d0e72400ec81195d691169b53
    • affected 3dd8012a8eeb3702fa17450ec1a16a3f38af138d – < e1d456b26bf23e30db305a6184e8abd9ab68bbf2
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 5.10.266 – ≤ 5.10.*
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72155 badge
[![CVE-2026-72155](https://cveledger.app/badge/CVE-2026-72155.svg)](https://cveledger.app/cve/CVE-2026-72155)

Record last updated .