Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31732gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31732, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected aab5c6f200238ac45001bec3d5494fff8438a8dc – < a500e1837c4266ddb05b39b3e1cc71f49a43ffa5
    • affected aab5c6f200238ac45001bec3d5494fff8438a8dc – < f0cf9c7b7c281956cc0dec163132cd96f76e1d60
    • affected aab5c6f200238ac45001bec3d5494fff8438a8dc – < fb4584d2b324c522404c733c65840a1a6519ada8
    • affected aab5c6f200238ac45001bec3d5494fff8438a8dc – < 16fdabe143fce2cbf89139677728e17e21b46c28
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31732 badge
[![CVE-2026-31732](https://cveledger.app/badge/CVE-2026-31732.svg)](https://cveledger.app/cve/CVE-2026-31732)

Record last updated .