<?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 09:13:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-14326</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-14326</link>
      <description>bdu:2025-14326</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-14326</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-344459</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344459</link>
      <description>EUVD-2026-344459</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344459</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47346</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47346</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()&lt;/p&gt;
&lt;p&gt;commit 6f755e85c332 (&amp;#34;coresight: Add helper for inserting synchronization
packets&amp;#34;) removed trailing &amp;#39;\0&amp;#39; from barrier_pkt array and updated the
call sites like etb_update_buffer() to have proper checks for barrier_pkt
size before read but missed updating tmc_update_etf_buffer() which still
reads barrier_pkt past the array size resulting in KASAN out-of-bounds
bug. Fix this by adding a check for barrier_pkt size before accessing
like it is done in etb_update_buffer().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in tmc_update_etf_buffer+0x4b8/0x698
 Read of size 4 at addr ffffffd05b7d1030 by task perf/2629&lt;/p&gt;
&lt;p&gt;Call trace:
  dump_backtrace+0x0/0x27c
  show_stack+0x20/0x2c
  dump_stack+0x11c/0x188
  print_address_description+0x3c/0x4a4
  __kasan_report+0x140/0x164
  kasan_report+0x10/0x18
  __asan_report_load4_noabort+0x1c/0x24
  tmc_update_etf_buffer+0x4b8/0x698
  etm_event_stop+0x248/0x2d8
  etm_event_del+0x20/0x2c
  event_sched_out+0x214/0x6f0
  group_sched_out+0xd0/0x270
  ctx_sched_out+0x2ec/0x518
  __perf_event_task_sched_out+0x4fc/0xe6c
  __schedule+0x1094/0x16a0
  preempt_schedule_irq+0x88/0x170
  arm64_preempt_schedule_irq+0xf0/0x18c
  el1_irq+0xe8/0x180
  perf_event_exec+0x4d8/0x56c
  setup_new_exec+0x204/0x400
  load_elf_binary+0x72c/0x18c0
  search_binary_handler+0x13c/0x420
  load_script+0x500/0x6c4
  search_binary_handler+0x13c/0x420…&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;coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()&lt;/p&gt;
&lt;p&gt;commit 6f755e85c332 (&amp;#34;coresight: Add helper for inserting synchronization
packets&amp;#34;) removed trailing &amp;#39;\0&amp;#39; from barrier_pkt array and updated the
call sites like etb_update_buffer() to have proper checks for barrier_pkt
size before read but missed updating tmc_update_etf_buffer() which still
reads barrier_pkt past the array size resulting in KASAN out-of-bounds
bug. Fix this by adding a check for barrier_pkt size before accessing
like it is done in etb_update_buffer().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in tmc_update_etf_buffer+0x4b8/0x698
 Read of size 4 at addr ffffffd05b7d1030 by task perf/2629&lt;/p&gt;
&lt;p&gt;Call trace:
  dump_backtrace+0x0/0x27c
  show_stack+0x20/0x2c
  dump_stack+0x11c/0x188
  print_address_description+0x3c/0x4a4
  __kasan_report+0x140/0x164
  kasan_report+0x10/0x18
  __asan_report_load4_noabort+0x1c/0x24
  tmc_update_etf_buffer+0x4b8/0x698
  etm_event_stop+0x248/0x2d8
  etm_event_del+0x20/0x2c
  event_sched_out+0x214/0x6f0
  group_sched_out+0xd0/0x270
  ctx_sched_out+0x2ec/0x518
  __perf_event_task_sched_out+0x4fc/0xe6c
  __schedule+0x1094/0x16a0
  preempt_schedule_irq+0x88/0x170
  arm64_preempt_schedule_irq+0xf0/0x18c
  el1_irq+0xe8/0x180
  perf_event_exec+0x4d8/0x56c
  setup_new_exec+0x204/0x400
  load_elf_binary+0x72c/0x18c0
  search_binary_handler+0x13c/0x420
  load_script+0x500/0x6c4
  search_binary_handler+0x13c/0x420…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47346</guid>
    </item>
    <item>
      <title>GHSA-3hw4-pvhh-9qcq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3hw4-pvhh-9qcq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()&lt;/p&gt;
&lt;p&gt;commit 6f755e85c332 (&amp;#34;coresight: Add helper for inserting synchronization
packets&amp;#34;) removed trailing &amp;#39;\0&amp;#39; from barrier_pkt array and updated the
call sites like etb_update_buffer() to have proper checks for barrier_pkt
size before read but missed updating tmc_update_etf_buffer() which still
reads barrier_pkt past the array size resulting in KASAN out-of-bounds
bug. Fix this by adding a check for barrier_pkt size before accessing
like it is done in etb_update_buffer().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in tmc_update_etf_buffer+0x4b8/0x698
 Read of size 4 at addr ffffffd05b7d1030 by task perf/2629&lt;/p&gt;
&lt;p&gt;Call trace:
  dump_backtrace+0x0/0x27c
  show_stack+0x20/0x2c
  dump_stack+0x11c/0x188
  print_address_description+0x3c/0x4a4
  __kasan_report+0x140/0x164
  kasan_report+0x10/0x18
  __asan_report_load4_noabort+0x1c/0x24
  tmc_update_etf_buffer+0x4b8/0x698
  etm_event_stop+0x248/0x2d8
  etm_event_del+0x20/0x2c
  event_sched_out+0x214/0x6f0
  group_sched_out+0xd0/0x270
  ctx_sched_out+0x2ec/0x518
  __perf_event_task_sched_out+0x4fc/0xe6c
  __schedule+0x1094/0x16a0
  preempt_schedule_irq+0x88/0x170
  arm64_preempt_schedule_irq+0xf0/0x18c
  el1_irq+0xe8/0x180
  perf_event_exec+0x4d8/0x56c
  setup_new_exec+0x204/0x400
  load_elf_binary+0x72c/0x18c0
  search_binary_handler+0x13c/0x420
  load_script+0x500/0x6c4
  search_binary_handler+0x13c/0x420…&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;coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()&lt;/p&gt;
&lt;p&gt;commit 6f755e85c332 (&amp;#34;coresight: Add helper for inserting synchronization
packets&amp;#34;) removed trailing &amp;#39;\0&amp;#39; from barrier_pkt array and updated the
call sites like etb_update_buffer() to have proper checks for barrier_pkt
size before read but missed updating tmc_update_etf_buffer() which still
reads barrier_pkt past the array size resulting in KASAN out-of-bounds
bug. Fix this by adding a check for barrier_pkt size before accessing
like it is done in etb_update_buffer().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in tmc_update_etf_buffer+0x4b8/0x698
 Read of size 4 at addr ffffffd05b7d1030 by task perf/2629&lt;/p&gt;
&lt;p&gt;Call trace:
  dump_backtrace+0x0/0x27c
  show_stack+0x20/0x2c
  dump_stack+0x11c/0x188
  print_address_description+0x3c/0x4a4
  __kasan_report+0x140/0x164
  kasan_report+0x10/0x18
  __asan_report_load4_noabort+0x1c/0x24
  tmc_update_etf_buffer+0x4b8/0x698
  etm_event_stop+0x248/0x2d8
  etm_event_del+0x20/0x2c
  event_sched_out+0x214/0x6f0
  group_sched_out+0xd0/0x270
  ctx_sched_out+0x2ec/0x518
  __perf_event_task_sched_out+0x4fc/0xe6c
  __schedule+0x1094/0x16a0
  preempt_schedule_irq+0x88/0x170
  arm64_preempt_schedule_irq+0xf0/0x18c
  el1_irq+0xe8/0x180
  perf_event_exec+0x4d8/0x56c
  setup_new_exec+0x204/0x400
  load_elf_binary+0x72c/0x18c0
  search_binary_handler+0x13c/0x420
  load_script+0x500/0x6c4
  search_binary_handler+0x13c/0x420…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3hw4-pvhh-9qcq</guid>
    </item>
    <item>
      <title>OESA-2024-1767 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1767</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
can: mcba_usb: fix memory leak in mcba_usb&#13;
&#13;
Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS
Analyzer Tool. The problem was in unfreed usb_coherent.&#13;
&#13;
In mcba_usb_start() 20 coherent buffers are allocated and there is
nothing, that frees them:&#13;
&#13;
1) In callback function the urb is resubmitted and that&amp;amp;apos;s all
2) In disconnect function urbs are simply killed, but URB_FREE_BUFFER
   is not set (see mcba_usb_start) and this flag cannot be used with
   coherent buffers.&#13;
&#13;
Fail log:
| [ 1354.053291][ T8413] mcba_usb 1-1:0.0 can0: device disconnected
| [ 1367.059384][ T8420] kmemleak: 20 new suspected memory leaks (see /sys/kernel/debug/kmem)&#13;
&#13;
So, all allocated buffers should be freed with usb_free_coherent()
explicitly&#13;
&#13;
NOTE:
The same pattern for allocating and freeing coherent buffers
is used in drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c(CVE-2021-47231)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
can: j1939: fix Use-after-Free, hold skb ref while in use&#13;
&#13;
This patch fixes a Use-after-Free found by the syzbot.&#13;
&#13;
The problem is that a skb is taken from the per-session skb queue,
without incrementing the ref count. This leads to a Use-after-Free if
the skb is taken concurrently from the session queue due to a CTS.(CVE-2021-47232)&#13;
&#13;
In the Linux kernel, the following v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
can: mcba_usb: fix memory leak in mcba_usb&#13;
&#13;
Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS
Analyzer Tool. The problem was in unfreed usb_coherent.&#13;
&#13;
In mcba_usb_start() 20 coherent buffers are allocated and there is
nothing, that frees them:&#13;
&#13;
1) In callback function the urb is resubmitted and that&amp;amp;apos;s all
2) In disconnect function urbs are simply killed, but URB_FREE_BUFFER
   is not set (see mcba_usb_start) and this flag cannot be used with
   coherent buffers.&#13;
&#13;
Fail log:
| [ 1354.053291][ T8413] mcba_usb 1-1:0.0 can0: device disconnected
| [ 1367.059384][ T8420] kmemleak: 20 new suspected memory leaks (see /sys/kernel/debug/kmem)&#13;
&#13;
So, all allocated buffers should be freed with usb_free_coherent()
explicitly&#13;
&#13;
NOTE:
The same pattern for allocating and freeing coherent buffers
is used in drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c(CVE-2021-47231)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
can: j1939: fix Use-after-Free, hold skb ref while in use&#13;
&#13;
This patch fixes a Use-after-Free found by the syzbot.&#13;
&#13;
The problem is that a skb is taken from the per-session skb queue,
without incrementing the ref count. This leads to a Use-after-Free if
the skb is taken concurrently from the session queue due to a CTS.(CVE-2021-47232)&#13;
&#13;
In the Linux kernel, the following v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1767</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47346</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47346</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer() commit 6f755e85c332 (&amp;#34;coresight: Add helper for inserting synchronization packets&amp;#34;) removed trailing &amp;#39;\0&amp;#39; from barrier_pkt array and updated the call sites like etb_update_buffer() to have proper checks for barrier_pkt size before read but missed updating tmc_update_etf_buffer() which still reads barrier_pkt past the array size resulting in KASAN out-of-bounds bug. Fix this by adding a check for barrier_pkt size before accessing like it is done in etb_update_buffer().  BUG: KASAN: global-out-of-bounds in tmc_update_etf_buffer+0x4b8/0x698  Read of size 4 at addr ffffffd05b7d1030 by task perf/2629  Call trace:   dump_backtrace+0x0/0x27c   show_stack+0x20/0x2c   dump_stack+0x11c/0x188   print_address_description+0x3c/0x4a4   __kasan_report+0x140/0x164   kasan_report+0x10/0x18   __asan_report_load4_noabort+0x1c/0x24   tmc_update_etf_buffer+0x4b8/0x698   etm_event_stop+0x248/0x2d8   etm_event_del+0x20/0x2c   event_sched_out+0x214/0x6f0   group_sched_out+0xd0/0x270   ctx_sched_out+0x2ec/0x518   __perf_event_task_sched_out+0x4fc/0xe6c   __schedule+0x1094/0x16a0   preempt_schedule_irq+0x88/0x170   arm64_preempt_schedule_irq+0xf0/0x18c   el1_irq+0xe8/0x180   perf_event_exec+0x4d8/0x56c   setup_new_exec+0x204/0x400   load_elf_binary+0x72c/0x18c0   search_binary_handler+0x13c/0x420   load_script+0x500/0x6c4   search_binary_handler+0x13c/0x420   exe…&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer() commit 6f755e85c332 (&amp;#34;coresight: Add helper for inserting synchronization packets&amp;#34;) removed trailing &amp;#39;\0&amp;#39; from barrier_pkt array and updated the call sites like etb_update_buffer() to have proper checks for barrier_pkt size before read but missed updating tmc_update_etf_buffer() which still reads barrier_pkt past the array size resulting in KASAN out-of-bounds bug. Fix this by adding a check for barrier_pkt size before accessing like it is done in etb_update_buffer().  BUG: KASAN: global-out-of-bounds in tmc_update_etf_buffer+0x4b8/0x698  Read of size 4 at addr ffffffd05b7d1030 by task perf/2629  Call trace:   dump_backtrace+0x0/0x27c   show_stack+0x20/0x2c   dump_stack+0x11c/0x188   print_address_description+0x3c/0x4a4   __kasan_report+0x140/0x164   kasan_report+0x10/0x18   __asan_report_load4_noabort+0x1c/0x24   tmc_update_etf_buffer+0x4b8/0x698   etm_event_stop+0x248/0x2d8   etm_event_del+0x20/0x2c   event_sched_out+0x214/0x6f0   group_sched_out+0xd0/0x270   ctx_sched_out+0x2ec/0x518   __perf_event_task_sched_out+0x4fc/0xe6c   __schedule+0x1094/0x16a0   preempt_schedule_irq+0x88/0x170   arm64_preempt_schedule_irq+0xf0/0x18c   el1_irq+0xe8/0x180   perf_event_exec+0x4d8/0x56c   setup_new_exec+0x204/0x400   load_elf_binary+0x72c/0x18c0   search_binary_handler+0x13c/0x420   load_script+0x500/0x6c4   search_binary_handler+0x13c/0x420   exe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47346</guid>
    </item>
  </channel>
</rss>
