<?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 05:32:53 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-10748</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-10748</link>
      <description>bdu:2024-10748</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-10748</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-344509</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344509</link>
      <description>EUVD-2026-344509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344509</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47535</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47535</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/msm/a6xx: Allocate enough space for GMU registers&lt;/p&gt;
&lt;p&gt;In commit 142639a52a01 (&amp;#34;drm/msm/a6xx: fix crashstate capture for
A650&amp;#34;) we changed a6xx_get_gmu_registers() to read 3 sets of
registers. Unfortunately, we didn&amp;#39;t change the memory allocation for
the array. That leads to a KASAN warning (this was on the chromeos-5.4
kernel, which has the problematic commit backported to it):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430
  Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209
  CPU: 5 PID: 209 Comm: A618-worker Tainted: G        W         5.4.156-lockdep #22
  Hardware name: Google Lazor Limozeen without Touchscreen (rev5 - rev8) (DT)
  Call trace:
   dump_backtrace+0x0/0x248
   show_stack+0x20/0x2c
   dump_stack+0x128/0x1ec
   print_address_description+0x88/0x4a0
   __kasan_report+0xfc/0x120
   kasan_report+0x10/0x18
   __asan_report_store8_noabort+0x1c/0x24
   _a6xx_get_gmu_registers+0x144/0x430
   a6xx_gpu_state_get+0x330/0x25d4
   msm_gpu_crashstate_capture+0xa0/0x84c
   recover_worker+0x328/0x838
   kthread_worker_fn+0x32c/0x574
   kthread+0x2dc/0x39c
   ret_from_fork+0x10/0x18&lt;/p&gt;
&lt;p&gt;Allocated by task 209:
   __kasan_kmalloc+0xfc/0x1c4
   kasan_kmalloc+0xc/0x14
   kmem_cache_alloc_trace+0x1f0/0x2a0
   a6xx_gpu_state_get+0x164/0x25d4
   msm_gpu_crashstate_capture+0xa0/0x84c
   recover_worker+0x328/0x838
   kthread_worker_fn+0x32c/0x574
   kthread+0x2dc/0x39c
   ret_…&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;drm/msm/a6xx: Allocate enough space for GMU registers&lt;/p&gt;
&lt;p&gt;In commit 142639a52a01 (&amp;#34;drm/msm/a6xx: fix crashstate capture for
A650&amp;#34;) we changed a6xx_get_gmu_registers() to read 3 sets of
registers. Unfortunately, we didn&amp;#39;t change the memory allocation for
the array. That leads to a KASAN warning (this was on the chromeos-5.4
kernel, which has the problematic commit backported to it):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430
  Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209
  CPU: 5 PID: 209 Comm: A618-worker Tainted: G        W         5.4.156-lockdep #22
  Hardware name: Google Lazor Limozeen without Touchscreen (rev5 - rev8) (DT)
  Call trace:
   dump_backtrace+0x0/0x248
   show_stack+0x20/0x2c
   dump_stack+0x128/0x1ec
   print_address_description+0x88/0x4a0
   __kasan_report+0xfc/0x120
   kasan_report+0x10/0x18
   __asan_report_store8_noabort+0x1c/0x24
   _a6xx_get_gmu_registers+0x144/0x430
   a6xx_gpu_state_get+0x330/0x25d4
   msm_gpu_crashstate_capture+0xa0/0x84c
   recover_worker+0x328/0x838
   kthread_worker_fn+0x32c/0x574
   kthread+0x2dc/0x39c
   ret_from_fork+0x10/0x18&lt;/p&gt;
&lt;p&gt;Allocated by task 209:
   __kasan_kmalloc+0xfc/0x1c4
   kasan_kmalloc+0xc/0x14
   kmem_cache_alloc_trace+0x1f0/0x2a0
   a6xx_gpu_state_get+0x164/0x25d4
   msm_gpu_crashstate_capture+0xa0/0x84c
   recover_worker+0x328/0x838
   kthread_worker_fn+0x32c/0x574
   kthread+0x2dc/0x39c
   ret_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47535</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2008-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2008-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-2024:2008-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47535</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47535</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Allocate enough space for GMU registers In commit 142639a52a01 (&amp;#34;drm/msm/a6xx: fix crashstate capture for A650&amp;#34;) we changed a6xx_get_gmu_registers() to read 3 sets of registers. Unfortunately, we didn&amp;#39;t change the memory allocation for the array. That leads to a KASAN warning (this was on the chromeos-5.4 kernel, which has the problematic commit backported to it):   BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430   Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209   CPU: 5 PID: 209 Comm: A618-worker Tainted: G        W 5.4.156-lockdep #22   Hardware name: Google Lazor Limozeen without Touchscreen (rev5 - rev8) (DT)   Call trace:    dump_backtrace+0x0/0x248    show_stack+0x20/0x2c    dump_stack+0x128/0x1ec    print_address_description+0x88/0x4a0    __kasan_report+0xfc/0x120    kasan_report+0x10/0x18    __asan_report_store8_noabort+0x1c/0x24    _a6xx_get_gmu_registers+0x144/0x430    a6xx_gpu_state_get+0x330/0x25d4    msm_gpu_crashstate_capture+0xa0/0x84c    recover_worker+0x328/0x838    kthread_worker_fn+0x32c/0x574    kthread+0x2dc/0x39c    ret_from_fork+0x10/0x18   Allocated by task 209:    __kasan_kmalloc+0xfc/0x1c4    kasan_kmalloc+0xc/0x14    kmem_cache_alloc_trace+0x1f0/0x2a0    a6xx_gpu_state_get+0x164/0x25d4    msm_gpu_crashstate_capture+0xa0/0x84c    recover_worker+0x328/0x838    kthread_worker_fn+0x32c/0x574    kthread+0x2dc/0x39c    ret_from_fork+0x…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Allocate enough space for GMU registers In commit 142639a52a01 (&amp;#34;drm/msm/a6xx: fix crashstate capture for A650&amp;#34;) we changed a6xx_get_gmu_registers() to read 3 sets of registers. Unfortunately, we didn&amp;#39;t change the memory allocation for the array. That leads to a KASAN warning (this was on the chromeos-5.4 kernel, which has the problematic commit backported to it):   BUG: KASAN: slab-out-of-bounds in _a6xx_get_gmu_registers+0x144/0x430   Write of size 8 at addr ffffff80c89432b0 by task A618-worker/209   CPU: 5 PID: 209 Comm: A618-worker Tainted: G        W 5.4.156-lockdep #22   Hardware name: Google Lazor Limozeen without Touchscreen (rev5 - rev8) (DT)   Call trace:    dump_backtrace+0x0/0x248    show_stack+0x20/0x2c    dump_stack+0x128/0x1ec    print_address_description+0x88/0x4a0    __kasan_report+0xfc/0x120    kasan_report+0x10/0x18    __asan_report_store8_noabort+0x1c/0x24    _a6xx_get_gmu_registers+0x144/0x430    a6xx_gpu_state_get+0x330/0x25d4    msm_gpu_crashstate_capture+0xa0/0x84c    recover_worker+0x328/0x838    kthread_worker_fn+0x32c/0x574    kthread+0x2dc/0x39c    ret_from_fork+0x10/0x18   Allocated by task 209:    __kasan_kmalloc+0xfc/0x1c4    kasan_kmalloc+0xc/0x14    kmem_cache_alloc_trace+0x1f0/0x2a0    a6xx_gpu_state_get+0x164/0x25d4    msm_gpu_crashstate_capture+0xa0/0x84c    recover_worker+0x328/0x838    kthread_worker_fn+0x32c/0x574    kthread+0x2dc/0x39c    ret_from_fork+0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47535</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1235 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1235</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1235</guid>
    </item>
  </channel>
</rss>
