<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T11:24:30.680680+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38467</id>
    <title>CVE-2025-38467 — drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling</title>
    <updated>2026-10-04T11:24:30.713971+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling</p>
<p>If there'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:</p>
<p>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
    [...]</p>
<p>Otherwise, the panics don't happen. This indicates that it's some sort
of race condition.</p>
<p>Add a check to validate if the drm device can handle vblanks before
calling drm_crtc_handle_vblank() to avoid this.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38467"/>
  </entry>
</feed>
