<?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-04T01:51:28.051664+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-2023-52584</id>
    <title>CVE-2023-52584 — spmi: mediatek: Fix UAF on device remove</title>
    <updated>2026-10-04T01:51:28.233008+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, linux kernel</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>spmi: mediatek: Fix UAF on device remove</p>
<p>The pmif driver data that contains the clocks is allocated along with
spmi_controller.
On device remove, spmi_controller will be freed first, and then devres
, including the clocks, will be cleanup.
This leads to UAF because putting the clocks will access the clocks in
the pmif driver data, which is already freed along with spmi_controller.</p>
<p>This can be reproduced by enabling DEBUG_TEST_DRIVER_REMOVE and
building the kernel with KASAN.</p>
<p>Fix the UAF issue by using unmanaged clk_bulk_get() and putting the
clocks before freeing spmi_controller.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-52584"/>
  </entry>
</feed>
