PatchSiren cyber security CVE debrief
CVE-2026-72397 Linux CVE debrief
The Linux kernel vulnerability CVE-2026-72397 has been resolved. The pmbus_data2reg_vid() function was modified to honor the vrm_version in its calculations, as it previously hardcoded the VR11 encoding. This change ensures that drivers selecting non-VR11 VID modes and exposing regulators or hwmon vout setters will not send incorrect codes to PMBUS_VOUT_COMMAND.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-15
- Original CVE updated
- 2026-08-15
- Advisory published
- 2026-08-15
- Advisory updated
- 2026-08-15
Who should care
System administrators and developers working with Linux kernel-based systems, particularly those using pmbus and VID modes, should review and apply the patch to prevent potential issues. Additionally, security teams and vulnerability management professionals should be aware of the potential impact of this vulnerability on their systems and take steps to verify and mitigate exposure. Operators of systems using the affected Linux kernel configurations should also be aware of the potential risks and take proactive measures to ensure system security and stability. This includes reviewing system configurations, monitoring system logs, and verifying the implementation of the patch.
Technical summary
The pmbus_data2reg_vid() function in the Linux kernel was modified to correctly handle vrm_version configurations. Previously, it hardcoded the VR11 encoding, which could lead to incorrect codes being sent to PMBUS_VOUT_COMMAND. This change ensures that drivers using non-VR11 VID modes will now correctly calculate and send codes. The technical impact of this vulnerability is significant, as it could result in dangerously wrong codes being sent to PMBUS_VOUT_COMMAND, potentially leading to system instability or incorrect voltage regulation. The fix addresses this issue by making the function configurable and aware of different VID modes.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the kernel patch to ensure the fix is implemented
- Verify system configurations and VID modes to prevent incorrect codes from being sent to PMBUS_VOUT_COMMAND
- Monitor system logs for potential issues related to the vulnerability
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and NVD entry provide limited information about the vulnerability. Further analysis is required to fully understand the impact and affected systems. The pmbus_data2reg_vid() function's modification to honor vrm_version configurations is crucial. Defenders should verify system configurations, VID modes, and potential exposure to incorrect codes being sent to PMBUS_VOUT_COMMAND. Additionally, reviewing the Linux kernel patch and its implications on system operations is essential. The lack of detailed information on affected products and components necessitates a thorough review of system dependencies and potential vulnerabilities.
Official resources
-
CVE-2026-72397 CVE record
CVE.org
-
CVE-2026-72397 NVD detail
NVD
-
Source item URL
nvd_modified
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-15T06:22:13.270Z and has not been modified since then.