{"id":"CVE-2026-99489","summary":"HID: wacom: Redesign shared sibling data lifecycle","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: wacom: Redesign shared sibling data lifecycle\n\nThe Wacom driver coordinates state between sibling interfaces of\nthe same physical device using a shared structure 'wacom_shared'\ninside 'wacom_hdev_data'.  The driver kept a volatile representative\npointer 'data-\u003edev' pointing to a sibling 'hid_device' for physical\npath comparisons during sibling matching.\n\nThis pointer management is fragile.  When the representative device\nis disconnected, wacom_remove_shared_data() failed to clear/update\n'data-\u003edev', leading to a Use-After-Free vulnerability when\nsubsequent sibling probes dereference the dangling 'data-\u003edev'\npointer.\n\nResolve this issue by redesigning the sibling data lifecycle:\n\n - Eliminate the volatile 'data-\u003edev' representative pointer\n   completely\n - Redesign 'wacom_hdev_data' to store stable static copies of the\n   required attributes upon first allocation: 'phys' path string,\n   'vendor', 'product' IDs and the sibling's 'device_type'\n - Use these static attributes for stable sibling matching in\n   wacom_are_sibling() and wacom_get_hdev_data()\n\nThis ensures sibling matching remains safe and stable even if\nindividual siblings are dynamically added or removed.\n\nTo secure the lifecycle against concurrent probe/disconnect races:\n\n - Switch kref_put() to kref_put_mutex() in\n   wacom_remove_shared_data() to serialize refcount drops with list\n   traversal and lookup\n - Modify wacom_release_shared_data() to assume the list lock is\n   already held\n\nAlso, do not accumulate the 'device_type' capability flag during\nsubsequent sibling probes.  Keeping only the first probed sibling's\ndevice_type exactly preserves the original sibling matching behavior\nwithout introducing side effects.","modified":"2026-11-19T17:01:23.739055523Z","published":"2026-11-19T14:43:29.533Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99489.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/321da540c4a2091c0e23b5f4ced0131a1c77d679"},{"type":"WEB","url":"https://git.kernel.org/stable/c/480c9cb14ae81f8e112ff83f8778b3d7b9324dc8"},{"type":"WEB","url":"https://git.kernel.org/stable/c/4eeb0a16f11c72a0a15e793310470418d1c2d3cd"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f1fb9f9087c76bca6de81aa38e1e9c820dc54744"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99489.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99489"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"4492efffffeb88d87e7aa74765f3c53b3a7dd40f"},{"fixed":"4eeb0a16f11c72a0a15e793310470418d1c2d3cd"},{"fixed":"321da540c4a2091c0e23b5f4ced0131a1c77d679"},{"fixed":"f1fb9f9087c76bca6de81aa38e1e9c820dc54744"},{"fixed":"480c9cb14ae81f8e112ff83f8778b3d7b9324dc8"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99489.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.35"},{"fixed":"6.12.117"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.61"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.2"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99489.json"}}],"schema_version":"1.9.2"}