CVE-2026-99489

Source
https://cve.org/CVERecord?id=CVE-2026-99489
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99489.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99489
Downstream
Published
2026-11-19T14:43:29Z
Modified
2026-11-19T17:01:23Z
Summary
HID: wacom: Redesign shared sibling data lifecycle
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->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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99489.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

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"

Linux / Kernel

Package

Name
Kernel

Affected 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"