<?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 11:24:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38467 — drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38467</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: exynos7_drm_decon: add vblank check in IRQ handling&lt;/p&gt;
&lt;p&gt;If there&amp;#39;s support for another console device (such as a TTY serial),
the kernel occasionally panics during boot. The panic message and a
relevant snippet of the call stack is as follows:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 000000000000000
  Call trace:
    drm_crtc_handle_vblank+0x10/0x30 (P)
    decon_irq_handler+0x88/0xb4
    [...]&lt;/p&gt;
&lt;p&gt;Otherwise, the panics don&amp;#39;t happen. This indicates that it&amp;#39;s some sort
of race condition.&lt;/p&gt;
&lt;p&gt;Add a check to validate if the drm device can handle vblanks before
calling drm_crtc_handle_vblank() to avoid this.&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: exynos7_drm_decon: add vblank check in IRQ handling&lt;/p&gt;
&lt;p&gt;If there&amp;#39;s support for another console device (such as a TTY serial),
the kernel occasionally panics during boot. The panic message and a
relevant snippet of the call stack is as follows:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 000000000000000
  Call trace:
    drm_crtc_handle_vblank+0x10/0x30 (P)
    decon_irq_handler+0x88/0xb4
    [...]&lt;/p&gt;
&lt;p&gt;Otherwise, the panics don&amp;#39;t happen. This indicates that it&amp;#39;s some sort
of race condition.&lt;/p&gt;
&lt;p&gt;Add a check to validate if the drm device can handle vblanks before
calling drm_crtc_handle_vblank() to avoid this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38467</guid>
    </item>
  </channel>
</rss>
