<?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:24:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45956 — drm/exynos: vidi: use priv-&gt;vidi_dev for ctx lookup in vidi_connection_ioctl()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-45956</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/exynos: vidi: use priv-&amp;gt;vidi_dev for ctx lookup in vidi_connection_ioctl()&lt;/p&gt;
&lt;p&gt;vidi_connection_ioctl() retrieves the driver_data from drm_dev-&amp;gt;dev to
obtain a struct vidi_context pointer. However, drm_dev-&amp;gt;dev is the
exynos-drm master device, and the driver_data contained therein is not
the vidi component device, but a completely different device.&lt;/p&gt;
&lt;p&gt;This can lead to various bugs, ranging from null pointer dereferences and
garbage value accesses to, in unlucky cases, out-of-bounds errors,
use-after-free errors, and more.&lt;/p&gt;
&lt;p&gt;To resolve this issue, we need to store/delete the vidi device pointer in
exynos_drm_private-&amp;gt;vidi_dev during bind/unbind, and then read this
exynos_drm_private-&amp;gt;vidi_dev within ioctl() to obtain the correct
struct vidi_context pointer.&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/exynos: vidi: use priv-&amp;gt;vidi_dev for ctx lookup in vidi_connection_ioctl()&lt;/p&gt;
&lt;p&gt;vidi_connection_ioctl() retrieves the driver_data from drm_dev-&amp;gt;dev to
obtain a struct vidi_context pointer. However, drm_dev-&amp;gt;dev is the
exynos-drm master device, and the driver_data contained therein is not
the vidi component device, but a completely different device.&lt;/p&gt;
&lt;p&gt;This can lead to various bugs, ranging from null pointer dereferences and
garbage value accesses to, in unlucky cases, out-of-bounds errors,
use-after-free errors, and more.&lt;/p&gt;
&lt;p&gt;To resolve this issue, we need to store/delete the vidi device pointer in
exynos_drm_private-&amp;gt;vidi_dev during bind/unbind, and then read this
exynos_drm_private-&amp;gt;vidi_dev within ioctl() to obtain the correct
struct vidi_context pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-45956</guid>
    </item>
  </channel>
</rss>
