<?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>Wed, 30 Sep 2026 23:34:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53851 — drm/msm/dp: Drop aux devices together with DP controller</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53851</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;drm/msm/dp: Drop aux devices together with DP controller&lt;/p&gt;
&lt;p&gt;Using devres to depopulate the aux bus made sure that upon a probe
deferral the EDP panel device would be destroyed and recreated upon next
attempt.&lt;/p&gt;
&lt;p&gt;But the struct device which the devres is tied to is the DPUs
(drm_dev-&amp;gt;dev), which may be happen after the DP controller is torn
down.&lt;/p&gt;
&lt;p&gt;Indications of this can be seen in the commonly seen EDID-hexdump full
of zeros in the log, or the occasional/rare KASAN fault where the
panel&amp;#39;s attempt to read the EDID information causes a use after free on
DP resources.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s tempting to move the devres to the DP controller&amp;#39;s struct device,
but the resources used by the device(s) on the aux bus are explicitly
torn down in the error path. The KASAN-reported use-after-free also
remains, as the DP aux &amp;#34;module&amp;#34; explicitly frees its devres-allocated
memory in this code path.&lt;/p&gt;
&lt;p&gt;As such, explicitly depopulate the aux bus in the error path, and in the
component unbind path, to avoid these issues.&lt;/p&gt;
&lt;p&gt;Patchwork: https://patchwork.freedesktop.org/patch/542163/&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;drm/msm/dp: Drop aux devices together with DP controller&lt;/p&gt;
&lt;p&gt;Using devres to depopulate the aux bus made sure that upon a probe
deferral the EDP panel device would be destroyed and recreated upon next
attempt.&lt;/p&gt;
&lt;p&gt;But the struct device which the devres is tied to is the DPUs
(drm_dev-&amp;gt;dev), which may be happen after the DP controller is torn
down.&lt;/p&gt;
&lt;p&gt;Indications of this can be seen in the commonly seen EDID-hexdump full
of zeros in the log, or the occasional/rare KASAN fault where the
panel&amp;#39;s attempt to read the EDID information causes a use after free on
DP resources.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s tempting to move the devres to the DP controller&amp;#39;s struct device,
but the resources used by the device(s) on the aux bus are explicitly
torn down in the error path. The KASAN-reported use-after-free also
remains, as the DP aux &amp;#34;module&amp;#34; explicitly frees its devres-allocated
memory in this code path.&lt;/p&gt;
&lt;p&gt;As such, explicitly depopulate the aux bus in the error path, and in the
component unbind path, to avoid these issues.&lt;/p&gt;
&lt;p&gt;Patchwork: https://patchwork.freedesktop.org/patch/542163/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53851</guid>
    </item>
  </channel>
</rss>
