<?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>Tue, 17 Nov 2026 10:04:39 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99103</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99103</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99103</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>EUVD-2026-396171</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396171</link>
      <description>EUVD-2026-396171</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396171</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99103</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99103</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;workqueue: Fix unbound pool lifetime for pending pwqs&lt;/p&gt;
&lt;p&gt;KASAN reports a use-after-free of an unbound worker_pool in
node_activate_pending_pwq():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120
  Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
  Workqueue:  0x0 (flush-8:0)
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x53/0x70
   print_report+0xce/0x610
   kasan_report+0xce/0x100
   _raw_spin_trylock+0x6d/0x120
   pwq_dec_nr_in_flight+0x4b4/0xcb0
   process_one_work+0x921/0x11a0
   worker_thread+0x4d0/0xd20
   kthread+0x2de/0x3c0
   ret_from_fork+0x3aa/0x620
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Allocated by task 311:
   alloc_pwq+0x439/0xca0
   apply_wqattrs_prepare+0x75e/0xd10
   apply_workqueue_attrs_locked+0x44/0xa0
   wq_nice_store+0x350/0x450&lt;/p&gt;
&lt;p&gt;Freed by task 0:
   kfree+0x127/0x3b0
   rcu_core+0x523/0x1780
   handle_softirqs+0x1b3/0x610&lt;/p&gt;
&lt;p&gt;Last potentially related work creation:
   put_unbound_pool+0x3f3/0x7d0
   pwq_release_workfn+0x494/0x8e0
   kthread_worker_fn+0x1ff/0x790&lt;/p&gt;
&lt;p&gt;Canceling the last inactive work skips pwq_dec_nr_active(), so an empty
pwq can remain on pending_pwqs when its refcnt reaches zero.
pwq_release_workfn() currently puts the pool before removing that pwq.
If this drops the last po…&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;workqueue: Fix unbound pool lifetime for pending pwqs&lt;/p&gt;
&lt;p&gt;KASAN reports a use-after-free of an unbound worker_pool in
node_activate_pending_pwq():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120
  Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
  Workqueue:  0x0 (flush-8:0)
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x53/0x70
   print_report+0xce/0x610
   kasan_report+0xce/0x100
   _raw_spin_trylock+0x6d/0x120
   pwq_dec_nr_in_flight+0x4b4/0xcb0
   process_one_work+0x921/0x11a0
   worker_thread+0x4d0/0xd20
   kthread+0x2de/0x3c0
   ret_from_fork+0x3aa/0x620
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Allocated by task 311:
   alloc_pwq+0x439/0xca0
   apply_wqattrs_prepare+0x75e/0xd10
   apply_workqueue_attrs_locked+0x44/0xa0
   wq_nice_store+0x350/0x450&lt;/p&gt;
&lt;p&gt;Freed by task 0:
   kfree+0x127/0x3b0
   rcu_core+0x523/0x1780
   handle_softirqs+0x1b3/0x610&lt;/p&gt;
&lt;p&gt;Last potentially related work creation:
   put_unbound_pool+0x3f3/0x7d0
   pwq_release_workfn+0x494/0x8e0
   kthread_worker_fn+0x1ff/0x790&lt;/p&gt;
&lt;p&gt;Canceling the last inactive work skips pwq_dec_nr_active(), so an empty
pwq can remain on pending_pwqs when its refcnt reaches zero.
pwq_release_workfn() currently puts the pool before removing that pwq.
If this drops the last po…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99103</guid>
    </item>
    <item>
      <title>GHSA-qwjv-757x-9f99</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qwjv-757x-9f99</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;workqueue: Fix unbound pool lifetime for pending pwqs&lt;/p&gt;
&lt;p&gt;KASAN reports a use-after-free of an unbound worker_pool in
node_activate_pending_pwq():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120
  Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
  Workqueue:  0x0 (flush-8:0)
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x53/0x70
   print_report+0xce/0x610
   kasan_report+0xce/0x100
   _raw_spin_trylock+0x6d/0x120
   pwq_dec_nr_in_flight+0x4b4/0xcb0
   process_one_work+0x921/0x11a0
   worker_thread+0x4d0/0xd20
   kthread+0x2de/0x3c0
   ret_from_fork+0x3aa/0x620
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Allocated by task 311:
   alloc_pwq+0x439/0xca0
   apply_wqattrs_prepare+0x75e/0xd10
   apply_workqueue_attrs_locked+0x44/0xa0
   wq_nice_store+0x350/0x450&lt;/p&gt;
&lt;p&gt;Freed by task 0:
   kfree+0x127/0x3b0
   rcu_core+0x523/0x1780
   handle_softirqs+0x1b3/0x610&lt;/p&gt;
&lt;p&gt;Last potentially related work creation:
   put_unbound_pool+0x3f3/0x7d0
   pwq_release_workfn+0x494/0x8e0
   kthread_worker_fn+0x1ff/0x790&lt;/p&gt;
&lt;p&gt;Canceling the last inactive work skips pwq_dec_nr_active(), so an empty
pwq can remain on pending_pwqs when its refcnt reaches zero.
pwq_release_workfn() currently puts the pool before removing that pwq.
If this drops the last po…&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;workqueue: Fix unbound pool lifetime for pending pwqs&lt;/p&gt;
&lt;p&gt;KASAN reports a use-after-free of an unbound worker_pool in
node_activate_pending_pwq():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120
  Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
  Workqueue:  0x0 (flush-8:0)
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x53/0x70
   print_report+0xce/0x610
   kasan_report+0xce/0x100
   _raw_spin_trylock+0x6d/0x120
   pwq_dec_nr_in_flight+0x4b4/0xcb0
   process_one_work+0x921/0x11a0
   worker_thread+0x4d0/0xd20
   kthread+0x2de/0x3c0
   ret_from_fork+0x3aa/0x620
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Allocated by task 311:
   alloc_pwq+0x439/0xca0
   apply_wqattrs_prepare+0x75e/0xd10
   apply_workqueue_attrs_locked+0x44/0xa0
   wq_nice_store+0x350/0x450&lt;/p&gt;
&lt;p&gt;Freed by task 0:
   kfree+0x127/0x3b0
   rcu_core+0x523/0x1780
   handle_softirqs+0x1b3/0x610&lt;/p&gt;
&lt;p&gt;Last potentially related work creation:
   put_unbound_pool+0x3f3/0x7d0
   pwq_release_workfn+0x494/0x8e0
   kthread_worker_fn+0x1ff/0x790&lt;/p&gt;
&lt;p&gt;Canceling the last inactive work skips pwq_dec_nr_active(), so an empty
pwq can remain on pending_pwqs when its refcnt reaches zero.
pwq_release_workfn() currently puts the pool before removing that pwq.
If this drops the last po…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qwjv-757x-9f99</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99103 — workqueue: Fix unbound pool lifetime for pending pwqs</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99103</link>
      <description>msrc_CVE-2026-99103</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99103</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99103</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99103</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 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a use-after-free of an unbound worker_pool in node_activate_pending_pwq():   BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120   Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318   CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy)   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014   Workqueue:  0x0 (flush-8:0)   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x53/0x70    print_report+0xce/0x610    kasan_report+0xce/0x100    _raw_spin_trylock+0x6d/0x120    pwq_dec_nr_in_flight+0x4b4/0xcb0    process_one_work+0x921/0x11a0    worker_thread+0x4d0/0xd20    kthread+0x2de/0x3c0    ret_from_fork+0x3aa/0x620    ret_from_fork_asm+0x1a/0x30    &amp;lt;/TASK&amp;gt;   Allocated by task 311:    alloc_pwq+0x439/0xca0    apply_wqattrs_prepare+0x75e/0xd10    apply_workqueue_attrs_locked+0x44/0xa0    wq_nice_store+0x350/0x450   Freed by task 0:    kfree+0x127/0x3b0    rcu_core+0x523/0x1780    handle_softirqs+0x1b3/0x610   Last potentially related work creation:    put_unbound_pool+0x3f3/0x7d0    pwq_release_workfn+0x494/0x8e0    kthread_worker_fn+0x1ff/0x790 Canceling the last inactive work skips pwq_dec_nr_active(), so an empty pwq can remain on pending_pwqs when its refcnt reaches zero. pwq_release_workfn() currently puts the pool before removing that pwq. If this drops the last pool refer…&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 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a use-after-free of an unbound worker_pool in node_activate_pending_pwq():   BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120   Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318   CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy)   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014   Workqueue:  0x0 (flush-8:0)   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x53/0x70    print_report+0xce/0x610    kasan_report+0xce/0x100    _raw_spin_trylock+0x6d/0x120    pwq_dec_nr_in_flight+0x4b4/0xcb0    process_one_work+0x921/0x11a0    worker_thread+0x4d0/0xd20    kthread+0x2de/0x3c0    ret_from_fork+0x3aa/0x620    ret_from_fork_asm+0x1a/0x30    &amp;lt;/TASK&amp;gt;   Allocated by task 311:    alloc_pwq+0x439/0xca0    apply_wqattrs_prepare+0x75e/0xd10    apply_workqueue_attrs_locked+0x44/0xa0    wq_nice_store+0x350/0x450   Freed by task 0:    kfree+0x127/0x3b0    rcu_core+0x523/0x1780    handle_softirqs+0x1b3/0x610   Last potentially related work creation:    put_unbound_pool+0x3f3/0x7d0    pwq_release_workfn+0x494/0x8e0    kthread_worker_fn+0x1ff/0x790 Canceling the last inactive work skips pwq_dec_nr_active(), so an empty pwq can remain on pending_pwqs when its refcnt reaches zero. pwq_release_workfn() currently puts the pool before removing that pwq. If this drops the last pool refer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99103</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4224</guid>
    </item>
  </channel>
</rss>
