<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 17:34:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50426 — remoteproc: imx_dsp_rproc: Add mutex protection for workqueue</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-50426</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;remoteproc: imx_dsp_rproc: Add mutex protection for workqueue&lt;/p&gt;
&lt;p&gt;The workqueue may execute late even after remoteproc is stopped or
stopping, some resources (rpmsg device and endpoint) have been
released in rproc_stop_subdevices(), then rproc_vq_interrupt()
accessing these resources will cause kennel dump.&lt;/p&gt;
&lt;p&gt;Call trace:
 virtqueue_add_split+0x1ac/0x560
 virtqueue_add_inbuf+0x4c/0x60
 rpmsg_recv_done+0x15c/0x294
 vring_interrupt+0x6c/0xa4
 rproc_vq_interrupt+0x30/0x50
 imx_dsp_rproc_vq_work+0x24/0x40 [imx_dsp_rproc]
 process_one_work+0x1d0/0x354
 worker_thread+0x13c/0x470
 kthread+0x154/0x160
 ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;Add mutex protection in imx_dsp_rproc_vq_work(), if the state is
not running, then just skip calling rproc_vq_interrupt().&lt;/p&gt;
&lt;p&gt;Also the flush workqueue operation can&amp;#39;t be added in rproc stop
for the same reason. The call sequence is&lt;/p&gt;
&lt;p&gt;rproc_shutdown
-&amp;gt; rproc_stop
   -&amp;gt;rproc_stop_subdevices
   -&amp;gt;rproc-&amp;gt;ops-&amp;gt;stop()
     -&amp;gt;imx_dsp_rproc_stop
       -&amp;gt;flush_work
         -&amp;gt; rproc_vq_interrupt&lt;/p&gt;
&lt;p&gt;The resource needed by rproc_vq_interrupt has been released in
rproc_stop_subdevices, so flush_work is not safe to be called in
imx_dsp_rproc_stop.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;remoteproc: imx_dsp_rproc: Add mutex protection for workqueue&lt;/p&gt;
&lt;p&gt;The workqueue may execute late even after remoteproc is stopped or
stopping, some resources (rpmsg device and endpoint) have been
released in rproc_stop_subdevices(), then rproc_vq_interrupt()
accessing these resources will cause kennel dump.&lt;/p&gt;
&lt;p&gt;Call trace:
 virtqueue_add_split+0x1ac/0x560
 virtqueue_add_inbuf+0x4c/0x60
 rpmsg_recv_done+0x15c/0x294
 vring_interrupt+0x6c/0xa4
 rproc_vq_interrupt+0x30/0x50
 imx_dsp_rproc_vq_work+0x24/0x40 [imx_dsp_rproc]
 process_one_work+0x1d0/0x354
 worker_thread+0x13c/0x470
 kthread+0x154/0x160
 ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;Add mutex protection in imx_dsp_rproc_vq_work(), if the state is
not running, then just skip calling rproc_vq_interrupt().&lt;/p&gt;
&lt;p&gt;Also the flush workqueue operation can&amp;#39;t be added in rproc stop
for the same reason. The call sequence is&lt;/p&gt;
&lt;p&gt;rproc_shutdown
-&amp;gt; rproc_stop
   -&amp;gt;rproc_stop_subdevices
   -&amp;gt;rproc-&amp;gt;ops-&amp;gt;stop()
     -&amp;gt;imx_dsp_rproc_stop
       -&amp;gt;flush_work
         -&amp;gt; rproc_vq_interrupt&lt;/p&gt;
&lt;p&gt;The resource needed by rproc_vq_interrupt has been released in
rproc_stop_subdevices, so flush_work is not safe to be called in
imx_dsp_rproc_stop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-50426</guid>
    </item>
  </channel>
</rss>
