Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72240: mfd: sm501: Fix reference leak on failed device registration

—No exploit Fix available

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.22% (FIRST EPSS).
  • Fixed version: Linux Linux 0baf9d43a7b7b43df2900bd8656e75b725028b6e, 16a42c88c4667fa0bd944e438a667e059551f1f1, 2ff8156fd500d54c61430b6834137fd0a07047ce.

Low priority for now. Upgrade to Linux Linux 0baf9d43a7b7b43df2900bd8656e75b725028b6e, 16a42c88c4667fa0bd944e438a667e059551f1f1, 2ff8156fd500d54c61430b6834137fd0a07047ce 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: 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.

Published
Aug 15, 2026
Updated
Nov 6, 2026
EPSS
0.2% · 12th 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%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-72240

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

    • 2.6.21affected
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before bbb1ecaed4ed7680e63d3a0f143f03de32de5d6eaffected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before e2dac91380a10e9e8d5883fb73ce9d9b390a629caffected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before 0baf9d43a7b7b43df2900bd8656e75b725028b6eaffected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before a3e340d506c1036a747fb0972aebf1063f7ef30eaffected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before 760a1029692f1d788dc11aa636a3bf432e58b240affected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before 16a42c88c4667fa0bd944e438a667e059551f1f1affected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before 2ff8156fd500d54c61430b6834137fd0a07047ceaffected · git
    • b6d6454fdb66f3829af8b92ab06825b6060fdf7e and later · before 8c2f0b42fc252e1bf1c7746447091a468e784ca1affected · git
    • before 2.6.21not 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

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-72234Aug 15, 2026 · batman-adv: access unicast_ttvn skb->data only after skb realloc
    39Monitor
  • ← EarlierCVE-2026-72235Aug 15, 2026 · batman-adv: retrieve ethhdr after potential skb realloc on RX
    35Monitor
  • Later →CVE-2026-72241Aug 15, 2026 · leds: uleds: Fix potential buffer overread
    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 Linux0baf9d43a7b7b43df2900bd8656e75b725028b6eVendor (CNA)
Linux Linux16a42c88c4667fa0bd944e438a667e059551f1f1Vendor (CNA)
Linux Linux2ff8156fd500d54c61430b6834137fd0a07047ceVendor (CNA)
Linux Linux760a1029692f1d788dc11aa636a3bf432e58b240Vendor (CNA)
Linux Linux8c2f0b42fc252e1bf1c7746447091a468e784ca1Vendor (CNA)
Linux Linuxa3e340d506c1036a747fb0972aebf1063f7ef30eVendor (CNA)
Linux Linuxbbb1ecaed4ed7680e63d3a0f143f03de32de5d6eVendor (CNA)
Linux Linuxe2dac91380a10e9e8d5883fb73ce9d9b390a629cVendor (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).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

References

All records