Answer in brief
CVE-2026-72240 records a Unknown severity vulnerability in mfd: sm501: Fix reference leak on failed device registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72240 records a Unknown severity vulnerability in mfd: sm501: Fix reference leak on failed device registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <e2dac91380a10e9e8d5883fb73ce9d9b390a629c || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <0baf9d43a7b7b43df2900bd8656e75b725028b6e || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <a3e340d506c1036a747fb0972aebf1063f7ef30e || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <760a1029692f1d788dc11aa636a3bf432e58b240 || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <16a42c88c4667fa0bd944e438a667e059551f1f1 || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <2ff8156fd500d54c61430b6834137fd0a07047ce || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <8c2f0b42fc252e1bf1c7746447091a468e784ca1 | bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e, e2dac91380a10e9e8d5883fb73ce9d9b390a629c, 0baf9d43a7b7b43df2900bd8656e75b725028b6e, a3e340d506c1036a747fb0972aebf1063f7ef30e, 760a1029692f1d788dc11aa636a3bf432e58b240, 16a42c88c4667fa0bd944e438a667e059551f1f1, 2ff8156fd500d54c61430b6834137fd0a07047ce, 8c2f0b42fc252e1bf1c7746447091a468e784ca1 |
| Linux/Linuxgeneric | 2.6.21 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <e2dac91380a10e9e8d5883fb73ce9d9b390a629c || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <0baf9d43a7b7b43df2900bd8656e75b725028b6e || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <a3e340d506c1036a747fb0972aebf1063f7ef30e || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <760a1029692f1d788dc11aa636a3bf432e58b240 || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <16a42c88c4667fa0bd944e438a667e059551f1f1 || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <2ff8156fd500d54c61430b6834137fd0a07047ce || >=b6d6454fdb66f3829af8b92ab06825b6060fdf7e <8c2f0b42fc252e1bf1c7746447091a468e784ca1 | bbb1ecaed4ed7680e63d3a0f143f03de32de5d6e, e2dac91380a10e9e8d5883fb73ce9d9b390a629c, 0baf9d43a7b7b43df2900bd8656e75b725028b6e, a3e340d506c1036a747fb0972aebf1063f7ef30e, 760a1029692f1d788dc11aa636a3bf432e58b240, 16a42c88c4667fa0bd944e438a667e059551f1f1, 2ff8156fd500d54c61430b6834137fd0a07047ce, 8c2f0b42fc252e1bf1c7746447091a468e784ca1 |
| Linux/Linuxgeneric | 2.6.21 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.