VulnerabilityPublished 15 Aug 2026Updated 9 Oct 2026

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

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1017.17~24.04.1, 7.0.0-1016.16~24.04.1 +11

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-4g3m-gr2j-r4mp

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-38.38	Fixed in 7.0.0-38.38
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1017.17	Fixed in 7.0.0-1017.17
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1016.16	Fixed in 7.0.0-1016.16
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.9	Fixed in 7.0.0-1008.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied to affected Linux Azure kernel versions to resolve the locking issue. The vendor advisory confirms that this and other Linux kernel vulnerabilities have been fixed in updated linux-azure kernel releases. Users should update to the fixed kernel versions to mitigate this issue.

Description

A vulnerability in the Linux kernel's mtd spi-nor swp locking mechanism was resolved, addressing incorrect behavior when unlocking blocks on certain Linux Azure kernel versions. The flaw caused unlock requests for specific locked blocks to fail due to improper lock length calculations, potentially impacting user experience. This issue has been fixed with an improved locking logic. Multiple Linux Azure kernel versions are affected. The vulnerability is rated medium severity and a patch is available.

Impact

The vulnerability causes failure in unlocking specific locked blocks on the device, which may lead to user inconvenience or inability to unlock device blocks as intended. There is no indication of direct security compromise or exploitation in the wild. The impact is primarily on the correctness and usability of the locking mechanism in the affected Linux Azure kernel versions.

Summary

The Linux kernel vulnerability (CVE-2026-72155) affects the mtd spi-nor swp subsystem's locking mechanism. When unlocking the first block(s) of a device, attempts to unlock only the locked blocks failed due to incorrect conditions involving "can_be_top" and "can_be_bottom" flags. The implementation incorrectly set the lock length to a positive number instead of zero when unlocking everything, causing the unlock operation to fail. The fix adds an extra condition to ensure lock_len is set to zero when unlocking the entire device, improving the user experience and correctness of the locking logic. This issue affects multiple specific versions of the linux-azure kernel.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 07:07 UTC

Technical details

References

Community reviews

Related threats