{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.88-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.11-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del()  l2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer and id_addr_timer while holding conn-\u003elock. However, the work functions l2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire conn-\u003elock, creating a potential AB-BA deadlock if the work is already executing when l2cap_conn_del() takes the lock.  Move the work cancellations before acquiring conn-\u003elock and use disable_delayed_work_sync() to additionally prevent the works from being rearmed after cancellation, consistent with the pattern used in hci_conn_del().",
  "id": "DEBIAN-CVE-2026-31499",
  "modified": "2026-09-14T16:47:31.115961886Z",
  "published": "2026-04-22T14:16:48.283Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31499"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31499"
  ]
}