<?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://cve.radiocsirt.org</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, 02 Oct 2026 23:32:23 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-64595 — CVE-2026-64595 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64595</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-64595</guid>
    </item>
    <item>
      <title>EUVD-2026-353445</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353445</link>
      <description>EUVD-2026-353445</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353445</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64595</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64595</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()&lt;/p&gt;
&lt;p&gt;hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:&lt;/p&gt;
&lt;p&gt;INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);
    schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));&lt;/p&gt;
&lt;p&gt;cfg_setup() dereferences drvdata.hdev to issue MCU command requests.
hid_go_cfg_remove() tears down sysfs and stops the HID device, but
never drains the delayed work.  If the device is unbound within the
2 ms scheduling delay (a probe failure rolling back via remove, or a
fast rmmod after probe), the work fires after hid_destroy_device()
has dropped its reference and released the underlying hdev struct,
leaving cfg_setup() with a stale drvdata.hdev pointer.&lt;/p&gt;
&lt;p&gt;Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove()
already calls cancel_delayed_work_sync() on its analogous work, and
drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel
must come before guard(mutex)(&amp;amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.&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: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()&lt;/p&gt;
&lt;p&gt;hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:&lt;/p&gt;
&lt;p&gt;INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);
    schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));&lt;/p&gt;
&lt;p&gt;cfg_setup() dereferences drvdata.hdev to issue MCU command requests.
hid_go_cfg_remove() tears down sysfs and stops the HID device, but
never drains the delayed work.  If the device is unbound within the
2 ms scheduling delay (a probe failure rolling back via remove, or a
fast rmmod after probe), the work fires after hid_destroy_device()
has dropped its reference and released the underlying hdev struct,
leaving cfg_setup() with a stale drvdata.hdev pointer.&lt;/p&gt;
&lt;p&gt;Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove()
already calls cancel_delayed_work_sync() on its analogous work, and
drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel
must come before guard(mutex)(&amp;amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64595</guid>
    </item>
    <item>
      <title>GHSA-ch5w-wf8g-jr9p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ch5w-wf8g-jr9p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()&lt;/p&gt;
&lt;p&gt;hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:&lt;/p&gt;
&lt;p&gt;INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);
    schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));&lt;/p&gt;
&lt;p&gt;cfg_setup() dereferences drvdata.hdev to issue MCU command requests.
hid_go_cfg_remove() tears down sysfs and stops the HID device, but
never drains the delayed work.  If the device is unbound within the
2 ms scheduling delay (a probe failure rolling back via remove, or a
fast rmmod after probe), the work fires after hid_destroy_device()
has dropped its reference and released the underlying hdev struct,
leaving cfg_setup() with a stale drvdata.hdev pointer.&lt;/p&gt;
&lt;p&gt;Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove()
already calls cancel_delayed_work_sync() on its analogous work, and
drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel
must come before guard(mutex)(&amp;amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.&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: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()&lt;/p&gt;
&lt;p&gt;hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it
to run 2 ms later:&lt;/p&gt;
&lt;p&gt;INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);
    schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2));&lt;/p&gt;
&lt;p&gt;cfg_setup() dereferences drvdata.hdev to issue MCU command requests.
hid_go_cfg_remove() tears down sysfs and stops the HID device, but
never drains the delayed work.  If the device is unbound within the
2 ms scheduling delay (a probe failure rolling back via remove, or a
fast rmmod after probe), the work fires after hid_destroy_device()
has dropped its reference and released the underlying hdev struct,
leaving cfg_setup() with a stale drvdata.hdev pointer.&lt;/p&gt;
&lt;p&gt;Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove()
already calls cancel_delayed_work_sync() on its analogous work, and
drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel
must come before guard(mutex)(&amp;amp;drvdata.cfg_mutex) because cfg_setup()
acquires that mutex; reversing the order would deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ch5w-wf8g-jr9p</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64595</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64595</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 90 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove() hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it to run 2 ms later:     INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);     schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2)); cfg_setup() dereferences drvdata.hdev to issue MCU command requests. hid_go_cfg_remove() tears down sysfs and stops the HID device, but never drains the delayed work.  If the device is unbound within the 2 ms scheduling delay (a probe failure rolling back via remove, or a fast rmmod after probe), the work fires after hid_destroy_device() has dropped its reference and released the underlying hdev struct, leaving cfg_setup() with a stale drvdata.hdev pointer. Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove() already calls cancel_delayed_work_sync() on its analogous work, and drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel must come before guard(mutex)(&amp;amp;drvdata.cfg_mutex) because cfg_setup() acquires that mutex; reversing the order would deadlock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 90 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove() hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it to run 2 ms later:     INIT_DELAYED_WORK(&amp;amp;drvdata.go_cfg_setup, &amp;amp;cfg_setup);     schedule_delayed_work(&amp;amp;drvdata.go_cfg_setup, msecs_to_jiffies(2)); cfg_setup() dereferences drvdata.hdev to issue MCU command requests. hid_go_cfg_remove() tears down sysfs and stops the HID device, but never drains the delayed work.  If the device is unbound within the 2 ms scheduling delay (a probe failure rolling back via remove, or a fast rmmod after probe), the work fires after hid_destroy_device() has dropped its reference and released the underlying hdev struct, leaving cfg_setup() with a stale drvdata.hdev pointer. Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove() already calls cancel_delayed_work_sync() on its analogous work, and drain go_cfg_setup at the top of hid_go_cfg_remove().  The cancel must come before guard(mutex)(&amp;amp;drvdata.cfg_mutex) because cfg_setup() acquires that mutex; reversing the order would deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64595</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2680 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2680</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.&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, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2680</guid>
    </item>
  </channel>
</rss>
