CVE-2026-99489: HID: wacom: Redesign shared sibling data lifecycle
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 'wacomshared' inside 'wacomhdevdata'. The driver kept a volatile representative pointer 'data->dev' pointing to a sibling 'hiddevice' for physical path comparisons during sibling matching.
This pointer management is fragile. When the representative device is disconnected, wacomremoveshareddata() 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 'wacomhdevdata' to store stable static copies of the required attributes upon first allocation: 'phys' path string, 'vendor', 'product' IDs and the sibling's 'devicetype' - Use these static attributes for stable sibling matching in wacomaresibling() and wacomgethdevdata()
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 krefput() to krefputmutex() in wacomremoveshareddata() to serialize refcount drops with list traversal and lookup - Modify wacomreleaseshareddata() to assume the list lock is already held
Also, do not accumulate the 'devicetype' capability flag during subsequent sibling probes. Keeping only the first probed sibling's devicetype exactly preserves the original sibling matching behavior without introducing side effects.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2