<?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 03:28:43 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10373</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10373</link>
      <description>bdu:2026-10373</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10373</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — 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-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-320383</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320383</link>
      <description>EUVD-2026-320383</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320383</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50652</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50652</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;uio: uio_dmem_genirq: Fix missing unlock in irq configuration&lt;/p&gt;
&lt;p&gt;Commit b74351287d4b (&amp;#34;uio: fix a sleep-in-atomic-context bug in
uio_dmem_genirq_irqcontrol()&amp;#34;) started calling disable_irq() without
holding the spinlock because it can sleep. However, that fix introduced
another bug: if interrupt is already disabled and a new disable request
comes in, then the spinlock is not unlocked:&lt;/p&gt;
&lt;p&gt;root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# [   14.851538] BUG: scheduling while atomic: bash/223/0x00000002
[   14.851991] Modules linked in: uio_dmem_genirq uio myfpga(OE) bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm snd_pcm ppdev joydev psmouse snd_timer snd e1000fb_sys_fops syscopyarea parport sysfillrect soundcore sysimgblt input_leds pcspkr i2c_piix4 serio_raw floppy evbug qemu_fw_cfg mac_hid pata_acpi ip_tables x_tables autofs4 [last unloaded: parport_pc]
[   14.854206] CPU: 0 PID: 223 Comm: bash Tainted: G           OE      6.0.0-rc7 #21
[   14.854786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
[   14.855664] Call Trace:
[   14.855861]  &amp;lt;TASK&amp;gt;
[   14.856025]  dump_stack_lvl+0x4d/0x67
[   14.856325]  dump_stack+0x14/0x1a
[   14.856583]  __schedule_bug.cold+0x4b/0x5c
[   14.856915]  __schedule+0xe81/0x13d0
[   14.857199]  ? idr_find+0x13/0x20
[   14.85…&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;uio: uio_dmem_genirq: Fix missing unlock in irq configuration&lt;/p&gt;
&lt;p&gt;Commit b74351287d4b (&amp;#34;uio: fix a sleep-in-atomic-context bug in
uio_dmem_genirq_irqcontrol()&amp;#34;) started calling disable_irq() without
holding the spinlock because it can sleep. However, that fix introduced
another bug: if interrupt is already disabled and a new disable request
comes in, then the spinlock is not unlocked:&lt;/p&gt;
&lt;p&gt;root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# [   14.851538] BUG: scheduling while atomic: bash/223/0x00000002
[   14.851991] Modules linked in: uio_dmem_genirq uio myfpga(OE) bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm snd_pcm ppdev joydev psmouse snd_timer snd e1000fb_sys_fops syscopyarea parport sysfillrect soundcore sysimgblt input_leds pcspkr i2c_piix4 serio_raw floppy evbug qemu_fw_cfg mac_hid pata_acpi ip_tables x_tables autofs4 [last unloaded: parport_pc]
[   14.854206] CPU: 0 PID: 223 Comm: bash Tainted: G           OE      6.0.0-rc7 #21
[   14.854786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
[   14.855664] Call Trace:
[   14.855861]  &amp;lt;TASK&amp;gt;
[   14.856025]  dump_stack_lvl+0x4d/0x67
[   14.856325]  dump_stack+0x14/0x1a
[   14.856583]  __schedule_bug.cold+0x4b/0x5c
[   14.856915]  __schedule+0xe81/0x13d0
[   14.857199]  ? idr_find+0x13/0x20
[   14.85…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50652</guid>
    </item>
    <item>
      <title>GHSA-7863-hf67-mmwv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7863-hf67-mmwv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;uio: uio_dmem_genirq: Fix missing unlock in irq configuration&lt;/p&gt;
&lt;p&gt;Commit b74351287d4b (&amp;#34;uio: fix a sleep-in-atomic-context bug in
uio_dmem_genirq_irqcontrol()&amp;#34;) started calling disable_irq() without
holding the spinlock because it can sleep. However, that fix introduced
another bug: if interrupt is already disabled and a new disable request
comes in, then the spinlock is not unlocked:&lt;/p&gt;
&lt;p&gt;root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# [   14.851538] BUG: scheduling while atomic: bash/223/0x00000002
[   14.851991] Modules linked in: uio_dmem_genirq uio myfpga(OE) bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm snd_pcm ppdev joydev psmouse snd_timer snd e1000fb_sys_fops syscopyarea parport sysfillrect soundcore sysimgblt input_leds pcspkr i2c_piix4 serio_raw floppy evbug qemu_fw_cfg mac_hid pata_acpi ip_tables x_tables autofs4 [last unloaded: parport_pc]
[   14.854206] CPU: 0 PID: 223 Comm: bash Tainted: G           OE      6.0.0-rc7 #21
[   14.854786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
[   14.855664] Call Trace:
[   14.855861]  &amp;lt;TASK&amp;gt;
[   14.856025]  dump_stack_lvl+0x4d/0x67
[   14.856325]  dump_stack+0x14/0x1a
[   14.856583]  __schedule_bug.cold+0x4b/0x5c
[   14.856915]  __schedule+0xe81/0x13d0
[   14.857199]  ? idr_find+0x13/0x20
[   14.85…&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;uio: uio_dmem_genirq: Fix missing unlock in irq configuration&lt;/p&gt;
&lt;p&gt;Commit b74351287d4b (&amp;#34;uio: fix a sleep-in-atomic-context bug in
uio_dmem_genirq_irqcontrol()&amp;#34;) started calling disable_irq() without
holding the spinlock because it can sleep. However, that fix introduced
another bug: if interrupt is already disabled and a new disable request
comes in, then the spinlock is not unlocked:&lt;/p&gt;
&lt;p&gt;root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0
root@localhost:~# [   14.851538] BUG: scheduling while atomic: bash/223/0x00000002
[   14.851991] Modules linked in: uio_dmem_genirq uio myfpga(OE) bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm snd_pcm ppdev joydev psmouse snd_timer snd e1000fb_sys_fops syscopyarea parport sysfillrect soundcore sysimgblt input_leds pcspkr i2c_piix4 serio_raw floppy evbug qemu_fw_cfg mac_hid pata_acpi ip_tables x_tables autofs4 [last unloaded: parport_pc]
[   14.854206] CPU: 0 PID: 223 Comm: bash Tainted: G           OE      6.0.0-rc7 #21
[   14.854786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
[   14.855664] Call Trace:
[   14.855861]  &amp;lt;TASK&amp;gt;
[   14.856025]  dump_stack_lvl+0x4d/0x67
[   14.856325]  dump_stack+0x14/0x1a
[   14.856583]  __schedule_bug.cold+0x4b/0x5c
[   14.856915]  __schedule+0xe81/0x13d0
[   14.857199]  ? idr_find+0x13/0x20
[   14.85…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7863-hf67-mmwv</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50652</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50652</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: uio: uio_dmem_genirq: Fix missing unlock in irq configuration Commit b74351287d4b (&amp;#34;uio: fix a sleep-in-atomic-context bug in uio_dmem_genirq_irqcontrol()&amp;#34;) started calling disable_irq() without holding the spinlock because it can sleep. However, that fix introduced another bug: if interrupt is already disabled and a new disable request comes in, then the spinlock is not unlocked: root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0 root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0 root@localhost:~# [   14.851538] BUG: scheduling while atomic: bash/223/0x00000002 [   14.851991] Modules linked in: uio_dmem_genirq uio myfpga(OE) bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm snd_pcm ppdev joydev psmouse snd_timer snd e1000fb_sys_fops syscopyarea parport sysfillrect soundcore sysimgblt input_leds pcspkr i2c_piix4 serio_raw floppy evbug qemu_fw_cfg mac_hid pata_acpi ip_tables x_tables autofs4 [last unloaded: parport_pc] [   14.854206] CPU: 0 PID: 223 Comm: bash Tainted: G           OE 6.0.0-rc7 #21 [   14.854786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 [   14.855664] Call Trace: [   14.855861]  &amp;lt;TASK&amp;gt; [   14.856025]  dump_stack_lvl+0x4d/0x67 [   14.856325]  dump_stack+0x14/0x1a [   14.856583]  __schedule_bug.cold+0x4b/0x5c [   14.856915]  __schedule+0xe81/0x13d0 [   14.857199]  ? idr_find+0x13/0x20 [   14.857456]  ?…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: uio: uio_dmem_genirq: Fix missing unlock in irq configuration Commit b74351287d4b (&amp;#34;uio: fix a sleep-in-atomic-context bug in uio_dmem_genirq_irqcontrol()&amp;#34;) started calling disable_irq() without holding the spinlock because it can sleep. However, that fix introduced another bug: if interrupt is already disabled and a new disable request comes in, then the spinlock is not unlocked: root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0 root@localhost:~# printf &amp;#39;\x00\x00\x00\x00&amp;#39; &amp;gt; /dev/uio0 root@localhost:~# [   14.851538] BUG: scheduling while atomic: bash/223/0x00000002 [   14.851991] Modules linked in: uio_dmem_genirq uio myfpga(OE) bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm snd_pcm ppdev joydev psmouse snd_timer snd e1000fb_sys_fops syscopyarea parport sysfillrect soundcore sysimgblt input_leds pcspkr i2c_piix4 serio_raw floppy evbug qemu_fw_cfg mac_hid pata_acpi ip_tables x_tables autofs4 [last unloaded: parport_pc] [   14.854206] CPU: 0 PID: 223 Comm: bash Tainted: G           OE 6.0.0-rc7 #21 [   14.854786] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 [   14.855664] Call Trace: [   14.855861]  &amp;lt;TASK&amp;gt; [   14.856025]  dump_stack_lvl+0x4d/0x67 [   14.856325]  dump_stack+0x14/0x1a [   14.856583]  __schedule_bug.cold+0x4b/0x5c [   14.856915]  __schedule+0xe81/0x13d0 [   14.857199]  ? idr_find+0x13/0x20 [   14.857456]  ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50652</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765</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-2765</guid>
    </item>
  </channel>
</rss>
