<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:20:40.891564+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99489</id>
    <title>CVE-2026-99489 — HID: wacom: Redesign shared sibling data lifecycle</title>
    <updated>2026-11-20T21:20:40.893046+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>HID: wacom: Redesign shared sibling data lifecycle</p>
<p>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-&gt;dev' pointing to a sibling 'hid_device' for physical
path comparisons during sibling matching.</p>
<p>This pointer management is fragile.  When the representative device
is disconnected, wacom_remove_shared_data() failed to clear/update
'data-&gt;dev', leading to a Use-After-Free vulnerability when
subsequent sibling probes dereference the dangling 'data-&gt;dev'
pointer.</p>
<p>Resolve this issue by redesigning the sibling data lifecycle:</p>
<p>- Eliminate the volatile 'data-&gt;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()</p>
<p>This ensures sibling matching remains safe and stable even if
individual siblings are dynamically added or removed.</p>
<p>To secure the lifecycle against concurrent probe/disconnect races:</p>
<p>- 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()…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99489"/>
  </entry>
</feed>
