---
id: CVE-2026-31732
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()

  Since commit aab5c6f20023 ("gpio: set device type for GPIO chips"),
  `gdev->dev.release` is unset
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()

  Since commit aab5c6f20023 ("gpio: set device type for GPIO chips"),
  `gdev->dev.release` is unset.  A…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-401
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 6.9, < 6.18.22'
  - 'linux_kernel >= 6.19, < 6.19.12'
  - linux_kernel = 7.0
patched:
  - linux_kernel 6.19.12
published: '2026-05-01'
updated: '2026-07-04'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-31732'
references:
  - url: 'https://git.kernel.org/stable/c/16fdabe143fce2cbf89139677728e17e21b46c28'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a500e1837c4266ddb05b39b3e1cc71f49a43ffa5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f0cf9c7b7c281956cc0dec163132cd96f76e1d60'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fb4584d2b324c522404c733c65840a1a6519ada8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00162
epssPercentile: 0.0465
ingestedAt: '2026-07-04T12:56:09.363Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()

Since commit aab5c6f20023 ("gpio: set device type for GPIO chips"),
`gdev->dev.release` is unset.  As a result, the reference count to
`gdev->dev` isn't dropped on the error handling paths.

Drop the reference on errors.

Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:

   >>> Some memory allocation.  Go to ERR ZONE 1 on errors.
   >>> device_initialize().

   gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev->dev`.  The subsequent error handling paths
   shouldn't go through ERR ZONE 1 again which leads to double free.

   >>> Some initialization mainly on `gdev`.
   >>> The rest of initialization.  Go to ERR ZONE 2 on errors.
   >>> Chip registration success and exit.

   >>> ERR ZONE 2.  gpio_device_put() and exit.
   >>> ERR ZONE 1.

## Affected

- `linux_kernel >= 6.9, < 6.18.22`
- `linux_kernel >= 6.19, < 6.19.12`
- `linux_kernel = 7.0`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.19.12`