<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T17:53:23.059025+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-43305</id>
    <title>CVE-2026-43305 — drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path</title>
    <updated>2026-09-30T17:53:23.068398+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 mismatched unlock for DMUB HW lock in HWSS fast path</p>
<p>[Why]
The evaluation for whether we need to use the DMUB HW lock isn't the
same as whether we need to unlock which results in a hang when the
fast path is used for ASIC without FAMS support.</p>
<p>[How]
Store a flag that indicates whether we should use the lock and use
that same flag to specify whether unlocking is needed.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-43305"/>
  </entry>
</feed>
