Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98529 Overview
CVE-2026-98529 affects the Linux kernel's Arizona GPIO driver (gpio-arizona). The flaw is a runtime power management (PM) reference leak in arizona_gpio_direction_out(). When switching a persistent GPIO line from input to output, the driver acquires a runtime PM reference on the parent device. If the subsequent regmap_update_bits() call fails, the reference is never released. No later direction_in() call can balance it because the direction change never completed.
The upstream fix drops the runtime PM reference on the update failure path. Multiple stable kernel branches received backports of the patch.
Critical Impact
Leaked runtime PM references prevent the parent device from entering low-power states, causing resource retention and potential suspend/resume failures on systems using Cirrus Logic Arizona codecs.
Affected Products
- Linux kernel gpio-arizona driver (Cirrus Logic Arizona codec GPIO support)
- Multiple upstream and stable kernel branches patched via the commits referenced below
- Embedded and mobile Linux systems that integrate Arizona-family audio codecs
Discovery Timeline
- 2026-10-18 - CVE-2026-98529 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-98529
Vulnerability Analysis
The arizona_gpio_direction_out() function manages GPIO direction transitions for Cirrus Logic Arizona-family audio codecs. For persistent GPIO lines, switching from input to output requires the parent device to stay powered, so the driver calls pm_runtime_get_sync() to raise the runtime PM usage count on the parent.
After obtaining the reference, the driver calls regmap_update_bits() to program the hardware direction register. The original code assumed this write would succeed. When the regmap write fails, the function returns the error without releasing the PM reference it just acquired.
The imbalance is unrecoverable through normal driver flow. A later arizona_gpio_direction_in() call cannot drop the stray reference, because the direction state machine never transitioned to output in the first place. The reference persists until driver unload or reboot.
Root Cause
The root cause is missing cleanup on an error path, a classic resource-leak pattern [CWE-772]. The function acquires a reference before performing an operation that can fail, but does not release that reference when the operation fails. The condition for leaking is specific: the GPIO must be marked persistent, the direction must change from input to output, and the regmap write must fail.
Attack Vector
This is a reliability and resource-management defect in a hardware-specific driver. Triggering the leak requires regmap_update_bits() to fail, which depends on bus errors, codec power states, or faulty hardware interaction. The flaw is not a direct remote attack vector and no exploit is publicly available. The EPSS score is 0.22% at the 11.8 percentile.
The practical impact is denial of low-power states for the Arizona codec parent device, increased power consumption, and potential suspend/resume regressions. The vulnerability is described in prose only because no public proof-of-concept code exists; readers can review the authoritative fix in the Linux Kernel Commit 40c010c1.
Detection Methods for CVE-2026-98529
Indicators of Compromise
- Elevated runtime PM usage counts on Arizona codec parent devices visible under /sys/devices/.../power/runtime_usage
- Arizona codec devices stuck in active runtime PM status when they should be suspended
- Kernel log messages indicating regmap_update_bits failures originating from gpio-arizona
- Unexpected increases in platform power draw correlating with GPIO direction changes
Detection Strategies
- Inventory kernel versions across Linux fleets and flag hosts running pre-patch builds of the gpio-arizona driver
- Audit /sys/kernel/debug/pm_genpd/ and runtime PM sysfs entries for Arizona parent devices that fail to idle
- Correlate suspend/resume failures on embedded or mobile Linux platforms with Arizona codec presence
Monitoring Recommendations
- Collect kernel logs centrally and alert on repeated regmap write failures associated with the Arizona driver
- Track system power telemetry on devices using Cirrus Logic Arizona codecs to detect baseline regressions
- Monitor kernel package versions through configuration management and flag deviations from patched baselines
How to Mitigate CVE-2026-98529
Immediate Actions Required
- Identify all Linux systems that load the gpio-arizona driver and prioritize them for kernel updates
- Apply vendor kernel updates that include the backported fix for CVE-2026-98529
- Reboot affected systems after patching to ensure the corrected driver is loaded
- Validate runtime PM behavior on Arizona codec devices after the update
Patch Information
The fix drops the runtime PM reference on the regmap_update_bits() failure path in arizona_gpio_direction_out(). The patch has been merged across multiple stable branches. Reference commits include Linux Kernel Commit 39748357, Linux Kernel Commit 40c010c1, Linux Kernel Commit 5c8e87f3, Linux Kernel Commit 61ed58b7, Linux Kernel Commit 9d8d6cdd, Linux Kernel Commit 9ee200f4, Linux Kernel Commit a9f73848, and Linux Kernel Commit e9d81027.
Workarounds
- Unload the gpio-arizona module on systems that do not require Arizona codec GPIO functionality
- Avoid runtime direction changes on persistent GPIO lines backed by the Arizona driver until the patch is applied
- Reboot affected systems periodically to clear accumulated leaked runtime PM references as a temporary measure
# Verify running kernel version and loaded Arizona GPIO driver
uname -r
lsmod | grep -i arizona
# Inspect runtime PM state for Arizona parent devices
for d in /sys/bus/*/devices/*arizona*; do
echo "$d"
cat "$d/power/runtime_status" 2>/dev/null
cat "$d/power/runtime_usage" 2>/dev/null
done
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

