{
  "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.117-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.3.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  HID: wacom: Redesign shared sibling data lifecycle  The Wacom driver coordinates state between sibling interfaces of the same physical device using a shared structure 'wacom_shared' inside 'wacom_hdev_data'.  The driver kept a volatile representative pointer 'data-\u003edev' pointing to a sibling 'hid_device' for physical path comparisons during sibling matching.  This pointer management is fragile.  When the representative device is disconnected, wacom_remove_shared_data() failed to clear/update 'data-\u003edev', leading to a Use-After-Free vulnerability when subsequent sibling probes dereference the dangling 'data-\u003edev' pointer.  Resolve this issue by redesigning the sibling data lifecycle:   - Eliminate the volatile 'data-\u003edev' representative pointer    completely  - Redesign 'wacom_hdev_data' to store stable static copies of the    required attributes upon first allocation: 'phys' path string,    'vendor', 'product' IDs and the sibling's 'device_type'  - Use these static attributes for stable sibling matching in    wacom_are_sibling() and wacom_get_hdev_data()  This ensures sibling matching remains safe and stable even if individual siblings are dynamically added or removed.  To secure the lifecycle against concurrent probe/disconnect races:   - Switch kref_put() to kref_put_mutex() in    wacom_remove_shared_data() to serialize refcount drops with list    traversal and lookup  - Modify wacom_release_shared_data() to assume the list lock is    already held  Also, do not accumulate the 'device_type' capability flag during subsequent sibling probes.  Keeping only the first probed sibling's device_type exactly preserves the original sibling matching behavior without introducing side effects.",
  "id": "DEBIAN-CVE-2026-99489",
  "modified": "2026-11-20T04:47:26.571928794Z",
  "published": "2026-11-19T15:18:03.740Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99489"
    }
  ],
  "upstream": [
    "CVE-2026-99489"
  ]
}