<?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>Fri, 02 Oct 2026 19:53:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05940</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05940</link>
      <description>bdu:2026-05940</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05940</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — 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-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-310804</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310804</link>
      <description>EUVD-2026-310804</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310804</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49783</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49783</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fpu: Drop fpregs lock before inheriting FPU permissions&lt;/p&gt;
&lt;p&gt;Mike Galbraith reported the following against an old fork of preempt-rt
but the same issue also applies to the current preempt-rt tree.&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd
   preempt_count: 1, expected: 0
   RCU nest depth: 0, expected: 0
   Preemption disabled at:
   fpu_clone
   CPU: 6 PID: 1 Comm: systemd Tainted: G            E       (unreleased)
   Call Trace:
    &amp;lt;TASK&amp;gt;
    dump_stack_lvl
    ? fpu_clone
    __might_resched
    rt_spin_lock
    fpu_clone
    ? copy_thread
    ? copy_process
    ? shmem_alloc_inode
    ? kmem_cache_alloc
    ? kernel_clone
    ? __do_sys_clone
    ? do_syscall_64
    ? __x64_sys_rt_sigprocmask
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? exc_page_fault
    ? entry_SYSCALL_64_after_hwframe
    &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Mike says:&lt;/p&gt;
&lt;p&gt;The splat comes from fpu_inherit_perms() being called under fpregs_lock(),
  and us reaching the spin_lock_irq() therein due to fpu_state_size_dynamic()
  returning true despite static key __fpu_state_size_dynamic having never
  been enabled.&lt;/p&gt;
&lt;p&gt;Mike&amp;#39;s assessment looks correct. fpregs_lock on a PREEMPT_RT kernel disables
preemption so calling spin_lock_irq()…&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;x86/fpu: Drop fpregs lock before inheriting FPU permissions&lt;/p&gt;
&lt;p&gt;Mike Galbraith reported the following against an old fork of preempt-rt
but the same issue also applies to the current preempt-rt tree.&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd
   preempt_count: 1, expected: 0
   RCU nest depth: 0, expected: 0
   Preemption disabled at:
   fpu_clone
   CPU: 6 PID: 1 Comm: systemd Tainted: G            E       (unreleased)
   Call Trace:
    &amp;lt;TASK&amp;gt;
    dump_stack_lvl
    ? fpu_clone
    __might_resched
    rt_spin_lock
    fpu_clone
    ? copy_thread
    ? copy_process
    ? shmem_alloc_inode
    ? kmem_cache_alloc
    ? kernel_clone
    ? __do_sys_clone
    ? do_syscall_64
    ? __x64_sys_rt_sigprocmask
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? exc_page_fault
    ? entry_SYSCALL_64_after_hwframe
    &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Mike says:&lt;/p&gt;
&lt;p&gt;The splat comes from fpu_inherit_perms() being called under fpregs_lock(),
  and us reaching the spin_lock_irq() therein due to fpu_state_size_dynamic()
  returning true despite static key __fpu_state_size_dynamic having never
  been enabled.&lt;/p&gt;
&lt;p&gt;Mike&amp;#39;s assessment looks correct. fpregs_lock on a PREEMPT_RT kernel disables
preemption so calling spin_lock_irq()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49783</guid>
    </item>
    <item>
      <title>GHSA-g5p7-q8gg-6qmf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g5p7-q8gg-6qmf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fpu: Drop fpregs lock before inheriting FPU permissions&lt;/p&gt;
&lt;p&gt;Mike Galbraith reported the following against an old fork of preempt-rt
but the same issue also applies to the current preempt-rt tree.&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd
   preempt_count: 1, expected: 0
   RCU nest depth: 0, expected: 0
   Preemption disabled at:
   fpu_clone
   CPU: 6 PID: 1 Comm: systemd Tainted: G            E       (unreleased)
   Call Trace:
    &amp;lt;TASK&amp;gt;
    dump_stack_lvl
    ? fpu_clone
    __might_resched
    rt_spin_lock
    fpu_clone
    ? copy_thread
    ? copy_process
    ? shmem_alloc_inode
    ? kmem_cache_alloc
    ? kernel_clone
    ? __do_sys_clone
    ? do_syscall_64
    ? __x64_sys_rt_sigprocmask
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? exc_page_fault
    ? entry_SYSCALL_64_after_hwframe
    &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Mike says:&lt;/p&gt;
&lt;p&gt;The splat comes from fpu_inherit_perms() being called under fpregs_lock(),
  and us reaching the spin_lock_irq() therein due to fpu_state_size_dynamic()
  returning true despite static key __fpu_state_size_dynamic having never
  been enabled.&lt;/p&gt;
&lt;p&gt;Mike&amp;#39;s assessment looks correct. fpregs_lock on a PREEMPT_RT kernel disables
preemption so calling spin_lock_irq()…&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;x86/fpu: Drop fpregs lock before inheriting FPU permissions&lt;/p&gt;
&lt;p&gt;Mike Galbraith reported the following against an old fork of preempt-rt
but the same issue also applies to the current preempt-rt tree.&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd
   preempt_count: 1, expected: 0
   RCU nest depth: 0, expected: 0
   Preemption disabled at:
   fpu_clone
   CPU: 6 PID: 1 Comm: systemd Tainted: G            E       (unreleased)
   Call Trace:
    &amp;lt;TASK&amp;gt;
    dump_stack_lvl
    ? fpu_clone
    __might_resched
    rt_spin_lock
    fpu_clone
    ? copy_thread
    ? copy_process
    ? shmem_alloc_inode
    ? kmem_cache_alloc
    ? kernel_clone
    ? __do_sys_clone
    ? do_syscall_64
    ? __x64_sys_rt_sigprocmask
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? syscall_exit_to_user_mode
    ? do_syscall_64
    ? exc_page_fault
    ? entry_SYSCALL_64_after_hwframe
    &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;Mike says:&lt;/p&gt;
&lt;p&gt;The splat comes from fpu_inherit_perms() being called under fpregs_lock(),
  and us reaching the spin_lock_irq() therein due to fpu_state_size_dynamic()
  returning true despite static key __fpu_state_size_dynamic having never
  been enabled.&lt;/p&gt;
&lt;p&gt;Mike&amp;#39;s assessment looks correct. fpregs_lock on a PREEMPT_RT kernel disables
preemption so calling spin_lock_irq()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g5p7-q8gg-6qmf</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49783</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49783</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 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Drop fpregs lock before inheriting FPU permissions Mike Galbraith reported the following against an old fork of preempt-rt but the same issue also applies to the current preempt-rt tree.    BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46    in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd    preempt_count: 1, expected: 0    RCU nest depth: 0, expected: 0    Preemption disabled at:    fpu_clone    CPU: 6 PID: 1 Comm: systemd Tainted: G            E       (unreleased)    Call Trace:     &amp;lt;TASK&amp;gt;     dump_stack_lvl     ? fpu_clone     __might_resched     rt_spin_lock     fpu_clone     ? copy_thread     ? copy_process     ? shmem_alloc_inode     ? kmem_cache_alloc     ? kernel_clone     ? __do_sys_clone     ? do_syscall_64     ? __x64_sys_rt_sigprocmask     ? syscall_exit_to_user_mode     ? do_syscall_64     ? syscall_exit_to_user_mode     ? do_syscall_64     ? syscall_exit_to_user_mode     ? do_syscall_64     ? exc_page_fault     ? entry_SYSCALL_64_after_hwframe     &amp;lt;/TASK&amp;gt; Mike says:   The splat comes from fpu_inherit_perms() being called under fpregs_lock(),   and us reaching the spin_lock_irq() therein due to fpu_state_size_dynamic()   returning true despite static key __fpu_state_size_dynamic having never   been enabled. Mike&amp;#39;s assessment looks correct. fpregs_lock on a PREEMPT_RT kernel disables preemption so calling spin_lock_irq() in fpu…&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 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Drop fpregs lock before inheriting FPU permissions Mike Galbraith reported the following against an old fork of preempt-rt but the same issue also applies to the current preempt-rt tree.    BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46    in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd    preempt_count: 1, expected: 0    RCU nest depth: 0, expected: 0    Preemption disabled at:    fpu_clone    CPU: 6 PID: 1 Comm: systemd Tainted: G            E       (unreleased)    Call Trace:     &amp;lt;TASK&amp;gt;     dump_stack_lvl     ? fpu_clone     __might_resched     rt_spin_lock     fpu_clone     ? copy_thread     ? copy_process     ? shmem_alloc_inode     ? kmem_cache_alloc     ? kernel_clone     ? __do_sys_clone     ? do_syscall_64     ? __x64_sys_rt_sigprocmask     ? syscall_exit_to_user_mode     ? do_syscall_64     ? syscall_exit_to_user_mode     ? do_syscall_64     ? syscall_exit_to_user_mode     ? do_syscall_64     ? exc_page_fault     ? entry_SYSCALL_64_after_hwframe     &amp;lt;/TASK&amp;gt; Mike says:   The splat comes from fpu_inherit_perms() being called under fpregs_lock(),   and us reaching the spin_lock_irq() therein due to fpu_state_size_dynamic()   returning true despite static key __fpu_state_size_dynamic having never   been enabled. Mike&amp;#39;s assessment looks correct. fpregs_lock on a PREEMPT_RT kernel disables preemption so calling spin_lock_irq() in fpu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49783</guid>
    </item>
  </channel>
</rss>
