CVE-2026-99489

published 19 Nov 2026 · updated 21 Nov 2026

HID: wacom: Redesign shared sibling data lifecycle

4.6MediumCVSS 4.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f1fb9f9087c76bca6de81aa38e1e9c820dc54744, Kernel 321da540c4a2091c0e23b5f4ced0131a1c77d679, Kernel 480c9cb14ae81f8e112ff83f8778b3d7b9324dc8 and 4 more.

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->dev' 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->dev', leading to a Use-After-Free vulnerability when subsequent sibling probes dereference the dangling 'data->dev' pointer. Resolve this issue by redesigning the sibling data lifecycle: - Eliminate the volatile 'data->dev' 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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=4492efffffeb88d87e7aa74765f3c53b3a7dd40f <f1fb9f9087c76bca6de81aa38e1e9c820dc54744, >=4492efffffeb88d87e7aa74765f3c53b3a7dd40f <321da540c4a2091c0e23b5f4ced0131a1c77d679, >=4492efffffeb88d87e7aa74765f3c53b3a7dd40f <480c9cb14ae81f8e112ff83f8778b3d7b9324dc8, >=4492efffffeb88d87e7aa74765f3c53b3a7dd40f <4eeb0a16f11c72a0a15e793310470418d1c2d3cd, =2.6.35f1fb9f9087c76bca6de81aa38e1e9c820dc54744, 321da540c4a2091c0e23b5f4ced0131a1c77d679, 480c9cb14ae81f8e112ff83f8778b3d7b9324dc8, 4eeb0a16f11c72a0a15e793310470418d1c2d3cd
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=2.6.35 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99489 severity on Zeptric[![CVE-2026-99489](https://zeptric.io/badge/cve/CVE-2026-99489.svg)](https://zeptric.io/cve/CVE-2026-99489)