<?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>Sat, 03 Oct 2026 09:37:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03347</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03347</link>
      <description>bdu:2026-03347</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03347</guid>
    </item>
    <item>
      <title>EUVD-2026-311216</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311216</link>
      <description>EUVD-2026-311216</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311216</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50426</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50426</link>
      <description>&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;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/fkie_cve-2022-50426</guid>
    </item>
    <item>
      <title>GHSA-w4mq-qvfm-cqjm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w4mq-qvfm-cqjm</link>
      <description>&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;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/ghsa-w4mq-qvfm-cqjm</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50426</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50426</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: remoteproc: imx_dsp_rproc: Add mutex protection for workqueue 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. 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 Add mutex protection in imx_dsp_rproc_vq_work(), if the state is not running, then just skip calling rproc_vq_interrupt(). Also the flush workqueue operation can&amp;#39;t be added in rproc stop for the same reason. The call sequence is 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 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: remoteproc: imx_dsp_rproc: Add mutex protection for workqueue 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. 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 Add mutex protection in imx_dsp_rproc_vq_work(), if the state is not running, then just skip calling rproc_vq_interrupt(). Also the flush workqueue operation can&amp;#39;t be added in rproc stop for the same reason. The call sequence is 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 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/ubuntu-cve-2022-50426</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
