Skip to content
Threat Brief

← All advisories

CVE-2026-99489

Severity unknownNo known exploitationFix available

HID: wacom: Redesign shared sibling data lifecycle

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 4492efffffeb88d87e7aa74765f3c53b3a7dd40f before 321da540c4a2091c0e23b5f4ced0131a1c77d679321da540c4a2091c0e23b5f4ced0131a1c77d679CVE Program
LinuxLinuxfrom 4492efffffeb88d87e7aa74765f3c53b3a7dd40f before f1fb9f9087c76bca6de81aa38e1e9c820dc54744f1fb9f9087c76bca6de81aa38e1e9c820dc54744CVE Program
LinuxLinuxfrom 4492efffffeb88d87e7aa74765f3c53b3a7dd40f before 480c9cb14ae81f8e112ff83f8778b3d7b9324dc8480c9cb14ae81f8e112ff83f8778b3d7b9324dc8CVE Program
LinuxLinuxfrom 4492efffffeb88d87e7aa74765f3c53b3a7dd40f before 4eeb0a16f11c72a0a15e793310470418d1c2d3cd4eeb0a16f11c72a0a15e793310470418d1c2d3cdCVE Program
LinuxLinux2.6.35Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 2.6.35Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references