CVE-2026-72171: mtd: slram: remove failed entries from the device list
Noroxi assessment
Priority: Monitor (action score 31/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 200b8bc5b6065b02f3775cf131f14b8e1156a00a, 2fd0cbbb34447ccddab67a2a638a07c6d94cae7a, 36f1648644d769c496a8e47e53603e863e358d73.
Low priority for now. Upgrade to Linux Linux 200b8bc5b6065b02f3775cf131f14b8e1156a00a, 2fd0cbbb34447ccddab67a2a638a07c6d94cae7a, 36f1648644d769c496a8e47e53603e863e358d73 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: slram: remove failed entries from the device list register_device() links a new slram_mtdlist entry before allocating all of the state needed by the entry. If a later allocation, memremap(), or mtd_device_register() fails, the partially initialized entry remains on the global list. A later cleanup can then dereference or free invalid state from that failed entry. Unwind the partially initialized entry and clear the list tail on each failure path after the entry has been linked.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9ee674ab10f755bbedbcbb8e76745d2bb8de88d1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e97415b8254d9cc131b7bb1c80fcf38123269b9aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f40acf577bb0fb0829f285ecfeb27d817840601caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 200b8bc5b6065b02f3775cf131f14b8e1156a00aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2fd0cbbb34447ccddab67a2a638a07c6d94cae7aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d8dcbbfa0d695a5244059aa34a2e81f3e8df1082affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before bdcdfc2464659789032edfad15ff5f7a166f5d7baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 36f1648644d769c496a8e47e53603e863e358d73affected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72167Aug 15, 2026 · mtd: rawnand: pl353: fix probe resource allocation0Monitor
- ← EarlierCVE-2026-72169Aug 15, 2026 · kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES0Monitor
- Later →CVE-2026-72173Aug 15, 2026 · fs/proc/task_mmu: do not warn on seeing non-migration pmd entry0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 200b8bc5b6065b02f3775cf131f14b8e1156a00a | Vendor (CNA) |
| Linux Linux | 2fd0cbbb34447ccddab67a2a638a07c6d94cae7a | Vendor (CNA) |
| Linux Linux | 36f1648644d769c496a8e47e53603e863e358d73 | Vendor (CNA) |
| Linux Linux | 9ee674ab10f755bbedbcbb8e76745d2bb8de88d1 | Vendor (CNA) |
| Linux Linux | bdcdfc2464659789032edfad15ff5f7a166f5d7b | Vendor (CNA) |
| Linux Linux | d8dcbbfa0d695a5244059aa34a2e81f3e8df1082 | Vendor (CNA) |
| Linux Linux | e97415b8254d9cc131b7bb1c80fcf38123269b9a | Vendor (CNA) |
| Linux Linux | f40acf577bb0fb0829f285ecfeb27d817840601c | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package 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.
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 researchersFinders, 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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2fd0cbbb34447ccddab67a2a638a07c6d94cae7a
- git.kernel.org/stable/c/36f1648644d769c496a8e47e53603e863e358d73
- git.kernel.org/stable/c/9ee674ab10f755bbedbcbb8e76745d2bb8de88d1
- git.kernel.org/stable/c/bdcdfc2464659789032edfad15ff5f7a166f5d7b
- git.kernel.org/stable/c/d8dcbbfa0d695a5244059aa34a2e81f3e8df1082
- git.kernel.org/stable/c/e97415b8254d9cc131b7bb1c80fcf38123269b9a
- git.kernel.org/stable/c/f40acf577bb0fb0829f285ecfeb27d817840601c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.