<?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>Wed, 30 Sep 2026 22:14:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-93283</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-93283</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i3c: master: Fix device_register() error path&lt;/p&gt;
&lt;p&gt;When device_register() fails in i3c_master_register_new_i3c_devs(),
put_device() is called to drop the reference taken by
device_register().  That drops the last reference, so the device&amp;#39;s
release callback i3c_device_release() runs and frees the i3c_device.&lt;/p&gt;
&lt;p&gt;Two problems follow from that:&lt;/p&gt;
&lt;p&gt;i3c_device_release() does WARN_ON(i3cdev-&amp;gt;desc), so it warns because
desc-&amp;gt;dev-&amp;gt;desc still points back at the descriptor.  Clear it before
calling put_device().&lt;/p&gt;
&lt;p&gt;After put_device() frees the i3c_device, desc-&amp;gt;dev is left pointing at
freed memory, so clear desc-&amp;gt;dev as well.  That prevents, for example,
i3c_master_unregister_i3c_devs() seeing desc-&amp;gt;dev as non-NULL and
dereferencing it.&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;i3c: master: Fix device_register() error path&lt;/p&gt;
&lt;p&gt;When device_register() fails in i3c_master_register_new_i3c_devs(),
put_device() is called to drop the reference taken by
device_register().  That drops the last reference, so the device&amp;#39;s
release callback i3c_device_release() runs and frees the i3c_device.&lt;/p&gt;
&lt;p&gt;Two problems follow from that:&lt;/p&gt;
&lt;p&gt;i3c_device_release() does WARN_ON(i3cdev-&amp;gt;desc), so it warns because
desc-&amp;gt;dev-&amp;gt;desc still points back at the descriptor.  Clear it before
calling put_device().&lt;/p&gt;
&lt;p&gt;After put_device() frees the i3c_device, desc-&amp;gt;dev is left pointing at
freed memory, so clear desc-&amp;gt;dev as well.  That prevents, for example,
i3c_master_unregister_i3c_devs() seeing desc-&amp;gt;dev as non-NULL and
dereferencing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-93283</guid>
    </item>
    <item>
      <title>GHSA-6m8v-mm29-jx9w</title>
      <link>https://db.gcve.eu/vuln/ghsa-6m8v-mm29-jx9w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i3c: master: Fix device_register() error path&lt;/p&gt;
&lt;p&gt;When device_register() fails in i3c_master_register_new_i3c_devs(),
put_device() is called to drop the reference taken by
device_register().  That drops the last reference, so the device&amp;#39;s
release callback i3c_device_release() runs and frees the i3c_device.&lt;/p&gt;
&lt;p&gt;Two problems follow from that:&lt;/p&gt;
&lt;p&gt;i3c_device_release() does WARN_ON(i3cdev-&amp;gt;desc), so it warns because
desc-&amp;gt;dev-&amp;gt;desc still points back at the descriptor.  Clear it before
calling put_device().&lt;/p&gt;
&lt;p&gt;After put_device() frees the i3c_device, desc-&amp;gt;dev is left pointing at
freed memory, so clear desc-&amp;gt;dev as well.  That prevents, for example,
i3c_master_unregister_i3c_devs() seeing desc-&amp;gt;dev as non-NULL and
dereferencing it.&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;i3c: master: Fix device_register() error path&lt;/p&gt;
&lt;p&gt;When device_register() fails in i3c_master_register_new_i3c_devs(),
put_device() is called to drop the reference taken by
device_register().  That drops the last reference, so the device&amp;#39;s
release callback i3c_device_release() runs and frees the i3c_device.&lt;/p&gt;
&lt;p&gt;Two problems follow from that:&lt;/p&gt;
&lt;p&gt;i3c_device_release() does WARN_ON(i3cdev-&amp;gt;desc), so it warns because
desc-&amp;gt;dev-&amp;gt;desc still points back at the descriptor.  Clear it before
calling put_device().&lt;/p&gt;
&lt;p&gt;After put_device() frees the i3c_device, desc-&amp;gt;dev is left pointing at
freed memory, so clear desc-&amp;gt;dev as well.  That prevents, for example,
i3c_master_unregister_i3c_devs() seeing desc-&amp;gt;dev as non-NULL and
dereferencing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6m8v-mm29-jx9w</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93283</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-93283</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 211 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix device_register() error path When device_register() fails in i3c_master_register_new_i3c_devs(), put_device() is called to drop the reference taken by device_register().  That drops the last reference, so the device&amp;#39;s release callback i3c_device_release() runs and frees the i3c_device. Two problems follow from that: i3c_device_release() does WARN_ON(i3cdev-&amp;gt;desc), so it warns because desc-&amp;gt;dev-&amp;gt;desc still points back at the descriptor.  Clear it before calling put_device(). After put_device() frees the i3c_device, desc-&amp;gt;dev is left pointing at freed memory, so clear desc-&amp;gt;dev as well.  That prevents, for example, i3c_master_unregister_i3c_devs() seeing desc-&amp;gt;dev as non-NULL and dereferencing it.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 211 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix device_register() error path When device_register() fails in i3c_master_register_new_i3c_devs(), put_device() is called to drop the reference taken by device_register().  That drops the last reference, so the device&amp;#39;s release callback i3c_device_release() runs and frees the i3c_device. Two problems follow from that: i3c_device_release() does WARN_ON(i3cdev-&amp;gt;desc), so it warns because desc-&amp;gt;dev-&amp;gt;desc still points back at the descriptor.  Clear it before calling put_device(). After put_device() frees the i3c_device, desc-&amp;gt;dev is left pointing at freed memory, so clear desc-&amp;gt;dev as well.  That prevents, for example, i3c_master_unregister_i3c_devs() seeing desc-&amp;gt;dev as non-NULL and dereferencing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-93283</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
