<?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-28T09:26:26.769948+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-2022-50421</id>
    <title>CVE-2022-50421 — rpmsg: char: Avoid double destroy of default endpoint</title>
    <updated>2026-09-28T09:26:26.789889+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>rpmsg: char: Avoid double destroy of default endpoint</p>
<p>The rpmsg_dev_remove() in rpmsg_core is the place for releasing
this default endpoint.</p>
<p>So need to avoid destroying the default endpoint in
rpmsg_chrdev_eptdev_destroy(), this should be the same as
rpmsg_eptdev_release(). Otherwise there will be double destroy
issue that ept-&gt;refcount report warning:</p>
<p>refcount_t: underflow; use-after-free.</p>
<p>Call trace:
 refcount_warn_saturate+0xf8/0x150
 virtio_rpmsg_destroy_ept+0xd4/0xec
 rpmsg_dev_remove+0x60/0x70</p>
<p>The issue can be reproduced by stopping remoteproc before
closing the /dev/rpmsgX.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50421"/>
  </entry>
</feed>
