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-72240mfd: sm501: Fix reference leak on failed device registration

Description

In the Linux kernel, the following vulnerability has been resolved: mfd: sm501: Fix reference leak on failed device registration When platform_device_register() fails in sm501_register_device(), the embedded struct device in pdev has already been initialized by device_initialize(), but the failure path only reports the error and returns without dropping the device reference for the current platform device: sm501_register_device() -> platform_device_register(pdev) -> device_initialize(&pdev->dev) -> setup_pdev_dma_masks(pdev) -> platform_device_add(pdev) This leads to a reference leak when platform_device_register() fails. Fix this by calling platform_device_put() before returning the error. The issue was identified by a static analysis tool I developed and confirmed by manual review.

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 (20 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 b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < e2dac91380a10e9e8d5883fb73ce9d9b390a629c
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < 0baf9d43a7b7b43df2900bd8656e75b725028b6e
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < a3e340d506c1036a747fb0972aebf1063f7ef30e
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < 760a1029692f1d788dc11aa636a3bf432e58b240
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < 16a42c88c4667fa0bd944e438a667e059551f1f1
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < 2ff8156fd500d54c61430b6834137fd0a07047ce
    • affected b6d6454fdb66f3829af8b92ab06825b6060fdf7e – < 8c2f0b42fc252e1bf1c7746447091a468e784ca1
  • Linux · Linux

    • affected 2.6.21
    • unaffected < 2.6.21
    • 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-72240 badge
[![CVE-2026-72240](https://cveledger.app/badge/CVE-2026-72240.svg)](https://cveledger.app/cve/CVE-2026-72240)

Record last updated .