{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.5-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  pinctrl: spacemit: fix NULL check in spacemit_pin_set_config  spacemit_pin_set_config() looks up the per-pin descriptor with spacemit_get_pin() then checks the wrong variable for failure:  \tconst struct spacemit_pin *spin = spacemit_get_pin(pctrl, pin); \t... \tif (!pin) \t\treturn -EINVAL;  \treg = spacemit_pin_to_reg(pctrl, spin-\u003epin);  pin is an unsigned int pin id, where 0 (GPIO_0 / gmac0_rxdv on K3) is a valid pin, so rejecting it here drops the PAD config write for the first pin of every group. On K3 Pico-ITX the GMAC RGMII group lists pin 0 as its first entry, so its drive-strength / bias configuration was silently ignored.  The intended guard is against spacemit_get_pin() returning NULL when the pin id isn't in the SoC's pin table. Check spin instead, which both restores PAD setup for pin 0 and prevents a NULL deref on spin-\u003epin.",
  "id": "DEBIAN-CVE-2026-80648",
  "modified": "2026-09-14T16:47:30.363657192Z",
  "published": "2026-08-28T08:16:49.800Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-80648"
    }
  ],
  "upstream": [
    "CVE-2026-80648"
  ]
}