<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T13:52:42.218650+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2023-52485</id>
    <title>CVE-2023-52485 — drm/amd/display: Wake DMCUB before sending a command</title>
    <updated>2026-10-05T13:52:42.234377+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: Wake DMCUB before sending a command</p>
<p>[Why]
We can hang in place trying to send commands when the DMCUB isn't
powered on.</p>
<p>[How]
For functions that execute within a DC context or DC lock we can
wrap the direct calls to dm_execute_dmub_cmd/list with code that
exits idle power optimizations and reallows once we're done with
the command submission on success.</p>
<p>For DM direct submissions the DM will need to manage the enter/exit
sequencing manually.</p>
<p>We cannot invoke a DMCUB command directly within the DM execution
helper or we can deadlock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2023-52485"/>
  </entry>
</feed>
