<?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 17:15:25 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04897</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04897</link>
      <description>bdu:2026-04897</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04897</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0587 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</link>
      <description>certfr-2025-avi-0587</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0587</guid>
    </item>
    <item>
      <title>EUVD-2026-320347</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320347</link>
      <description>EUVD-2026-320347</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320347</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50045</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50045</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/pci: Fix get_phb_number() locking&lt;/p&gt;
&lt;p&gt;The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
warning on some systems:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper
  preempt_count: 1, expected: 0
  RCU nest depth: 0, expected: 0
  1 lock held by swapper/1:
   #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220
  Preemption disabled at:
  [&amp;lt;00000000&amp;gt;] 0x0
  CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1
  Call Trace:
  [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)
  [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8
  [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec
  [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4
  [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220
  [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784
  [d101de50] [c140852c] discover_phbs+0x30/0x4c
  [d101de60] [c0007fd4] do_one_initcall+0x94/0x344
  [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c
  [d101df10] [c00086e0] kernel_init+0x34/0x160
  [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64&lt;/p&gt;
&lt;p&gt;This is because pcibios_alloc_controller() holds hose_spinlock but
of_alias_get_id() takes of_mutex which can sleep.&lt;/p&gt;
&lt;p&gt;The hose_spinlock protects the phb_bitmap, and also the hose_list, but
it doesn&amp;#39;t need to be held while get_phb_number() calls the…&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;powerpc/pci: Fix get_phb_number() locking&lt;/p&gt;
&lt;p&gt;The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
warning on some systems:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper
  preempt_count: 1, expected: 0
  RCU nest depth: 0, expected: 0
  1 lock held by swapper/1:
   #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220
  Preemption disabled at:
  [&amp;lt;00000000&amp;gt;] 0x0
  CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1
  Call Trace:
  [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)
  [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8
  [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec
  [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4
  [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220
  [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784
  [d101de50] [c140852c] discover_phbs+0x30/0x4c
  [d101de60] [c0007fd4] do_one_initcall+0x94/0x344
  [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c
  [d101df10] [c00086e0] kernel_init+0x34/0x160
  [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64&lt;/p&gt;
&lt;p&gt;This is because pcibios_alloc_controller() holds hose_spinlock but
of_alias_get_id() takes of_mutex which can sleep.&lt;/p&gt;
&lt;p&gt;The hose_spinlock protects the phb_bitmap, and also the hose_list, but
it doesn&amp;#39;t need to be held while get_phb_number() calls the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50045</guid>
    </item>
    <item>
      <title>GHSA-752v-r57r-j98p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-752v-r57r-j98p</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/pci: Fix get_phb_number() locking&lt;/p&gt;
&lt;p&gt;The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
warning on some systems:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper
  preempt_count: 1, expected: 0
  RCU nest depth: 0, expected: 0
  1 lock held by swapper/1:
   #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220
  Preemption disabled at:
  [&amp;lt;00000000&amp;gt;] 0x0
  CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1
  Call Trace:
  [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)
  [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8
  [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec
  [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4
  [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220
  [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784
  [d101de50] [c140852c] discover_phbs+0x30/0x4c
  [d101de60] [c0007fd4] do_one_initcall+0x94/0x344
  [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c
  [d101df10] [c00086e0] kernel_init+0x34/0x160
  [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64&lt;/p&gt;
&lt;p&gt;This is because pcibios_alloc_controller() holds hose_spinlock but
of_alias_get_id() takes of_mutex which can sleep.&lt;/p&gt;
&lt;p&gt;The hose_spinlock protects the phb_bitmap, and also the hose_list, but
it doesn&amp;#39;t need to be held while get_phb_number() calls the…&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;powerpc/pci: Fix get_phb_number() locking&lt;/p&gt;
&lt;p&gt;The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
warning on some systems:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper
  preempt_count: 1, expected: 0
  RCU nest depth: 0, expected: 0
  1 lock held by swapper/1:
   #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220
  Preemption disabled at:
  [&amp;lt;00000000&amp;gt;] 0x0
  CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1
  Call Trace:
  [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)
  [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8
  [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec
  [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4
  [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220
  [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784
  [d101de50] [c140852c] discover_phbs+0x30/0x4c
  [d101de60] [c0007fd4] do_one_initcall+0x94/0x344
  [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c
  [d101df10] [c00086e0] kernel_init+0x34/0x160
  [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64&lt;/p&gt;
&lt;p&gt;This is because pcibios_alloc_controller() holds hose_spinlock but
of_alias_get_id() takes of_mutex which can sleep.&lt;/p&gt;
&lt;p&gt;The hose_spinlock protects the phb_bitmap, and also the hose_list, but
it doesn&amp;#39;t need to be held while get_phb_number() calls the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-752v-r57r-j98p</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02264-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02264-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:02264-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50045</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50045</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 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/pci: Fix get_phb_number() locking The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP warning on some systems:   BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper   preempt_count: 1, expected: 0   RCU nest depth: 0, expected: 0   1 lock held by swapper/1:    #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220   Preemption disabled at:   [&amp;lt;00000000&amp;gt;] 0x0   CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1   Call Trace:   [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)   [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8   [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec   [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4   [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220   [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784   [d101de50] [c140852c] discover_phbs+0x30/0x4c   [d101de60] [c0007fd4] do_one_initcall+0x94/0x344   [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c   [d101df10] [c00086e0] kernel_init+0x34/0x160   [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64 This is because pcibios_alloc_controller() holds hose_spinlock but of_alias_get_id() takes of_mutex which can sleep. The hose_spinlock protects the phb_bitmap, and also the hose_list, but it doesn&amp;#39;t need to be held while get_phb_number() calls the OF ro…&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 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/pci: Fix get_phb_number() locking The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP warning on some systems:   BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper   preempt_count: 1, expected: 0   RCU nest depth: 0, expected: 0   1 lock held by swapper/1:    #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220   Preemption disabled at:   [&amp;lt;00000000&amp;gt;] 0x0   CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1   Call Trace:   [d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)   [d101dcb0] [c0093b70] __might_resched+0x258/0x2a8   [d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec   [d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4   [d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220   [d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784   [d101de50] [c140852c] discover_phbs+0x30/0x4c   [d101de60] [c0007fd4] do_one_initcall+0x94/0x344   [d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c   [d101df10] [c00086e0] kernel_init+0x34/0x160   [d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64 This is because pcibios_alloc_controller() holds hose_spinlock but of_alias_get_id() takes of_mutex which can sleep. The hose_spinlock protects the phb_bitmap, and also the hose_list, but it doesn&amp;#39;t need to be held while get_phb_number() calls the OF ro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50045</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
