{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind  hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -\u003e hci_proto_disconn_ind -\u003e l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted concurrently.  disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work.  Fix by using proto_lock to guard l2cap_data, in addition to hdev-\u003elock which is held in other access paths.",
  "id": "DEBIAN-CVE-2026-90256",
  "modified": "2026-09-23T03:47:42.029494913Z",
  "published": "2026-09-17T17:17:21.980Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90256"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-90256"
  ]
}