In the Linux kernel, the following vulnerability has been resolved: regulator: fp9931: Fix VPOS/VNEG voltage selector table The VPOSNEG_table[] mapping does not match the FP9931 datasheet. The datasheet defines the VPOS/VNEG voltage mapping as: 00h-04h -> 7.04V (-7.04V) 05h -> 7.26V (-7.26V) 06h -> 7.49V (-7.49V) ... 28h-3Fh -> 15.06V (-15.06V) However, VPOSNEG_table[] has two issues: 1. Selector 0x00~0x04 should all map to 7.04V (5 entries), but the table has 6 entries of 7.04V, causing all subsequent entries to be shifted by one position. 2. Selectors 0x29~0x3F should all clamp to 15.06V (23 entries), but the table has only 41 entries. Any selector value above 0x28 would result in an out-of-bounds table access. Fix both issues by removing the duplicate 7.04V entry and appending the missing 23 clamped 15.06V entries, bringing the table to the correct size of 64 entries (0x00~0x3F).
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-80745 addresses a critical misconfiguration in the Linux kernel's FP9931 regulator driver where the voltage selector table (VPOSNEG_table[]) does not accurately reflect the FP9931 datasheet specifications. The vulnerability involves incorrect mapping of selector values to their corresponding VPOS/VNEG voltage outputs, with the table containing misaligned entries that could cause the regulator to output incorrect voltages. This affects any system using the FP9931 voltage regulator—commonly found in display and power management subsystems—potentially causing hardware malfunction, device instability, or system crashes when the driver attempts to set voltage levels that don't match actual hardware capabilities.
While this CVE carries a MITRE ATT&CK mapping of N/A, practitioners using Casky.ai would recognize this as a firmware/driver integrity issue detectable through code analysis and hardware state verification techniques. The extended reasoning capabilities of Claude AI, when mapped against Casky's 754 security skills, would identify attack patterns related to T1542 (Firmware Corruption) and T1561 (Disk Wipe), since malconfigured power regulation could be weaponized to corrupt system memory or trigger unexpected hardware failures. Security teams analyzing this vulnerability would examine kernel module behavior, voltage rail anomalies in system logs, and discrepancies between driver configuration and hardware specifications—findings that would surface during firmware integrity assessments and device driver audits in their Casky dashboard.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-80745. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation