{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.105-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.10-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux-6.12"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.107-1~deb12u1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind  The \"trigger\" debugfs file has a hand-rolled -\u003ewrite handler (trigger_write()) that dereferences the per-device gpio_la_poll_priv. The file is created with debugfs_create_file_unsafe(), and the handler never takes a debugfs reference. Nothing keeps the object alive while the handler runs.  priv is allocated with devm_kzalloc(). devres frees it when the platform device is unbound. debugfs_create_file_unsafe() installs no full_proxy wrapper, so debugfs_remove_recursive() in gpio_la_poll_remove() does not wait for an in-flight trigger_write(). The blob_lock taken there does not help, because trigger_write() never takes it. A write that races an unbind therefore writes into freed memory:    trigger_write()                  gpio_la_poll_remove()     priv = m-\u003eprivate     buf = memdup_user()  [may sleep]                                      mutex_lock(\u0026priv-\u003eblob_lock)                                      debugfs_remove_recursive()  [no wait]                                      mutex_unlock(\u0026priv-\u003eblob_lock)                                    (remove returns; devres frees priv)     priv-\u003etrig_data = buf   \u003c-- use-after-free write     priv-\u003etrig_len  = count  The race is reachable by root via /sys/bus/platform/drivers/gpio-sloppy-logic-analyzer/unbind.  Create \"trigger\" with debugfs_create_file() instead. Its full_proxy wrapper makes debugfs_remove_recursive() drain any in-flight -\u003ewrite before it returns.  The use-after-free is confirmed under KASAN with a minimal reproducer of the same debugfs_create_file_unsafe() plus devm_kzalloc() pattern (available on request); it produces a slab-use-after-free write in the handler.",
  "id": "DEBIAN-CVE-2026-80563",
  "modified": "2026-09-19T21:47:23.838591267Z",
  "published": "2026-08-26T15:17:11.310Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-80563"
    }
  ],
  "upstream": [
    "CVE-2026-80563"
  ]
}