<?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-09-29T15:15:44.706345+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-53515</id>
    <title>CVE-2023-53515 — virtio-mmio: don't break lifecycle of vm_dev</title>
    <updated>2026-09-29T15:15:48.657932+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>virtio-mmio: don't break lifecycle of vm_dev</p>
<p>vm_dev has a separate lifecycle because it has a 'struct device'
embedded. Thus, having a release callback for it is correct.</p>
<p>Allocating the vm_dev struct with devres totally breaks this protection,
though. Instead of waiting for the vm_dev release callback, the memory
is freed when the platform_device is removed. Resulting in a
use-after-free when finally the callback is to be called.</p>
<p>To easily see the problem, compile the kernel with
CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs.</p>
<p>The fix is easy, don't use devres in this case.</p>
<p>Found during my research about object lifetime problems.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53515"/>
  </entry>
</feed>
