{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.95-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.12-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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-\u003edev.release` is unset.  As a result, the reference count to `gdev-\u003edev` 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:     \u003e\u003e\u003e Some memory allocation.  Go to ERR ZONE 1 on errors.    \u003e\u003e\u003e device_initialize().     gpiodev_release() takes over the responsibility for freeing the    resources of `gdev-\u003edev`.  The subsequent error handling paths    shouldn't go through ERR ZONE 1 again which leads to double free.     \u003e\u003e\u003e Some initialization mainly on `gdev`.    \u003e\u003e\u003e The rest of initialization.  Go to ERR ZONE 2 on errors.    \u003e\u003e\u003e Chip registration success and exit.     \u003e\u003e\u003e ERR ZONE 2.  gpio_device_put() and exit.    \u003e\u003e\u003e ERR ZONE 1.",
  "id": "DEBIAN-CVE-2026-31732",
  "modified": "2026-09-14T16:47:28.859389824Z",
  "published": "2026-05-01T15:16:35.807Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31732"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31732"
  ]
}