<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T13:25:12.452645+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2026-03885</id>
    <title>bdu:2026-03885</title>
    <updated>2026-10-05T13:25:12.744815+00:00</updated>
    <content>bdu:2026-03885</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-03885"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</id>
    <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>
    <updated>2026-10-05T13:25:12.744892+00:00</updated>
    <content>certfr-2025-avi-0252</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-310388</id>
    <title>EUVD-2026-310388</title>
    <updated>2026-10-05T13:25:12.744916+00:00</updated>
    <content>EUVD-2026-310388</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-310388"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49193</id>
    <title>fkie_cve-2022-49193</title>
    <updated>2026-10-05T13:25:12.744930+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ice: fix 'scheduling while atomic' on aux critical err interrupt</p>
<p>There's a kernel BUG splat on processing aux critical error
interrupts in ice_misc_intr():</p>
<p>[ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000
...
[ 2101.060770] Call Trace:
[ 2101.063229]  &lt;IRQ&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]  &lt;/IRQ&gt;
...</p>
<p>As Andrew correctly mentioned previously[0], the following call
ladder happens:</p>
<p>ice_misc_intr() &lt;- hardirq
  ice_send_event_to_aux()
    device_lock()
      mutex_lock()
        might_sleep()
          might_resched() &lt;- oops</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-49193"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-74r5-9m22-5p6r</id>
    <title>GHSA-74r5-9m22-5p6r</title>
    <updated>2026-10-05T13:25:12.744984+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ice: fix 'scheduling while atomic' on aux critical err interrupt</p>
<p>There's a kernel BUG splat on processing aux critical error
interrupts in ice_misc_intr():</p>
<p>[ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000
...
[ 2101.060770] Call Trace:
[ 2101.063229]  &lt;IRQ&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]  &lt;/IRQ&gt;
...</p>
<p>As Andrew correctly mentioned previously[0], the following call
ladder happens:</p>
<p>ice_misc_intr() &lt;- hardirq
  ice_send_event_to_aux()
    device_lock()
      mutex_lock()
        might_sleep()
          might_resched() &lt;- oops</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-74r5-9m22-5p6r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1</id>
    <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-05T13:25:12.745049+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2025:1176-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49193</id>
    <title>UBUNTU-CVE-2022-49193</title>
    <updated>2026-10-05T13:25:12.745516+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ice: fix 'scheduling while atomic' on aux critical err interrupt There'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]  &lt;IRQ&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]  &lt;/IRQ&gt; ... As Andrew correctly mentioned previously[0], the following call ladder happens: ice_misc_intr() &lt;- hardirq   ice_send_event_to_aux()     device_lock()       mutex_lock()         might_sleep()           might_resched() &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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49193"/>
  </entry>
</feed>
