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-72171mtd: slram: remove failed entries from the device list

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days 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

CVSS scores of CVE-2026-72171, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9ee674ab10f755bbedbcbb8e76745d2bb8de88d1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e97415b8254d9cc131b7bb1c80fcf38123269b9a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f40acf577bb0fb0829f285ecfeb27d817840601c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 200b8bc5b6065b02f3775cf131f14b8e1156a00a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2fd0cbbb34447ccddab67a2a638a07c6d94cae7a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d8dcbbfa0d695a5244059aa34a2e81f3e8df1082
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bdcdfc2464659789032edfad15ff5f7a166f5d7b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 36f1648644d769c496a8e47e53603e863e358d73
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 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-72171 badge
[![CVE-2026-72171](https://cveledger.app/badge/CVE-2026-72171.svg)](https://cveledger.app/cve/CVE-2026-72171)

Record last updated .