PT-2026-151700

CVE-2026-99489

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾