<?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 13:25:05 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03885</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03885</link>
      <description>bdu:2026-03885</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03885</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — 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-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-310388</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310388</link>
      <description>EUVD-2026-310388</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310388</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49193</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49193</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix &amp;#39;scheduling while atomic&amp;#39; on aux critical err interrupt&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a kernel BUG splat on processing aux critical error
interrupts in ice_misc_intr():&lt;/p&gt;
&lt;p&gt;[ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000
...
[ 2101.060770] Call Trace:
[ 2101.063229]  &amp;lt;IRQ&amp;gt;
[ 2101.065252]  dump_stack+0x41/0x60
[ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58
[ 2101.073060]  __schedule+0x6a4/0x830
[ 2101.076570]  schedule+0x35/0xa0
[ 2101.079727]  schedule_preempt_disabled+0xa/0x10
[ 2101.084284]  __mutex_lock.isra.7+0x310/0x420
[ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice]
[ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice]
[ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice]
[ 2101.102232]  __handle_irq_event_percpu+0x40/0x180
[ 2101.106965]  handle_irq_event_percpu+0x30/0x80
[ 2101.111434]  handle_irq_event+0x36/0x53
[ 2101.115292]  handle_edge_irq+0x82/0x190
[ 2101.119148]  handle_irq+0x1c/0x30
[ 2101.122480]  do_IRQ+0x49/0xd0
[ 2101.125465]  common_interrupt+0xf/0xf
[ 2101.129146]  &amp;lt;/IRQ&amp;gt;
...&lt;/p&gt;
&lt;p&gt;As Andrew correctly mentioned previously[0], the following call
ladder happens:&lt;/p&gt;
&lt;p&gt;ice_misc_intr() &amp;lt;- hardirq
  ice_send_event_to_aux()
    device_lock()
      mutex_lock()
        might_sleep()
          might_resched() &amp;lt;- oops&lt;/p&gt;
&lt;p&gt;Add a new PF state bit which indicates that an aux critical error
occurred and serve it in ice_service_task() in process context.
The new ice_pf::oicr_err_reg is read-write in both h…&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;ice: fix &amp;#39;scheduling while atomic&amp;#39; on aux critical err interrupt&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a kernel BUG splat on processing aux critical error
interrupts in ice_misc_intr():&lt;/p&gt;
&lt;p&gt;[ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000
...
[ 2101.060770] Call Trace:
[ 2101.063229]  &amp;lt;IRQ&amp;gt;
[ 2101.065252]  dump_stack+0x41/0x60
[ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58
[ 2101.073060]  __schedule+0x6a4/0x830
[ 2101.076570]  schedule+0x35/0xa0
[ 2101.079727]  schedule_preempt_disabled+0xa/0x10
[ 2101.084284]  __mutex_lock.isra.7+0x310/0x420
[ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice]
[ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice]
[ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice]
[ 2101.102232]  __handle_irq_event_percpu+0x40/0x180
[ 2101.106965]  handle_irq_event_percpu+0x30/0x80
[ 2101.111434]  handle_irq_event+0x36/0x53
[ 2101.115292]  handle_edge_irq+0x82/0x190
[ 2101.119148]  handle_irq+0x1c/0x30
[ 2101.122480]  do_IRQ+0x49/0xd0
[ 2101.125465]  common_interrupt+0xf/0xf
[ 2101.129146]  &amp;lt;/IRQ&amp;gt;
...&lt;/p&gt;
&lt;p&gt;As Andrew correctly mentioned previously[0], the following call
ladder happens:&lt;/p&gt;
&lt;p&gt;ice_misc_intr() &amp;lt;- hardirq
  ice_send_event_to_aux()
    device_lock()
      mutex_lock()
        might_sleep()
          might_resched() &amp;lt;- oops&lt;/p&gt;
&lt;p&gt;Add a new PF state bit which indicates that an aux critical error
occurred and serve it in ice_service_task() in process context.
The new ice_pf::oicr_err_reg is read-write in both h…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49193</guid>
    </item>
    <item>
      <title>GHSA-74r5-9m22-5p6r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-74r5-9m22-5p6r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix &amp;#39;scheduling while atomic&amp;#39; on aux critical err interrupt&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a kernel BUG splat on processing aux critical error
interrupts in ice_misc_intr():&lt;/p&gt;
&lt;p&gt;[ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000
...
[ 2101.060770] Call Trace:
[ 2101.063229]  &amp;lt;IRQ&amp;gt;
[ 2101.065252]  dump_stack+0x41/0x60
[ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58
[ 2101.073060]  __schedule+0x6a4/0x830
[ 2101.076570]  schedule+0x35/0xa0
[ 2101.079727]  schedule_preempt_disabled+0xa/0x10
[ 2101.084284]  __mutex_lock.isra.7+0x310/0x420
[ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice]
[ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice]
[ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice]
[ 2101.102232]  __handle_irq_event_percpu+0x40/0x180
[ 2101.106965]  handle_irq_event_percpu+0x30/0x80
[ 2101.111434]  handle_irq_event+0x36/0x53
[ 2101.115292]  handle_edge_irq+0x82/0x190
[ 2101.119148]  handle_irq+0x1c/0x30
[ 2101.122480]  do_IRQ+0x49/0xd0
[ 2101.125465]  common_interrupt+0xf/0xf
[ 2101.129146]  &amp;lt;/IRQ&amp;gt;
...&lt;/p&gt;
&lt;p&gt;As Andrew correctly mentioned previously[0], the following call
ladder happens:&lt;/p&gt;
&lt;p&gt;ice_misc_intr() &amp;lt;- hardirq
  ice_send_event_to_aux()
    device_lock()
      mutex_lock()
        might_sleep()
          might_resched() &amp;lt;- oops&lt;/p&gt;
&lt;p&gt;Add a new PF state bit which indicates that an aux critical error
occurred and serve it in ice_service_task() in process context.
The new ice_pf::oicr_err_reg is read-write in both h…&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;ice: fix &amp;#39;scheduling while atomic&amp;#39; on aux critical err interrupt&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a kernel BUG splat on processing aux critical error
interrupts in ice_misc_intr():&lt;/p&gt;
&lt;p&gt;[ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000
...
[ 2101.060770] Call Trace:
[ 2101.063229]  &amp;lt;IRQ&amp;gt;
[ 2101.065252]  dump_stack+0x41/0x60
[ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58
[ 2101.073060]  __schedule+0x6a4/0x830
[ 2101.076570]  schedule+0x35/0xa0
[ 2101.079727]  schedule_preempt_disabled+0xa/0x10
[ 2101.084284]  __mutex_lock.isra.7+0x310/0x420
[ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice]
[ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice]
[ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice]
[ 2101.102232]  __handle_irq_event_percpu+0x40/0x180
[ 2101.106965]  handle_irq_event_percpu+0x30/0x80
[ 2101.111434]  handle_irq_event+0x36/0x53
[ 2101.115292]  handle_edge_irq+0x82/0x190
[ 2101.119148]  handle_irq+0x1c/0x30
[ 2101.122480]  do_IRQ+0x49/0xd0
[ 2101.125465]  common_interrupt+0xf/0xf
[ 2101.129146]  &amp;lt;/IRQ&amp;gt;
...&lt;/p&gt;
&lt;p&gt;As Andrew correctly mentioned previously[0], the following call
ladder happens:&lt;/p&gt;
&lt;p&gt;ice_misc_intr() &amp;lt;- hardirq
  ice_send_event_to_aux()
    device_lock()
      mutex_lock()
        might_sleep()
          might_resched() &amp;lt;- oops&lt;/p&gt;
&lt;p&gt;Add a new PF state bit which indicates that an aux critical error
occurred and serve it in ice_service_task() in process context.
The new ice_pf::oicr_err_reg is read-write in both h…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-74r5-9m22-5p6r</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49193</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49193</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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ice: fix &amp;#39;scheduling while atomic&amp;#39; on aux critical err interrupt There&amp;#39;s a kernel BUG splat on processing aux critical error interrupts in ice_misc_intr(): [ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000 ... [ 2101.060770] Call Trace: [ 2101.063229]  &amp;lt;IRQ&amp;gt; [ 2101.065252]  dump_stack+0x41/0x60 [ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58 [ 2101.073060]  __schedule+0x6a4/0x830 [ 2101.076570]  schedule+0x35/0xa0 [ 2101.079727]  schedule_preempt_disabled+0xa/0x10 [ 2101.084284]  __mutex_lock.isra.7+0x310/0x420 [ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice] [ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice] [ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice] [ 2101.102232]  __handle_irq_event_percpu+0x40/0x180 [ 2101.106965]  handle_irq_event_percpu+0x30/0x80 [ 2101.111434]  handle_irq_event+0x36/0x53 [ 2101.115292]  handle_edge_irq+0x82/0x190 [ 2101.119148]  handle_irq+0x1c/0x30 [ 2101.122480]  do_IRQ+0x49/0xd0 [ 2101.125465]  common_interrupt+0xf/0xf [ 2101.129146]  &amp;lt;/IRQ&amp;gt; ... As Andrew correctly mentioned previously[0], the following call ladder happens: ice_misc_intr() &amp;lt;- hardirq   ice_send_event_to_aux()     device_lock()       mutex_lock()         might_sleep()           might_resched() &amp;lt;- oops Add a new PF state bit which indicates that an aux critical error occurred and serve it in ice_service_task() in process context. The new ice_pf::oicr_err_reg is read-write in both hardirq…&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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ice: fix &amp;#39;scheduling while atomic&amp;#39; on aux critical err interrupt There&amp;#39;s a kernel BUG splat on processing aux critical error interrupts in ice_misc_intr(): [ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000 ... [ 2101.060770] Call Trace: [ 2101.063229]  &amp;lt;IRQ&amp;gt; [ 2101.065252]  dump_stack+0x41/0x60 [ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58 [ 2101.073060]  __schedule+0x6a4/0x830 [ 2101.076570]  schedule+0x35/0xa0 [ 2101.079727]  schedule_preempt_disabled+0xa/0x10 [ 2101.084284]  __mutex_lock.isra.7+0x310/0x420 [ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice] [ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice] [ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice] [ 2101.102232]  __handle_irq_event_percpu+0x40/0x180 [ 2101.106965]  handle_irq_event_percpu+0x30/0x80 [ 2101.111434]  handle_irq_event+0x36/0x53 [ 2101.115292]  handle_edge_irq+0x82/0x190 [ 2101.119148]  handle_irq+0x1c/0x30 [ 2101.122480]  do_IRQ+0x49/0xd0 [ 2101.125465]  common_interrupt+0xf/0xf [ 2101.129146]  &amp;lt;/IRQ&amp;gt; ... As Andrew correctly mentioned previously[0], the following call ladder happens: ice_misc_intr() &amp;lt;- hardirq   ice_send_event_to_aux()     device_lock()       mutex_lock()         might_sleep()           might_resched() &amp;lt;- oops Add a new PF state bit which indicates that an aux critical error occurred and serve it in ice_service_task() in process context. The new ice_pf::oicr_err_reg is read-write in both hardirq…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49193</guid>
    </item>
  </channel>
</rss>
