data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-98529 in the interactive tracker

CVE-2026-98529

gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out()

Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/gpio. Debian urgency: not yet assigned.

Debian does not build this code. The per-release build detail is under "Where it lives" below.

What to do, per Debian release

Debian's own status for CVE-2026-98529 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixed6.1.190-1Update the kernel and reboot. Fixed in 6.1.190-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.113-1Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.2.9-1Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.9-1Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

Switching a persistent GPIO line from input to output acquires a runtime PM reference on the parent device, but if the subsequent regmap_update_bits() fails the reference is never dropped and no later direction_in() can balance it since the direction was never changed. Drop the reference on the update failure path.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/gpio/gpio-arizona.c

What this is
WOLFSON MICROELECTRONICS DRIVERSMAINTAINERS section matched on drivers/gpio/gpio-arizona.c · patches@opensource.cirrus.com · Supported
Kernel module
none to look for. The file would have gone into gpio_arizona, and Debian does not compile it into that module, so finding gpio_arizona in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_GPIOLIB|CONFIG_GPIO_ARIZONA' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

  • bookworm, trixie, forky, sidn
n
not enabled on any flavour - this release does not build the code
Build switches
CONFIG_GPIOLIB, CONFIG_GPIO_ARIZONA
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-10-18 (today)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
not scored
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/gpio

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
4.135.10.27140c010c18663
4.135.15.22261ed58b745c1
4.136.1.1895c8e87f33b68
4.136.6.1589d8d6cddcb7c
4.136.12.1129ee200f48498
4.136.18.55a9f738487c11
4.137.2.939748357db26
4.137.3e9d810279f84

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98529, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.