<?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 02:51:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-02868</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-02868</link>
      <description>bdu:2025-02868</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-02868</guid>
    </item>
    <item>
      <title>EUVD-2026-309452</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309452</link>
      <description>EUVD-2026-309452</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309452</guid>
    </item>
    <item>
      <title>fkie_cve-2021-46942</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-46942</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring: fix shared sqpoll cancellation hangs&lt;/p&gt;
&lt;p&gt;[  736.982891] INFO: task iou-sqp-4294:4295 blocked for more than 122 seconds.
[  736.982897] Call Trace:
[  736.982901]  schedule+0x68/0xe0
[  736.982903]  io_uring_cancel_sqpoll+0xdb/0x110
[  736.982908]  io_sqpoll_cancel_cb+0x24/0x30
[  736.982911]  io_run_task_work_head+0x28/0x50
[  736.982913]  io_sq_thread+0x4e3/0x720&lt;/p&gt;
&lt;p&gt;We call io_uring_cancel_sqpoll() one by one for each ctx either in
sq_thread() itself or via task works, and it&amp;#39;s intended to cancel all
requests of a specified context. However the function uses per-task
counters to track the number of inflight requests, so it counts more
requests than available via currect io_uring ctx and goes to sleep for
them to appear (e.g. from IRQ), that will never happen.&lt;/p&gt;
&lt;p&gt;Cancel a bit more than before, i.e. all ctxs that share sqpoll
and continue to use shared counters. Don&amp;#39;t forget that we should not
remove ctx from the list before running that task_work sqpoll-cancel,
otherwise the function wouldn&amp;#39;t be able to find the context and will
hang.&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;io_uring: fix shared sqpoll cancellation hangs&lt;/p&gt;
&lt;p&gt;[  736.982891] INFO: task iou-sqp-4294:4295 blocked for more than 122 seconds.
[  736.982897] Call Trace:
[  736.982901]  schedule+0x68/0xe0
[  736.982903]  io_uring_cancel_sqpoll+0xdb/0x110
[  736.982908]  io_sqpoll_cancel_cb+0x24/0x30
[  736.982911]  io_run_task_work_head+0x28/0x50
[  736.982913]  io_sq_thread+0x4e3/0x720&lt;/p&gt;
&lt;p&gt;We call io_uring_cancel_sqpoll() one by one for each ctx either in
sq_thread() itself or via task works, and it&amp;#39;s intended to cancel all
requests of a specified context. However the function uses per-task
counters to track the number of inflight requests, so it counts more
requests than available via currect io_uring ctx and goes to sleep for
them to appear (e.g. from IRQ), that will never happen.&lt;/p&gt;
&lt;p&gt;Cancel a bit more than before, i.e. all ctxs that share sqpoll
and continue to use shared counters. Don&amp;#39;t forget that we should not
remove ctx from the list before running that task_work sqpoll-cancel,
otherwise the function wouldn&amp;#39;t be able to find the context and will
hang.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-46942</guid>
    </item>
    <item>
      <title>GHSA-rhmj-w54j-qcf6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rhmj-w54j-qcf6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring: fix shared sqpoll cancellation hangs&lt;/p&gt;
&lt;p&gt;[  736.982891] INFO: task iou-sqp-4294:4295 blocked for more than 122 seconds.
[  736.982897] Call Trace:
[  736.982901]  schedule+0x68/0xe0
[  736.982903]  io_uring_cancel_sqpoll+0xdb/0x110
[  736.982908]  io_sqpoll_cancel_cb+0x24/0x30
[  736.982911]  io_run_task_work_head+0x28/0x50
[  736.982913]  io_sq_thread+0x4e3/0x720&lt;/p&gt;
&lt;p&gt;We call io_uring_cancel_sqpoll() one by one for each ctx either in
sq_thread() itself or via task works, and it&amp;#39;s intended to cancel all
requests of a specified context. However the function uses per-task
counters to track the number of inflight requests, so it counts more
requests than available via currect io_uring ctx and goes to sleep for
them to appear (e.g. from IRQ), that will never happen.&lt;/p&gt;
&lt;p&gt;Cancel a bit more than before, i.e. all ctxs that share sqpoll
and continue to use shared counters. Don&amp;#39;t forget that we should not
remove ctx from the list before running that task_work sqpoll-cancel,
otherwise the function wouldn&amp;#39;t be able to find the context and will
hang.&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;io_uring: fix shared sqpoll cancellation hangs&lt;/p&gt;
&lt;p&gt;[  736.982891] INFO: task iou-sqp-4294:4295 blocked for more than 122 seconds.
[  736.982897] Call Trace:
[  736.982901]  schedule+0x68/0xe0
[  736.982903]  io_uring_cancel_sqpoll+0xdb/0x110
[  736.982908]  io_sqpoll_cancel_cb+0x24/0x30
[  736.982911]  io_run_task_work_head+0x28/0x50
[  736.982913]  io_sq_thread+0x4e3/0x720&lt;/p&gt;
&lt;p&gt;We call io_uring_cancel_sqpoll() one by one for each ctx either in
sq_thread() itself or via task works, and it&amp;#39;s intended to cancel all
requests of a specified context. However the function uses per-task
counters to track the number of inflight requests, so it counts more
requests than available via currect io_uring ctx and goes to sleep for
them to appear (e.g. from IRQ), that will never happen.&lt;/p&gt;
&lt;p&gt;Cancel a bit more than before, i.e. all ctxs that share sqpoll
and continue to use shared counters. Don&amp;#39;t forget that we should not
remove ctx from the list before running that task_work sqpoll-cancel,
otherwise the function wouldn&amp;#39;t be able to find the context and will
hang.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rhmj-w54j-qcf6</guid>
    </item>
    <item>
      <title>gsd-2021-46942</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-46942</link>
      <description>gsd-2021-46942</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-46942</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-46942</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46942</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring: fix shared sqpoll cancellation hangs [  736.982891] INFO: task iou-sqp-4294:4295 blocked for more than 122 seconds. [  736.982897] Call Trace: [  736.982901]  schedule+0x68/0xe0 [  736.982903]  io_uring_cancel_sqpoll+0xdb/0x110 [  736.982908]  io_sqpoll_cancel_cb+0x24/0x30 [  736.982911]  io_run_task_work_head+0x28/0x50 [  736.982913]  io_sq_thread+0x4e3/0x720 We call io_uring_cancel_sqpoll() one by one for each ctx either in sq_thread() itself or via task works, and it&amp;#39;s intended to cancel all requests of a specified context. However the function uses per-task counters to track the number of inflight requests, so it counts more requests than available via currect io_uring ctx and goes to sleep for them to appear (e.g. from IRQ), that will never happen. Cancel a bit more than before, i.e. all ctxs that share sqpoll and continue to use shared counters. Don&amp;#39;t forget that we should not remove ctx from the list before running that task_work sqpoll-cancel, otherwise the function wouldn&amp;#39;t be able to find the context and will hang.&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring: fix shared sqpoll cancellation hangs [  736.982891] INFO: task iou-sqp-4294:4295 blocked for more than 122 seconds. [  736.982897] Call Trace: [  736.982901]  schedule+0x68/0xe0 [  736.982903]  io_uring_cancel_sqpoll+0xdb/0x110 [  736.982908]  io_sqpoll_cancel_cb+0x24/0x30 [  736.982911]  io_run_task_work_head+0x28/0x50 [  736.982913]  io_sq_thread+0x4e3/0x720 We call io_uring_cancel_sqpoll() one by one for each ctx either in sq_thread() itself or via task works, and it&amp;#39;s intended to cancel all requests of a specified context. However the function uses per-task counters to track the number of inflight requests, so it counts more requests than available via currect io_uring ctx and goes to sleep for them to appear (e.g. from IRQ), that will never happen. Cancel a bit more than before, i.e. all ctxs that share sqpoll and continue to use shared counters. Don&amp;#39;t forget that we should not remove ctx from the list before running that task_work sqpoll-cancel, otherwise the function wouldn&amp;#39;t be able to find the context and will hang.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46942</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0500 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0500</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0500</guid>
    </item>
  </channel>
</rss>
