<?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-02T00:25:29.491318+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-2026-64447</id>
    <title>CVE-2026-64447 — staging: media: ipu7: fix double-free and use-after-free in error paths</title>
    <updated>2026-10-02T00:25:29.896775+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>staging: media: ipu7: fix double-free and use-after-free in error paths</p>
<p>In both ipu7_isys_init() and ipu7_psys_init(), pdata is allocated and
then passed to ipu7_bus_initialize_device(), which stores it in
adev-&gt;pdata. The ipu7_bus_release() function frees adev-&gt;pdata when the
device's reference count drops to zero.</p>
<p>Two error paths incorrectly call kfree(pdata) after the device teardown
has already freed it:</p>
<p>1. When ipu7_mmu_init() fails: put_device() is called, which drops the
   reference count to zero and triggers ipu7_bus_release() -&gt;
   kfree(pdata). The subsequent kfree(pdata) is a double-free.</p>
<p>2. When ipu7_bus_add_device() fails: it calls auxiliary_device_uninit()
   internally, which calls put_device() -&gt; ipu7_bus_release() -&gt;
   kfree(pdata). The subsequent kfree(pdata) is again a double-free.</p>
<p>Note that the kfree(pdata) when ipu7_bus_initialize_device() itself
fails is correct, because in that case auxiliary_device_init() failed
and the release function was never set up, so pdata must be freed
manually.</p>
<p>Additionally, the error code was not saved before calling put_device(),
causing ERR_CAST() to dereference the already-freed adev pointer when
constructing the return value. Fix this by saving the error from
dev_err_probe() before put_device() and returning ERR_PTR() instead.</p>
<p>Remove the redundant kfree(pdata) calls and fix the use-after-free in
the return values of the two affected error paths.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64447"/>
  </entry>
</feed>
