<?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-03T05:53:41.425218+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-2024-53133</id>
    <title>CVE-2024-53133 — drm/amd/display: Handle dml allocation failure to avoid crash</title>
    <updated>2026-10-03T05:53:41.426840+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: Handle dml allocation failure to avoid crash</p>
<p>[Why]
In the case where a dml allocation fails for any reason, the
current state's dml contexts would no longer be valid. Then
subsequent calls dc_state_copy_internal would shallow copy
invalid memory and if the new state was released, a double
free would occur.</p>
<p>[How]
Reset dml pointers in new_state to NULL and avoid invalid
pointer</p>
<p>(cherry picked from commit bcafdc61529a48f6f06355d78eb41b3aeda5296c)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-53133"/>
  </entry>
</feed>
