Public vulnerability disclosure

CVE-2026-72240

mfd: sm501: Fix reference leak on failed device registration

published

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.

Technical severityUnscoredNo score in collected sources
Published2026-08-15Source updated 2026-11-06
Collected2026-11-062 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < e2dac91380a10e9e8d5883fb73ce9d9b390a629c (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < 0baf9d43a7b7b43df2900bd8656e75b725028b6e (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < a3e340d506c1036a747fb0972aebf1063f7ef30e (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < 760a1029692f1d788dc11aa636a3bf432e58b240 (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < 16a42c88c4667fa0bd944e438a667e059551f1f1 (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < 2ff8156fd500d54c61430b6834137fd0a07047ce (affected, git)
≥ b6d6454fdb66f3829af8b92ab06825b6060fdf7e; < 8c2f0b42fc252e1bf1c7746447091a468e784ca1 (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
2.6.21 (affected)
≥ 0; < 2.6.21 (unaffected, semver)
≥ 5.10.261; ≤ 5.10.* (unaffected, semver)
≥ 5.15.212; ≤ 5.15.* (unaffected, semver)
≥ 6.1.178; ≤ 6.1.* (unaffected, semver)
≥ 6.6.145; ≤ 6.6.* (unaffected, semver)
≥ 6.12.97; ≤ 6.12.* (unaffected, semver)
≥ 6.18.40; ≤ 6.18.* (unaffected, semver)
≥ 7.1.5; ≤ 7.1.* (unaffected, semver)
≥ 7.2; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide