<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:03:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99489</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99489</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: wacom: Redesign shared sibling data lifecycle&lt;/p&gt;
&lt;p&gt;The Wacom driver coordinates state between sibling interfaces of
the same physical device using a shared structure &amp;#39;wacom_shared&amp;#39;
inside &amp;#39;wacom_hdev_data&amp;#39;.  The driver kept a volatile representative
pointer &amp;#39;data-&amp;gt;dev&amp;#39; pointing to a sibling &amp;#39;hid_device&amp;#39; for physical
path comparisons during sibling matching.&lt;/p&gt;
&lt;p&gt;This pointer management is fragile.  When the representative device
is disconnected, wacom_remove_shared_data() failed to clear/update
&amp;#39;data-&amp;gt;dev&amp;#39;, leading to a Use-After-Free vulnerability when
subsequent sibling probes dereference the dangling &amp;#39;data-&amp;gt;dev&amp;#39;
pointer.&lt;/p&gt;
&lt;p&gt;Resolve this issue by redesigning the sibling data lifecycle:&lt;/p&gt;
&lt;p&gt;- Eliminate the volatile &amp;#39;data-&amp;gt;dev&amp;#39; representative pointer
   completely
 - Redesign &amp;#39;wacom_hdev_data&amp;#39; to store stable static copies of the
   required attributes upon first allocation: &amp;#39;phys&amp;#39; path string,
   &amp;#39;vendor&amp;#39;, &amp;#39;product&amp;#39; IDs and the sibling&amp;#39;s &amp;#39;device_type&amp;#39;
 - Use these static attributes for stable sibling matching in
   wacom_are_sibling() and wacom_get_hdev_data()&lt;/p&gt;
&lt;p&gt;This ensures sibling matching remains safe and stable even if
individual siblings are dynamically added or removed.&lt;/p&gt;
&lt;p&gt;To secure the lifecycle against concurrent probe/disconnect races:&lt;/p&gt;
&lt;p&gt;- 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()…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: wacom: Redesign shared sibling data lifecycle&lt;/p&gt;
&lt;p&gt;The Wacom driver coordinates state between sibling interfaces of
the same physical device using a shared structure &amp;#39;wacom_shared&amp;#39;
inside &amp;#39;wacom_hdev_data&amp;#39;.  The driver kept a volatile representative
pointer &amp;#39;data-&amp;gt;dev&amp;#39; pointing to a sibling &amp;#39;hid_device&amp;#39; for physical
path comparisons during sibling matching.&lt;/p&gt;
&lt;p&gt;This pointer management is fragile.  When the representative device
is disconnected, wacom_remove_shared_data() failed to clear/update
&amp;#39;data-&amp;gt;dev&amp;#39;, leading to a Use-After-Free vulnerability when
subsequent sibling probes dereference the dangling &amp;#39;data-&amp;gt;dev&amp;#39;
pointer.&lt;/p&gt;
&lt;p&gt;Resolve this issue by redesigning the sibling data lifecycle:&lt;/p&gt;
&lt;p&gt;- Eliminate the volatile &amp;#39;data-&amp;gt;dev&amp;#39; representative pointer
   completely
 - Redesign &amp;#39;wacom_hdev_data&amp;#39; to store stable static copies of the
   required attributes upon first allocation: &amp;#39;phys&amp;#39; path string,
   &amp;#39;vendor&amp;#39;, &amp;#39;product&amp;#39; IDs and the sibling&amp;#39;s &amp;#39;device_type&amp;#39;
 - Use these static attributes for stable sibling matching in
   wacom_are_sibling() and wacom_get_hdev_data()&lt;/p&gt;
&lt;p&gt;This ensures sibling matching remains safe and stable even if
individual siblings are dynamically added or removed.&lt;/p&gt;
&lt;p&gt;To secure the lifecycle against concurrent probe/disconnect races:&lt;/p&gt;
&lt;p&gt;- 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()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99489</guid>
    </item>
    <item>
      <title>GHSA-572x-m765-7v76</title>
      <link>https://db.gcve.eu/vuln/ghsa-572x-m765-7v76</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: wacom: Redesign shared sibling data lifecycle&lt;/p&gt;
&lt;p&gt;The Wacom driver coordinates state between sibling interfaces of
the same physical device using a shared structure &amp;#39;wacom_shared&amp;#39;
inside &amp;#39;wacom_hdev_data&amp;#39;.  The driver kept a volatile representative
pointer &amp;#39;data-&amp;gt;dev&amp;#39; pointing to a sibling &amp;#39;hid_device&amp;#39; for physical
path comparisons during sibling matching.&lt;/p&gt;
&lt;p&gt;This pointer management is fragile.  When the representative device
is disconnected, wacom_remove_shared_data() failed to clear/update
&amp;#39;data-&amp;gt;dev&amp;#39;, leading to a Use-After-Free vulnerability when
subsequent sibling probes dereference the dangling &amp;#39;data-&amp;gt;dev&amp;#39;
pointer.&lt;/p&gt;
&lt;p&gt;Resolve this issue by redesigning the sibling data lifecycle:&lt;/p&gt;
&lt;p&gt;- Eliminate the volatile &amp;#39;data-&amp;gt;dev&amp;#39; representative pointer
   completely
 - Redesign &amp;#39;wacom_hdev_data&amp;#39; to store stable static copies of the
   required attributes upon first allocation: &amp;#39;phys&amp;#39; path string,
   &amp;#39;vendor&amp;#39;, &amp;#39;product&amp;#39; IDs and the sibling&amp;#39;s &amp;#39;device_type&amp;#39;
 - Use these static attributes for stable sibling matching in
   wacom_are_sibling() and wacom_get_hdev_data()&lt;/p&gt;
&lt;p&gt;This ensures sibling matching remains safe and stable even if
individual siblings are dynamically added or removed.&lt;/p&gt;
&lt;p&gt;To secure the lifecycle against concurrent probe/disconnect races:&lt;/p&gt;
&lt;p&gt;- 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()…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: wacom: Redesign shared sibling data lifecycle&lt;/p&gt;
&lt;p&gt;The Wacom driver coordinates state between sibling interfaces of
the same physical device using a shared structure &amp;#39;wacom_shared&amp;#39;
inside &amp;#39;wacom_hdev_data&amp;#39;.  The driver kept a volatile representative
pointer &amp;#39;data-&amp;gt;dev&amp;#39; pointing to a sibling &amp;#39;hid_device&amp;#39; for physical
path comparisons during sibling matching.&lt;/p&gt;
&lt;p&gt;This pointer management is fragile.  When the representative device
is disconnected, wacom_remove_shared_data() failed to clear/update
&amp;#39;data-&amp;gt;dev&amp;#39;, leading to a Use-After-Free vulnerability when
subsequent sibling probes dereference the dangling &amp;#39;data-&amp;gt;dev&amp;#39;
pointer.&lt;/p&gt;
&lt;p&gt;Resolve this issue by redesigning the sibling data lifecycle:&lt;/p&gt;
&lt;p&gt;- Eliminate the volatile &amp;#39;data-&amp;gt;dev&amp;#39; representative pointer
   completely
 - Redesign &amp;#39;wacom_hdev_data&amp;#39; to store stable static copies of the
   required attributes upon first allocation: &amp;#39;phys&amp;#39; path string,
   &amp;#39;vendor&amp;#39;, &amp;#39;product&amp;#39; IDs and the sibling&amp;#39;s &amp;#39;device_type&amp;#39;
 - Use these static attributes for stable sibling matching in
   wacom_are_sibling() and wacom_get_hdev_data()&lt;/p&gt;
&lt;p&gt;This ensures sibling matching remains safe and stable even if
individual siblings are dynamically added or removed.&lt;/p&gt;
&lt;p&gt;To secure the lifecycle against concurrent probe/disconnect races:&lt;/p&gt;
&lt;p&gt;- 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()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-572x-m765-7v76</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
