CVE-2026-80974 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems with the mfd sm501 driver enabled should review and apply the available patches to fix the memory leak vulnerability. Affected operator, platform, vulnerability-management, and security-team impact should be assessed to prioritize patch application and mitigation efforts.

Why it matters

A memory leak vulnerability was found in the Linux kernel's mfd sm501 driver. This could potentially lead to memory leaks when the device is removed. Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems with the mfd sm501 driver enabled should review and apply the available patches to fix the memory leak vulnerability.

• Memory leaks could lead to increased memory usage and potential system crashes
• Verification of patch application and memory leak fixes is necessary
• Monitoring system memory usage is recommended to detect potential issues

Technical summary

The Linux kernel's mfd sm501 driver has a memory leak vulnerability. The sm501_pci_probe() and sm501_plat_probe() functions allocate memory for struct sm501_devdata, but the corresponding remove functions sm501_pci_remove() and sm501_plat_remove() do not free this memory. This could potentially lead to memory leaks when the device is removed. Linux kernel developers and maintainers should review the Linux kernel patch commits to validate affected scope, severity, and vendor guidance. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Defensive priority

Low

Recommended defensive actions

• Review and apply the available patches to fix the memory leak vulnerability
• Monitor system memory usage to detect potential issues
• Consider implementing additional memory monitoring and leak detection tools
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. The Linux kernel patch commits are available, but there is no information on exploitation or impact. To verify patch application and memory leak fixes, defenders should review the Linux kernel patch commits and check relevant monitoring, detection, and logs for exposed assets that need extra review. Additional memory monitoring and leak detection tools may be necessary to detect potential issues.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.