<?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>Thu, 08 Oct 2026 11:23:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-40108</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-40108</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-40108</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1075 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1075</link>
      <description>certfr-2025-avi-1075</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1075</guid>
    </item>
    <item>
      <title>EUVD-2026-314900</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314900</link>
      <description>EUVD-2026-314900</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314900</guid>
    </item>
    <item>
      <title>fkie_cve-2025-40108</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-40108</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;serial: qcom-geni: Fix blocked task&lt;/p&gt;
&lt;p&gt;Revert commit 1afa70632c39 (&amp;#34;serial: qcom-geni: Enable PM runtime for
serial driver&amp;#34;) and its dependent commit 86fa39dd6fb7 (&amp;#34;serial:
qcom-geni: Enable Serial on SA8255p Qualcomm platforms&amp;#34;) because the
first one causes regression - hang task on Qualcomm RB1 board (QRB2210)
and unable to use serial at all during normal boot:&lt;/p&gt;
&lt;p&gt;INFO: task kworker/u16:0:12 blocked for more than 42 seconds.
        Not tainted 6.17.0-rc1-00004-g53e760d89498 #9
  &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  task:kworker/u16:0   state:D stack:0     pid:12    tgid:12    ppid:2      task_flags:0x4208060 flags:0x00000010
  Workqueue: async async_run_entry_fn
  Call trace:
   __switch_to+0xe8/0x1a0 (T)
   __schedule+0x290/0x7c0
   schedule+0x34/0x118
   rpm_resume+0x14c/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   __pm_runtime_resume+0x50/0x9c
   __driver_probe_device+0x58/0x120
   driver_probe_device+0x3c/0x154
   __driver_attach_async_helper+0x4c/0xc0
   async_run_entry_fn+0x34/0xe0
   process_one_work+0x148/0x290
   worker_thread+0x2c4/0x3e0
   kthread+0x118/0x1c0
   ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;The issue was reported on 12th of August and was ignored by author of
commits introducing issue for two weeks.  Only after complaining author
produced a fix which did not work, so if original commits cannot be
reliably fixed for 5 we…&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;serial: qcom-geni: Fix blocked task&lt;/p&gt;
&lt;p&gt;Revert commit 1afa70632c39 (&amp;#34;serial: qcom-geni: Enable PM runtime for
serial driver&amp;#34;) and its dependent commit 86fa39dd6fb7 (&amp;#34;serial:
qcom-geni: Enable Serial on SA8255p Qualcomm platforms&amp;#34;) because the
first one causes regression - hang task on Qualcomm RB1 board (QRB2210)
and unable to use serial at all during normal boot:&lt;/p&gt;
&lt;p&gt;INFO: task kworker/u16:0:12 blocked for more than 42 seconds.
        Not tainted 6.17.0-rc1-00004-g53e760d89498 #9
  &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  task:kworker/u16:0   state:D stack:0     pid:12    tgid:12    ppid:2      task_flags:0x4208060 flags:0x00000010
  Workqueue: async async_run_entry_fn
  Call trace:
   __switch_to+0xe8/0x1a0 (T)
   __schedule+0x290/0x7c0
   schedule+0x34/0x118
   rpm_resume+0x14c/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   __pm_runtime_resume+0x50/0x9c
   __driver_probe_device+0x58/0x120
   driver_probe_device+0x3c/0x154
   __driver_attach_async_helper+0x4c/0xc0
   async_run_entry_fn+0x34/0xe0
   process_one_work+0x148/0x290
   worker_thread+0x2c4/0x3e0
   kthread+0x118/0x1c0
   ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;The issue was reported on 12th of August and was ignored by author of
commits introducing issue for two weeks.  Only after complaining author
produced a fix which did not work, so if original commits cannot be
reliably fixed for 5 we…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-40108</guid>
    </item>
    <item>
      <title>GHSA-wqc8-4945-8xxr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wqc8-4945-8xxr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;serial: qcom-geni: Fix blocked task&lt;/p&gt;
&lt;p&gt;Revert commit 1afa70632c39 (&amp;#34;serial: qcom-geni: Enable PM runtime for
serial driver&amp;#34;) and its dependent commit 86fa39dd6fb7 (&amp;#34;serial:
qcom-geni: Enable Serial on SA8255p Qualcomm platforms&amp;#34;) because the
first one causes regression - hang task on Qualcomm RB1 board (QRB2210)
and unable to use serial at all during normal boot:&lt;/p&gt;
&lt;p&gt;INFO: task kworker/u16:0:12 blocked for more than 42 seconds.
        Not tainted 6.17.0-rc1-00004-g53e760d89498 #9
  &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  task:kworker/u16:0   state:D stack:0     pid:12    tgid:12    ppid:2      task_flags:0x4208060 flags:0x00000010
  Workqueue: async async_run_entry_fn
  Call trace:
   __switch_to+0xe8/0x1a0 (T)
   __schedule+0x290/0x7c0
   schedule+0x34/0x118
   rpm_resume+0x14c/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   __pm_runtime_resume+0x50/0x9c
   __driver_probe_device+0x58/0x120
   driver_probe_device+0x3c/0x154
   __driver_attach_async_helper+0x4c/0xc0
   async_run_entry_fn+0x34/0xe0
   process_one_work+0x148/0x290
   worker_thread+0x2c4/0x3e0
   kthread+0x118/0x1c0
   ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;The issue was reported on 12th of August and was ignored by author of
commits introducing issue for two weeks.  Only after complaining author
produced a fix which did not work, so if original commits cannot be
reliably fixed for 5 we…&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;serial: qcom-geni: Fix blocked task&lt;/p&gt;
&lt;p&gt;Revert commit 1afa70632c39 (&amp;#34;serial: qcom-geni: Enable PM runtime for
serial driver&amp;#34;) and its dependent commit 86fa39dd6fb7 (&amp;#34;serial:
qcom-geni: Enable Serial on SA8255p Qualcomm platforms&amp;#34;) because the
first one causes regression - hang task on Qualcomm RB1 board (QRB2210)
and unable to use serial at all during normal boot:&lt;/p&gt;
&lt;p&gt;INFO: task kworker/u16:0:12 blocked for more than 42 seconds.
        Not tainted 6.17.0-rc1-00004-g53e760d89498 #9
  &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.
  task:kworker/u16:0   state:D stack:0     pid:12    tgid:12    ppid:2      task_flags:0x4208060 flags:0x00000010
  Workqueue: async async_run_entry_fn
  Call trace:
   __switch_to+0xe8/0x1a0 (T)
   __schedule+0x290/0x7c0
   schedule+0x34/0x118
   rpm_resume+0x14c/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   rpm_resume+0x2a4/0x66c
   __pm_runtime_resume+0x50/0x9c
   __driver_probe_device+0x58/0x120
   driver_probe_device+0x3c/0x154
   __driver_attach_async_helper+0x4c/0xc0
   async_run_entry_fn+0x34/0xe0
   process_one_work+0x148/0x290
   worker_thread+0x2c4/0x3e0
   kthread+0x118/0x1c0
   ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;The issue was reported on 12th of August and was ignored by author of
commits introducing issue for two weeks.  Only after complaining author
produced a fix which did not work, so if original commits cannot be
reliably fixed for 5 we…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wqc8-4945-8xxr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40108</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40108</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 87 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: serial: qcom-geni: Fix blocked task Revert commit 1afa70632c39 (&amp;#34;serial: qcom-geni: Enable PM runtime for serial driver&amp;#34;) and its dependent commit 86fa39dd6fb7 (&amp;#34;serial: qcom-geni: Enable Serial on SA8255p Qualcomm platforms&amp;#34;) because the first one causes regression - hang task on Qualcomm RB1 board (QRB2210) and unable to use serial at all during normal boot:   INFO: task kworker/u16:0:12 blocked for more than 42 seconds.         Not tainted 6.17.0-rc1-00004-g53e760d89498 #9   &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.   task:kworker/u16:0   state:D stack:0     pid:12    tgid:12    ppid:2 task_flags:0x4208060 flags:0x00000010   Workqueue: async async_run_entry_fn   Call trace:    __switch_to+0xe8/0x1a0 (T)    __schedule+0x290/0x7c0    schedule+0x34/0x118    rpm_resume+0x14c/0x66c    rpm_resume+0x2a4/0x66c    rpm_resume+0x2a4/0x66c    rpm_resume+0x2a4/0x66c    __pm_runtime_resume+0x50/0x9c    __driver_probe_device+0x58/0x120    driver_probe_device+0x3c/0x154    __driver_attach_async_helper+0x4c/0xc0    async_run_entry_fn+0x34/0xe0    process_one_work+0x148/0x290    worker_thread+0x2c4/0x3e0    kthread+0x118/0x1c0    ret_from_fork+0x10/0x20 The issue was reported on 12th of August and was ignored by author of commits introducing issue for two weeks.  Only after complaining author produced a fix which did not work, so if original commits cannot be reliably fixed for 5 weeks, they…&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 87 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: serial: qcom-geni: Fix blocked task Revert commit 1afa70632c39 (&amp;#34;serial: qcom-geni: Enable PM runtime for serial driver&amp;#34;) and its dependent commit 86fa39dd6fb7 (&amp;#34;serial: qcom-geni: Enable Serial on SA8255p Qualcomm platforms&amp;#34;) because the first one causes regression - hang task on Qualcomm RB1 board (QRB2210) and unable to use serial at all during normal boot:   INFO: task kworker/u16:0:12 blocked for more than 42 seconds.         Not tainted 6.17.0-rc1-00004-g53e760d89498 #9   &amp;#34;echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs&amp;#34; disables this message.   task:kworker/u16:0   state:D stack:0     pid:12    tgid:12    ppid:2 task_flags:0x4208060 flags:0x00000010   Workqueue: async async_run_entry_fn   Call trace:    __switch_to+0xe8/0x1a0 (T)    __schedule+0x290/0x7c0    schedule+0x34/0x118    rpm_resume+0x14c/0x66c    rpm_resume+0x2a4/0x66c    rpm_resume+0x2a4/0x66c    rpm_resume+0x2a4/0x66c    __pm_runtime_resume+0x50/0x9c    __driver_probe_device+0x58/0x120    driver_probe_device+0x3c/0x154    __driver_attach_async_helper+0x4c/0xc0    async_run_entry_fn+0x34/0xe0    process_one_work+0x148/0x290    worker_thread+0x2c4/0x3e0    kthread+0x118/0x1c0    ret_from_fork+0x10/0x20 The issue was reported on 12th of August and was ignored by author of commits introducing issue for two weeks.  Only after complaining author produced a fix which did not work, so if original commits cannot be reliably fixed for 5 weeks, they…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40108</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2531 — Linux Kernel: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2531</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2531</guid>
    </item>
  </channel>
</rss>
