<?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-04T04:48:26.033015+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-40316</id>
    <title>CVE-2025-40316 — drm/mediatek: Fix device use-after-free on unbind</title>
    <updated>2026-10-04T04:48:26.034453+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/mediatek: Fix device use-after-free on unbind</p>
<p>A recent change fixed device reference leaks when looking up drm
platform device driver data during bind() but failed to remove a partial
fix which had been added by commit 80805b62ea5b ("drm/mediatek: Fix
kobject put for component sub-drivers").</p>
<p>This results in a reference imbalance on component bind() failures and
on unbind() which could lead to a user-after-free.</p>
<p>Make sure to only drop the references after retrieving the driver data
by effectively reverting the previous partial fix.</p>
<p>Note that holding a reference to a device does not prevent its driver
data from going away so there is no point in keeping the reference.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-40316"/>
  </entry>
</feed>
