<?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-09-29T15:57:32.460706+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-2026-93175</id>
    <title>CVE-2026-93175 — drm/amd/display: Fix dangling pointer in CRTC reset function</title>
    <updated>2026-09-29T15:57:33.326721+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/amd/display: Fix dangling pointer in CRTC reset function</p>
<p>amdgpu_dm_crtc_reset_state() frees the old state before allocating
a new one. If kzalloc() fails, the function returns without updating
the state pointer, leaving a dangling pointer to already freed memory.</p>
<p>Fix this by allocating the new state first. On allocation failure, the
old state remains untouched and the function safely returns.</p>
<p>Found by Linux Verification Center (linuxtesting.org) with SVACE.</p>
<p>[adjust for movement around current amd-staging-drm-next]</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-93175"/>
  </entry>
</feed>
