<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 12:07:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68249 — most: usb: hdm_probe: Fix calling put_device() before device initialization</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68249</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;most: usb: hdm_probe: Fix calling put_device() before device initialization&lt;/p&gt;
&lt;p&gt;The early error path in hdm_probe() can jump to err_free_mdev before
&amp;amp;mdev-&amp;gt;dev has been initialized with device_initialize(). Calling
put_device(&amp;amp;mdev-&amp;gt;dev) there triggers a device core WARN and ends up
invoking kref_put(&amp;amp;kobj-&amp;gt;kref, kobject_release) on an uninitialized
kobject.&lt;/p&gt;
&lt;p&gt;In this path the private struct was only kmalloc&amp;#39;ed and the intended
release is effectively kfree(mdev) anyway, so free it directly instead
of calling put_device() on an uninitialized device.&lt;/p&gt;
&lt;p&gt;This removes the WARNING and fixes the pre-initialization error path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;most: usb: hdm_probe: Fix calling put_device() before device initialization&lt;/p&gt;
&lt;p&gt;The early error path in hdm_probe() can jump to err_free_mdev before
&amp;amp;mdev-&amp;gt;dev has been initialized with device_initialize(). Calling
put_device(&amp;amp;mdev-&amp;gt;dev) there triggers a device core WARN and ends up
invoking kref_put(&amp;amp;kobj-&amp;gt;kref, kobject_release) on an uninitialized
kobject.&lt;/p&gt;
&lt;p&gt;In this path the private struct was only kmalloc&amp;#39;ed and the intended
release is effectively kfree(mdev) anyway, so free it directly instead
of calling put_device() on an uninitialized device.&lt;/p&gt;
&lt;p&gt;This removes the WARNING and fixes the pre-initialization error path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68249</guid>
    </item>
  </channel>
</rss>
