<?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 10:59:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04061</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04061</link>
      <description>bdu:2026-04061</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04061</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1032 — 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-1032</link>
      <description>certfr-2025-avi-1032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032</guid>
    </item>
    <item>
      <title>EUVD-2026-311293</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311293</link>
      <description>EUVD-2026-311293</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311293</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50534</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50534</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm thin: Use last transaction&amp;#39;s pmd-&amp;gt;root when commit failed&lt;/p&gt;
&lt;p&gt;Recently we found a softlock up problem in dm thin pool btree lookup
code due to corrupted metadata:&lt;/p&gt;
&lt;p&gt;Kernel panic - not syncing: softlockup: hung tasks
 CPU: 7 PID: 2669225 Comm: kworker/u16:3
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
 Workqueue: dm-thin do_worker [dm_thin_pool]
 Call Trace:
   &amp;lt;IRQ&amp;gt;
   dump_stack+0x9c/0xd3
   panic+0x35d/0x6b9
   watchdog_timer_fn.cold+0x16/0x25
   __run_hrtimer+0xa2/0x2d0
   &amp;lt;/IRQ&amp;gt;
   RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio]
   __bufio_new+0x11f/0x4f0 [dm_bufio]
   new_read+0xa3/0x1e0 [dm_bufio]
   dm_bm_read_lock+0x33/0xd0 [dm_persistent_data]
   ro_step+0x63/0x100 [dm_persistent_data]
   btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data]
   dm_btree_lookup+0x16f/0x210 [dm_persistent_data]
   dm_thin_find_block+0x12c/0x210 [dm_thin_pool]
   __process_bio_read_only+0xc5/0x400 [dm_thin_pool]
   process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool]
   process_one_work+0x3c5/0x730&lt;/p&gt;
&lt;p&gt;Following process may generate a broken btree mixed with fresh and
stale btree nodes, which could get dm thin trapped in an infinite loop
while looking up data block:
 Transaction 1: pmd-&amp;gt;root = A, A-&amp;gt;B-&amp;gt;C   // One path in btree
                pmd-&amp;gt;root = X, X-&amp;gt;Y-&amp;gt;Z   // Copy-up
 Transaction 2: X,Z is updated on disk, Y write failed.
                // Commit failed, dm thin becomes read-only.…&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;dm thin: Use last transaction&amp;#39;s pmd-&amp;gt;root when commit failed&lt;/p&gt;
&lt;p&gt;Recently we found a softlock up problem in dm thin pool btree lookup
code due to corrupted metadata:&lt;/p&gt;
&lt;p&gt;Kernel panic - not syncing: softlockup: hung tasks
 CPU: 7 PID: 2669225 Comm: kworker/u16:3
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
 Workqueue: dm-thin do_worker [dm_thin_pool]
 Call Trace:
   &amp;lt;IRQ&amp;gt;
   dump_stack+0x9c/0xd3
   panic+0x35d/0x6b9
   watchdog_timer_fn.cold+0x16/0x25
   __run_hrtimer+0xa2/0x2d0
   &amp;lt;/IRQ&amp;gt;
   RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio]
   __bufio_new+0x11f/0x4f0 [dm_bufio]
   new_read+0xa3/0x1e0 [dm_bufio]
   dm_bm_read_lock+0x33/0xd0 [dm_persistent_data]
   ro_step+0x63/0x100 [dm_persistent_data]
   btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data]
   dm_btree_lookup+0x16f/0x210 [dm_persistent_data]
   dm_thin_find_block+0x12c/0x210 [dm_thin_pool]
   __process_bio_read_only+0xc5/0x400 [dm_thin_pool]
   process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool]
   process_one_work+0x3c5/0x730&lt;/p&gt;
&lt;p&gt;Following process may generate a broken btree mixed with fresh and
stale btree nodes, which could get dm thin trapped in an infinite loop
while looking up data block:
 Transaction 1: pmd-&amp;gt;root = A, A-&amp;gt;B-&amp;gt;C   // One path in btree
                pmd-&amp;gt;root = X, X-&amp;gt;Y-&amp;gt;Z   // Copy-up
 Transaction 2: X,Z is updated on disk, Y write failed.
                // Commit failed, dm thin becomes read-only.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50534</guid>
    </item>
    <item>
      <title>GHSA-84fr-rw9r-j8p4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-84fr-rw9r-j8p4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm thin: Use last transaction&amp;#39;s pmd-&amp;gt;root when commit failed&lt;/p&gt;
&lt;p&gt;Recently we found a softlock up problem in dm thin pool btree lookup
code due to corrupted metadata:&lt;/p&gt;
&lt;p&gt;Kernel panic - not syncing: softlockup: hung tasks
 CPU: 7 PID: 2669225 Comm: kworker/u16:3
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
 Workqueue: dm-thin do_worker [dm_thin_pool]
 Call Trace:
   &amp;lt;IRQ&amp;gt;
   dump_stack+0x9c/0xd3
   panic+0x35d/0x6b9
   watchdog_timer_fn.cold+0x16/0x25
   __run_hrtimer+0xa2/0x2d0
   &amp;lt;/IRQ&amp;gt;
   RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio]
   __bufio_new+0x11f/0x4f0 [dm_bufio]
   new_read+0xa3/0x1e0 [dm_bufio]
   dm_bm_read_lock+0x33/0xd0 [dm_persistent_data]
   ro_step+0x63/0x100 [dm_persistent_data]
   btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data]
   dm_btree_lookup+0x16f/0x210 [dm_persistent_data]
   dm_thin_find_block+0x12c/0x210 [dm_thin_pool]
   __process_bio_read_only+0xc5/0x400 [dm_thin_pool]
   process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool]
   process_one_work+0x3c5/0x730&lt;/p&gt;
&lt;p&gt;Following process may generate a broken btree mixed with fresh and
stale btree nodes, which could get dm thin trapped in an infinite loop
while looking up data block:
 Transaction 1: pmd-&amp;gt;root = A, A-&amp;gt;B-&amp;gt;C   // One path in btree
                pmd-&amp;gt;root = X, X-&amp;gt;Y-&amp;gt;Z   // Copy-up
 Transaction 2: X,Z is updated on disk, Y write failed.
                // Commit failed, dm thin becomes read-only.…&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;dm thin: Use last transaction&amp;#39;s pmd-&amp;gt;root when commit failed&lt;/p&gt;
&lt;p&gt;Recently we found a softlock up problem in dm thin pool btree lookup
code due to corrupted metadata:&lt;/p&gt;
&lt;p&gt;Kernel panic - not syncing: softlockup: hung tasks
 CPU: 7 PID: 2669225 Comm: kworker/u16:3
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
 Workqueue: dm-thin do_worker [dm_thin_pool]
 Call Trace:
   &amp;lt;IRQ&amp;gt;
   dump_stack+0x9c/0xd3
   panic+0x35d/0x6b9
   watchdog_timer_fn.cold+0x16/0x25
   __run_hrtimer+0xa2/0x2d0
   &amp;lt;/IRQ&amp;gt;
   RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio]
   __bufio_new+0x11f/0x4f0 [dm_bufio]
   new_read+0xa3/0x1e0 [dm_bufio]
   dm_bm_read_lock+0x33/0xd0 [dm_persistent_data]
   ro_step+0x63/0x100 [dm_persistent_data]
   btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data]
   dm_btree_lookup+0x16f/0x210 [dm_persistent_data]
   dm_thin_find_block+0x12c/0x210 [dm_thin_pool]
   __process_bio_read_only+0xc5/0x400 [dm_thin_pool]
   process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool]
   process_one_work+0x3c5/0x730&lt;/p&gt;
&lt;p&gt;Following process may generate a broken btree mixed with fresh and
stale btree nodes, which could get dm thin trapped in an infinite loop
while looking up data block:
 Transaction 1: pmd-&amp;gt;root = A, A-&amp;gt;B-&amp;gt;C   // One path in btree
                pmd-&amp;gt;root = X, X-&amp;gt;Y-&amp;gt;Z   // Copy-up
 Transaction 2: X,Z is updated on disk, Y write failed.
                // Commit failed, dm thin becomes read-only.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-84fr-rw9r-j8p4</guid>
    </item>
    <item>
      <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:2458</link>
      <description>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:2458</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4135-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:4135-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:4135-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50534</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50534</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, 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 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm thin: Use last transaction&amp;#39;s pmd-&amp;gt;root when commit failed Recently we found a softlock up problem in dm thin pool btree lookup code due to corrupted metadata:  Kernel panic - not syncing: softlockup: hung tasks  CPU: 7 PID: 2669225 Comm: kworker/u16:3  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)  Workqueue: dm-thin do_worker [dm_thin_pool]  Call Trace:    &amp;lt;IRQ&amp;gt;    dump_stack+0x9c/0xd3    panic+0x35d/0x6b9    watchdog_timer_fn.cold+0x16/0x25    __run_hrtimer+0xa2/0x2d0    &amp;lt;/IRQ&amp;gt;    RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio]    __bufio_new+0x11f/0x4f0 [dm_bufio]    new_read+0xa3/0x1e0 [dm_bufio]    dm_bm_read_lock+0x33/0xd0 [dm_persistent_data]    ro_step+0x63/0x100 [dm_persistent_data]    btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data]    dm_btree_lookup+0x16f/0x210 [dm_persistent_data]    dm_thin_find_block+0x12c/0x210 [dm_thin_pool]    __process_bio_read_only+0xc5/0x400 [dm_thin_pool]    process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool]    process_one_work+0x3c5/0x730 Following process may generate a broken btree mixed with fresh and stale btree nodes, which could get dm thin trapped in an infinite loop while looking up data block:  Transaction 1: pmd-&amp;gt;root = A, A-&amp;gt;B-&amp;gt;C   // One path in btree                 pmd-&amp;gt;root = X, X-&amp;gt;Y-&amp;gt;Z   // Copy-up  Transaction 2: X,Z is updated on disk, Y write failed.                 // Commit failed, dm thin becomes read-only.…&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, 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 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm thin: Use last transaction&amp;#39;s pmd-&amp;gt;root when commit failed Recently we found a softlock up problem in dm thin pool btree lookup code due to corrupted metadata:  Kernel panic - not syncing: softlockup: hung tasks  CPU: 7 PID: 2669225 Comm: kworker/u16:3  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)  Workqueue: dm-thin do_worker [dm_thin_pool]  Call Trace:    &amp;lt;IRQ&amp;gt;    dump_stack+0x9c/0xd3    panic+0x35d/0x6b9    watchdog_timer_fn.cold+0x16/0x25    __run_hrtimer+0xa2/0x2d0    &amp;lt;/IRQ&amp;gt;    RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio]    __bufio_new+0x11f/0x4f0 [dm_bufio]    new_read+0xa3/0x1e0 [dm_bufio]    dm_bm_read_lock+0x33/0xd0 [dm_persistent_data]    ro_step+0x63/0x100 [dm_persistent_data]    btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data]    dm_btree_lookup+0x16f/0x210 [dm_persistent_data]    dm_thin_find_block+0x12c/0x210 [dm_thin_pool]    __process_bio_read_only+0xc5/0x400 [dm_thin_pool]    process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool]    process_one_work+0x3c5/0x730 Following process may generate a broken btree mixed with fresh and stale btree nodes, which could get dm thin trapped in an infinite loop while looking up data block:  Transaction 1: pmd-&amp;gt;root = A, A-&amp;gt;B-&amp;gt;C   // One path in btree                 pmd-&amp;gt;root = X, X-&amp;gt;Y-&amp;gt;Z   // Copy-up  Transaction 2: X,Z is updated on disk, Y write failed.                 // Commit failed, dm thin becomes read-only.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50534</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2229 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229</guid>
    </item>
  </channel>
</rss>
