<?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>Sun, 04 Oct 2026 20:54:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49308 — extcon: Modify extcon device to be created after driver data is set</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49308</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;extcon: Modify extcon device to be created after driver data is set&lt;/p&gt;
&lt;p&gt;Currently, someone can invoke the sysfs such as state_show()
intermittently before dev_set_drvdata() is done.
And it can be a cause of kernel Oops because of edev is Null at that time.
So modified the driver registration to after setting drviver data.&lt;/p&gt;
&lt;p&gt;- Oops&amp;#39;s backtrace.&lt;/p&gt;
&lt;p&gt;Backtrace:
[&amp;lt;c067865c&amp;gt;] (state_show) from [&amp;lt;c05222e8&amp;gt;] (dev_attr_show)
[&amp;lt;c05222c0&amp;gt;] (dev_attr_show) from [&amp;lt;c02c66e0&amp;gt;] (sysfs_kf_seq_show)
[&amp;lt;c02c6648&amp;gt;] (sysfs_kf_seq_show) from [&amp;lt;c02c496c&amp;gt;] (kernfs_seq_show)
[&amp;lt;c02c4938&amp;gt;] (kernfs_seq_show) from [&amp;lt;c025e2a0&amp;gt;] (seq_read)
[&amp;lt;c025e11c&amp;gt;] (seq_read) from [&amp;lt;c02c50a0&amp;gt;] (kernfs_fop_read)
[&amp;lt;c02c5064&amp;gt;] (kernfs_fop_read) from [&amp;lt;c0231cac&amp;gt;] (__vfs_read)
[&amp;lt;c0231c5c&amp;gt;] (__vfs_read) from [&amp;lt;c0231ee0&amp;gt;] (vfs_read)
[&amp;lt;c0231e34&amp;gt;] (vfs_read) from [&amp;lt;c0232464&amp;gt;] (ksys_read)
[&amp;lt;c02323f0&amp;gt;] (ksys_read) from [&amp;lt;c02324fc&amp;gt;] (sys_read)
[&amp;lt;c02324e4&amp;gt;] (sys_read) from [&amp;lt;c00091d0&amp;gt;] (__sys_trace_return)&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;extcon: Modify extcon device to be created after driver data is set&lt;/p&gt;
&lt;p&gt;Currently, someone can invoke the sysfs such as state_show()
intermittently before dev_set_drvdata() is done.
And it can be a cause of kernel Oops because of edev is Null at that time.
So modified the driver registration to after setting drviver data.&lt;/p&gt;
&lt;p&gt;- Oops&amp;#39;s backtrace.&lt;/p&gt;
&lt;p&gt;Backtrace:
[&amp;lt;c067865c&amp;gt;] (state_show) from [&amp;lt;c05222e8&amp;gt;] (dev_attr_show)
[&amp;lt;c05222c0&amp;gt;] (dev_attr_show) from [&amp;lt;c02c66e0&amp;gt;] (sysfs_kf_seq_show)
[&amp;lt;c02c6648&amp;gt;] (sysfs_kf_seq_show) from [&amp;lt;c02c496c&amp;gt;] (kernfs_seq_show)
[&amp;lt;c02c4938&amp;gt;] (kernfs_seq_show) from [&amp;lt;c025e2a0&amp;gt;] (seq_read)
[&amp;lt;c025e11c&amp;gt;] (seq_read) from [&amp;lt;c02c50a0&amp;gt;] (kernfs_fop_read)
[&amp;lt;c02c5064&amp;gt;] (kernfs_fop_read) from [&amp;lt;c0231cac&amp;gt;] (__vfs_read)
[&amp;lt;c0231c5c&amp;gt;] (__vfs_read) from [&amp;lt;c0231ee0&amp;gt;] (vfs_read)
[&amp;lt;c0231e34&amp;gt;] (vfs_read) from [&amp;lt;c0232464&amp;gt;] (ksys_read)
[&amp;lt;c02323f0&amp;gt;] (ksys_read) from [&amp;lt;c02324fc&amp;gt;] (sys_read)
[&amp;lt;c02324e4&amp;gt;] (sys_read) from [&amp;lt;c00091d0&amp;gt;] (__sys_trace_return)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49308</guid>
    </item>
  </channel>
</rss>
