Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 12d4d69221159e6d0e72400ec81195d691169b53, 23c285be8f6fcde9088fe12bb69c701d46696be1, 6110ab5ffd84e8daa654652446a03ce2f77580a7.

Low priority for now. Upgrade to Linux Linux 12d4d69221159e6d0e72400ec81195d691169b53, 23c285be8f6fcde9088fe12bb69c701d46696be1, 6110ab5ffd84e8daa654652446a03ce2f77580a7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 23, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72155

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.6affected
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before 23c285be8f6fcde9088fe12bb69c701d46696be1affected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before a6fd2145c73b80bb6a5eed7355a4f63597d712d9affected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before 9a0d8dec3d11ca95d67537ea8fa6ee2730a5038aaffected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before dc341272cf8e15a2c511db3c4df5dab8adf70ad0affected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before 6110ab5ffd84e8daa654652446a03ce2f77580a7affected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before c0806df5cf806545160f3fdac3c888926ceac557affected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before 12d4d69221159e6d0e72400ec81195d691169b53affected · git
    • 3dd8012a8eeb3702fa17450ec1a16a3f38af138d and later · before e1d456b26bf23e30db305a6184e8abd9ab68bbf2affected · git
    • before 4.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72153Aug 15, 2026 · irqchip/crossbar: Use correct index in crossbar_domain_free()
    0Monitor
  • ← EarlierCVE-2026-72154Aug 15, 2026 · openrisc: Fix jump_label smp syncing
    31Monitor
  • Later →CVE-2026-72156Aug 15, 2026 · fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux12d4d69221159e6d0e72400ec81195d691169b53Vendor (CNA)
Linux Linux23c285be8f6fcde9088fe12bb69c701d46696be1Vendor (CNA)
Linux Linux6110ab5ffd84e8daa654652446a03ce2f77580a7Vendor (CNA)
Linux Linux9a0d8dec3d11ca95d67537ea8fa6ee2730a5038aVendor (CNA)
Linux Linuxa6fd2145c73b80bb6a5eed7355a4f63597d712d9Vendor (CNA)
Linux Linuxc0806df5cf806545160f3fdac3c888926ceac557Vendor (CNA)
Linux Linuxdc341272cf8e15a2c511db3c4df5dab8adf70ad0Vendor (CNA)
Linux Linuxe1d456b26bf23e30db305a6184e8abd9ab68bbf2Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records