<?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 20:33:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03847</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03847</link>
      <description>bdu:2026-03847</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03847</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-311313</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311313</link>
      <description>EUVD-2026-311313</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311313</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50563</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50563</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm thin: Fix UAF in run_timer_softirq()&lt;/p&gt;
&lt;p&gt;When dm_resume() and dm_destroy() are concurrent, it will
lead to UAF, as follows:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in __run_timers+0x173/0x710
 Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0
&amp;lt;snip&amp;gt;
 Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack_lvl+0x73/0x9f
  print_report.cold+0x132/0xaa2
  _raw_spin_lock_irqsave+0xcd/0x160
  __run_timers+0x173/0x710
  kasan_report+0xad/0x110
  __run_timers+0x173/0x710
  __asan_store8+0x9c/0x140
  __run_timers+0x173/0x710
  call_timer_fn+0x310/0x310
  pvclock_clocksource_read+0xfa/0x250
  kvm_clock_read+0x2c/0x70
  kvm_clock_get_cycles+0xd/0x20
  ktime_get+0x5c/0x110
  lapic_next_event+0x38/0x50
  clockevents_program_event+0xf1/0x1e0
  run_timer_softirq+0x49/0x90
  __do_softirq+0x16e/0x62c
  __irq_exit_rcu+0x1fa/0x270
  irq_exit_rcu+0x12/0x20
  sysvec_apic_timer_interrupt+0x8e/0xc0&lt;/p&gt;
&lt;p&gt;One of the concurrency UAF can be shown as below:&lt;/p&gt;
&lt;p&gt;use                                  free
do_resume                           |
  __find_device_hash_cell           |
    dm_get                          |
      atomic_inc(&amp;amp;md-&amp;gt;holders)      |
                                    | dm_destroy
                                    |   __dm_destroy
                                    |     if (!dm_suspended_md(md))
                                    |     atomic_read(&amp;amp;md-&amp;gt;holders)
                                    |     msleep(1)
  dm_resume…&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: Fix UAF in run_timer_softirq()&lt;/p&gt;
&lt;p&gt;When dm_resume() and dm_destroy() are concurrent, it will
lead to UAF, as follows:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in __run_timers+0x173/0x710
 Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0
&amp;lt;snip&amp;gt;
 Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack_lvl+0x73/0x9f
  print_report.cold+0x132/0xaa2
  _raw_spin_lock_irqsave+0xcd/0x160
  __run_timers+0x173/0x710
  kasan_report+0xad/0x110
  __run_timers+0x173/0x710
  __asan_store8+0x9c/0x140
  __run_timers+0x173/0x710
  call_timer_fn+0x310/0x310
  pvclock_clocksource_read+0xfa/0x250
  kvm_clock_read+0x2c/0x70
  kvm_clock_get_cycles+0xd/0x20
  ktime_get+0x5c/0x110
  lapic_next_event+0x38/0x50
  clockevents_program_event+0xf1/0x1e0
  run_timer_softirq+0x49/0x90
  __do_softirq+0x16e/0x62c
  __irq_exit_rcu+0x1fa/0x270
  irq_exit_rcu+0x12/0x20
  sysvec_apic_timer_interrupt+0x8e/0xc0&lt;/p&gt;
&lt;p&gt;One of the concurrency UAF can be shown as below:&lt;/p&gt;
&lt;p&gt;use                                  free
do_resume                           |
  __find_device_hash_cell           |
    dm_get                          |
      atomic_inc(&amp;amp;md-&amp;gt;holders)      |
                                    | dm_destroy
                                    |   __dm_destroy
                                    |     if (!dm_suspended_md(md))
                                    |     atomic_read(&amp;amp;md-&amp;gt;holders)
                                    |     msleep(1)
  dm_resume…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50563</guid>
    </item>
    <item>
      <title>GHSA-9g9c-838j-m3cg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9g9c-838j-m3cg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm thin: Fix UAF in run_timer_softirq()&lt;/p&gt;
&lt;p&gt;When dm_resume() and dm_destroy() are concurrent, it will
lead to UAF, as follows:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in __run_timers+0x173/0x710
 Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0
&amp;lt;snip&amp;gt;
 Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack_lvl+0x73/0x9f
  print_report.cold+0x132/0xaa2
  _raw_spin_lock_irqsave+0xcd/0x160
  __run_timers+0x173/0x710
  kasan_report+0xad/0x110
  __run_timers+0x173/0x710
  __asan_store8+0x9c/0x140
  __run_timers+0x173/0x710
  call_timer_fn+0x310/0x310
  pvclock_clocksource_read+0xfa/0x250
  kvm_clock_read+0x2c/0x70
  kvm_clock_get_cycles+0xd/0x20
  ktime_get+0x5c/0x110
  lapic_next_event+0x38/0x50
  clockevents_program_event+0xf1/0x1e0
  run_timer_softirq+0x49/0x90
  __do_softirq+0x16e/0x62c
  __irq_exit_rcu+0x1fa/0x270
  irq_exit_rcu+0x12/0x20
  sysvec_apic_timer_interrupt+0x8e/0xc0&lt;/p&gt;
&lt;p&gt;One of the concurrency UAF can be shown as below:&lt;/p&gt;
&lt;p&gt;use                                  free
do_resume                           |
  __find_device_hash_cell           |
    dm_get                          |
      atomic_inc(&amp;amp;md-&amp;gt;holders)      |
                                    | dm_destroy
                                    |   __dm_destroy
                                    |     if (!dm_suspended_md(md))
                                    |     atomic_read(&amp;amp;md-&amp;gt;holders)
                                    |     msleep(1)
  dm_resume…&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: Fix UAF in run_timer_softirq()&lt;/p&gt;
&lt;p&gt;When dm_resume() and dm_destroy() are concurrent, it will
lead to UAF, as follows:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in __run_timers+0x173/0x710
 Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0
&amp;lt;snip&amp;gt;
 Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack_lvl+0x73/0x9f
  print_report.cold+0x132/0xaa2
  _raw_spin_lock_irqsave+0xcd/0x160
  __run_timers+0x173/0x710
  kasan_report+0xad/0x110
  __run_timers+0x173/0x710
  __asan_store8+0x9c/0x140
  __run_timers+0x173/0x710
  call_timer_fn+0x310/0x310
  pvclock_clocksource_read+0xfa/0x250
  kvm_clock_read+0x2c/0x70
  kvm_clock_get_cycles+0xd/0x20
  ktime_get+0x5c/0x110
  lapic_next_event+0x38/0x50
  clockevents_program_event+0xf1/0x1e0
  run_timer_softirq+0x49/0x90
  __do_softirq+0x16e/0x62c
  __irq_exit_rcu+0x1fa/0x270
  irq_exit_rcu+0x12/0x20
  sysvec_apic_timer_interrupt+0x8e/0xc0&lt;/p&gt;
&lt;p&gt;One of the concurrency UAF can be shown as below:&lt;/p&gt;
&lt;p&gt;use                                  free
do_resume                           |
  __find_device_hash_cell           |
    dm_get                          |
      atomic_inc(&amp;amp;md-&amp;gt;holders)      |
                                    | dm_destroy
                                    |   __dm_destroy
                                    |     if (!dm_suspended_md(md))
                                    |     atomic_read(&amp;amp;md-&amp;gt;holders)
                                    |     msleep(1)
  dm_resume…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9g9c-838j-m3cg</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-50563</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50563</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 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm thin: Fix UAF in run_timer_softirq() When dm_resume() and dm_destroy() are concurrent, it will lead to UAF, as follows:  BUG: KASAN: use-after-free in __run_timers+0x173/0x710  Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0 &amp;lt;snip&amp;gt;  Call Trace:   &amp;lt;IRQ&amp;gt;   dump_stack_lvl+0x73/0x9f   print_report.cold+0x132/0xaa2   _raw_spin_lock_irqsave+0xcd/0x160   __run_timers+0x173/0x710   kasan_report+0xad/0x110   __run_timers+0x173/0x710   __asan_store8+0x9c/0x140   __run_timers+0x173/0x710   call_timer_fn+0x310/0x310   pvclock_clocksource_read+0xfa/0x250   kvm_clock_read+0x2c/0x70   kvm_clock_get_cycles+0xd/0x20   ktime_get+0x5c/0x110   lapic_next_event+0x38/0x50   clockevents_program_event+0xf1/0x1e0   run_timer_softirq+0x49/0x90   __do_softirq+0x16e/0x62c   __irq_exit_rcu+0x1fa/0x270   irq_exit_rcu+0x12/0x20   sysvec_apic_timer_interrupt+0x8e/0xc0 One of the concurrency UAF can be shown as below:         use                                  free do_resume                           |   __find_device_hash_cell           |     dm_get                          |       atomic_inc(&amp;amp;md-&amp;gt;holders)      |                                     | dm_destroy                                     |   __dm_destroy                                     |     if (!dm_suspended_md(md))                                     |     atomic_read(&amp;amp;md-&amp;gt;holders)                                     |     msleep(1)   dm_resume…&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 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm thin: Fix UAF in run_timer_softirq() When dm_resume() and dm_destroy() are concurrent, it will lead to UAF, as follows:  BUG: KASAN: use-after-free in __run_timers+0x173/0x710  Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0 &amp;lt;snip&amp;gt;  Call Trace:   &amp;lt;IRQ&amp;gt;   dump_stack_lvl+0x73/0x9f   print_report.cold+0x132/0xaa2   _raw_spin_lock_irqsave+0xcd/0x160   __run_timers+0x173/0x710   kasan_report+0xad/0x110   __run_timers+0x173/0x710   __asan_store8+0x9c/0x140   __run_timers+0x173/0x710   call_timer_fn+0x310/0x310   pvclock_clocksource_read+0xfa/0x250   kvm_clock_read+0x2c/0x70   kvm_clock_get_cycles+0xd/0x20   ktime_get+0x5c/0x110   lapic_next_event+0x38/0x50   clockevents_program_event+0xf1/0x1e0   run_timer_softirq+0x49/0x90   __do_softirq+0x16e/0x62c   __irq_exit_rcu+0x1fa/0x270   irq_exit_rcu+0x12/0x20   sysvec_apic_timer_interrupt+0x8e/0xc0 One of the concurrency UAF can be shown as below:         use                                  free do_resume                           |   __find_device_hash_cell           |     dm_get                          |       atomic_inc(&amp;amp;md-&amp;gt;holders)      |                                     | dm_destroy                                     |   __dm_destroy                                     |     if (!dm_suspended_md(md))                                     |     atomic_read(&amp;amp;md-&amp;gt;holders)                                     |     msleep(1)   dm_resume…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50563</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2394 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2394</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff oder 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 oder 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-2394</guid>
    </item>
  </channel>
</rss>
