CVE-2026-72240

mfd: sm501: Fix reference leak on failed device registration

N/A
Published: August 15, 2026 at 05:54 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.21 ≤ v < 5.10.2612.6.21 ≤ v < 5.15.2122.6.21 ≤ v < 6.1.1782.6.21 ≤ v < 6.12.972.6.21 ≤ v < 6.18.402.6.21 ≤ v < 6.6.1452.6.21 ≤ v < 7.1.52.6.21 ≤ v < 7.22.6.21b6d6454fdb66f3829af8b92ab06825b6060fdf7e
Vendor states this is fixed in 0baf9d43a7b7b43df2900bd8656e75b725028b6e (fixed)
Vendor states this is fixed in 16a42c88c4667fa0bd944e438a667e059551f1f1 (fixed)
Vendor states this is fixed in 2ff8156fd500d54c61430b6834137fd0a07047ce (fixed)
Vendor states this is fixed in 760a1029692f1d788dc11aa636a3bf432e58b240 (fixed)
Vendor states this is fixed in 8c2f0b42fc252e1bf1c7746447091a468e784ca1 (fixed)
Vendor states this is fixed in a3e340d506c1036a747fb0972aebf1063f7ef30e (fixed)
Vendor states this is fixed in bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e (fixed)
Vendor states this is fixed in e2dac91380a10e9e8d5883fb73ce9d9b390a629c (fixed)
Vendor states this is fixed in 2.6.21 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card