Look up another CVE · open CVE-2026-98528 in the interactive tracker
CVE-2026-98528
gpio: cdev: fix kernel stack leak to user-space in error path
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/gpio. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-98528 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
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.113-1 | Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.9-1 | Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.9-1 | Update 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
If we fail to acquire the GPIO chip guard in gpio_desc_to_lineinfo(), we return immediately before zeroing the info struct we'll end up passing to the user-space later in lineinfo_get_v1(). This may leak the kernel stack contents. Make gpio_desc_to_lineinfo() return int so that the -ENODEV returned on failure to acquire the guard can be propagated to the callers. While not strictly necessary: move the memset() before trying to acquire the SRCU read lock too for good measure.
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/gpiolib-cdev.c
- What this is
- GPIO UAPIMAINTAINERS section matched on drivers/gpio/gpiolib-cdev.c · linux-gpio@vger.kernel.org · Maintained
Check it on the machine
grep -wE 'CONFIG_GPIOLIB|CONFIG_GPIO_CDEV' /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 builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookworm, trixie, forky, sidYnot built on amd64/cloud-amd64
- Y
- built in where it is built at all; some flavours do not build it
- Build switches
- CONFIG_GPIOLIB, CONFIG_GPIO_CDEV
- 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
- unimportantsource
- Subsystem
- drivers/gpio
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.9 | 6.12.112 | 8460ee5216ab |
| 6.9 | 6.18.55 | cf3d043582e1 |
| 6.9 | 7.2.9 | 60a466f23190 |
| 6.9 | 7.3 | 1feb5d39b05a |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98528, 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.