{
  "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.11-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev-\u003etty_dev. If that registration fails, dev-\u003etty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev-\u003etty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev-\u003etty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
  "id": "DEBIAN-CVE-2026-99008",
  "modified": "2026-10-24T05:47:29.503382745Z",
  "published": "2026-10-23T13:17:23.290Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99008"
    }
  ],
  "upstream": [
    "CVE-2026-99008"
  ]
}