{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.113-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.10-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port-\u003etty to NULL without holding port-\u003elock, racing with vcc_event() LDC callbacks that read port-\u003etty under port-\u003elock and then use tty-\u003eport. This can cause a use-after-free when the callback dereferences tty-\u003eport after cleanup has already destroyed and freed it.",
  "id": "DEBIAN-CVE-2026-98754",
  "modified": "2026-10-19T04:47:38.848316949Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-98754"
    }
  ],
  "upstream": [
    "CVE-2026-98754"
  ]
}