<?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 21:38:16 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:8743 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:8743</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: um: Fix out-of-bounds read in LDT setup (CVE-2022-49395)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: um: Fix out-of-bounds read in LDT setup (CVE-2022-49395)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:8743</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0336 — 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-0336</link>
      <description>certfr-2025-avi-0336</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0336</guid>
    </item>
    <item>
      <title>EUVD-2026-310528</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310528</link>
      <description>EUVD-2026-310528</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310528</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49395</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49395</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: Fix out-of-bounds read in LDT setup&lt;/p&gt;
&lt;p&gt;syscall_stub_data() expects the data_count parameter to be the number of
longs, not bytes.&lt;/p&gt;
&lt;p&gt;==================================================================
 BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0
 Read of size 128 at addr 000000006411f6f0 by task swapper/1&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18
 Call Trace:
  show_stack.cold+0x166/0x2a7
  __dump_stack+0x3a/0x43
  dump_stack_lvl+0x1f/0x27
  print_report.cold+0xdb/0xf81
  kasan_report+0x119/0x1f0
  kasan_check_range+0x3a3/0x440
  memcpy+0x52/0x140
  syscall_stub_data+0x70/0xe0
  write_ldt_entry+0xac/0x190
  init_new_ldt+0x515/0x960
  init_new_context+0x2c4/0x4d0
  mm_init.constprop.0+0x5ed/0x760
  mm_alloc+0x118/0x170
  0x60033f48
  do_one_initcall+0x1d7/0x860
  0x60003e7b
  kernel_init+0x6e/0x3d4
  new_thread_handler+0x1e7/0x2c0&lt;/p&gt;
&lt;p&gt;The buggy address belongs to stack of task swapper/1
  and is located at offset 64 in frame:
  init_new_ldt+0x0/0x960&lt;/p&gt;
&lt;p&gt;This frame has 2 objects:
  [32, 40) &amp;#39;addr&amp;#39;
  [64, 80) &amp;#39;desc&amp;#39;
 ==================================================================&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;um: Fix out-of-bounds read in LDT setup&lt;/p&gt;
&lt;p&gt;syscall_stub_data() expects the data_count parameter to be the number of
longs, not bytes.&lt;/p&gt;
&lt;p&gt;==================================================================
 BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0
 Read of size 128 at addr 000000006411f6f0 by task swapper/1&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18
 Call Trace:
  show_stack.cold+0x166/0x2a7
  __dump_stack+0x3a/0x43
  dump_stack_lvl+0x1f/0x27
  print_report.cold+0xdb/0xf81
  kasan_report+0x119/0x1f0
  kasan_check_range+0x3a3/0x440
  memcpy+0x52/0x140
  syscall_stub_data+0x70/0xe0
  write_ldt_entry+0xac/0x190
  init_new_ldt+0x515/0x960
  init_new_context+0x2c4/0x4d0
  mm_init.constprop.0+0x5ed/0x760
  mm_alloc+0x118/0x170
  0x60033f48
  do_one_initcall+0x1d7/0x860
  0x60003e7b
  kernel_init+0x6e/0x3d4
  new_thread_handler+0x1e7/0x2c0&lt;/p&gt;
&lt;p&gt;The buggy address belongs to stack of task swapper/1
  and is located at offset 64 in frame:
  init_new_ldt+0x0/0x960&lt;/p&gt;
&lt;p&gt;This frame has 2 objects:
  [32, 40) &amp;#39;addr&amp;#39;
  [64, 80) &amp;#39;desc&amp;#39;
 ==================================================================&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49395</guid>
    </item>
    <item>
      <title>GHSA-pxwr-cc58-gq3m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pxwr-cc58-gq3m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: Fix out-of-bounds read in LDT setup&lt;/p&gt;
&lt;p&gt;syscall_stub_data() expects the data_count parameter to be the number of
longs, not bytes.&lt;/p&gt;
&lt;p&gt;==================================================================
 BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0
 Read of size 128 at addr 000000006411f6f0 by task swapper/1&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18
 Call Trace:
  show_stack.cold+0x166/0x2a7
  __dump_stack+0x3a/0x43
  dump_stack_lvl+0x1f/0x27
  print_report.cold+0xdb/0xf81
  kasan_report+0x119/0x1f0
  kasan_check_range+0x3a3/0x440
  memcpy+0x52/0x140
  syscall_stub_data+0x70/0xe0
  write_ldt_entry+0xac/0x190
  init_new_ldt+0x515/0x960
  init_new_context+0x2c4/0x4d0
  mm_init.constprop.0+0x5ed/0x760
  mm_alloc+0x118/0x170
  0x60033f48
  do_one_initcall+0x1d7/0x860
  0x60003e7b
  kernel_init+0x6e/0x3d4
  new_thread_handler+0x1e7/0x2c0&lt;/p&gt;
&lt;p&gt;The buggy address belongs to stack of task swapper/1
  and is located at offset 64 in frame:
  init_new_ldt+0x0/0x960&lt;/p&gt;
&lt;p&gt;This frame has 2 objects:
  [32, 40) &amp;#39;addr&amp;#39;
  [64, 80) &amp;#39;desc&amp;#39;
 ==================================================================&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;um: Fix out-of-bounds read in LDT setup&lt;/p&gt;
&lt;p&gt;syscall_stub_data() expects the data_count parameter to be the number of
longs, not bytes.&lt;/p&gt;
&lt;p&gt;==================================================================
 BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0
 Read of size 128 at addr 000000006411f6f0 by task swapper/1&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18
 Call Trace:
  show_stack.cold+0x166/0x2a7
  __dump_stack+0x3a/0x43
  dump_stack_lvl+0x1f/0x27
  print_report.cold+0xdb/0xf81
  kasan_report+0x119/0x1f0
  kasan_check_range+0x3a3/0x440
  memcpy+0x52/0x140
  syscall_stub_data+0x70/0xe0
  write_ldt_entry+0xac/0x190
  init_new_ldt+0x515/0x960
  init_new_context+0x2c4/0x4d0
  mm_init.constprop.0+0x5ed/0x760
  mm_alloc+0x118/0x170
  0x60033f48
  do_one_initcall+0x1d7/0x860
  0x60003e7b
  kernel_init+0x6e/0x3d4
  new_thread_handler+0x1e7/0x2c0&lt;/p&gt;
&lt;p&gt;The buggy address belongs to stack of task swapper/1
  and is located at offset 64 in frame:
  init_new_ldt+0x0/0x960&lt;/p&gt;
&lt;p&gt;This frame has 2 objects:
  [32, 40) &amp;#39;addr&amp;#39;
  [64, 80) &amp;#39;desc&amp;#39;
 ==================================================================&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pxwr-cc58-gq3m</guid>
    </item>
    <item>
      <title>OESA-2025-1370 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1370</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111&lt;/p&gt;
&lt;p&gt;The bug was found during fuzzing. Stacktrace locates it in
ath5k_eeprom_convert_pcal_info_5111.
When none of the curve is selected in the loop, idx can go
up to AR5K_EEPROM_N_PD_CURVES. The line makes pd out of bound.
pd = &amp;amp;amp;chinfo[pier].pd_curves[idx];&lt;/p&gt;
&lt;p&gt;There are many OOB writes using pd later in the code. So I
added a sanity check for idx. Checks for other loops involving
AR5K_EEPROM_N_PD_CURVES are not needed as the loop index is not
used outside the loops.&lt;/p&gt;
&lt;p&gt;The patch is NOT tested with real device.&lt;/p&gt;
&lt;p&gt;The following is the fuzzing report&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
Write of size 1 at addr ffff8880174a4d60 by task modprobe/214&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 214 Comm: modprobe Not tainted 5.6.0 #1
Call Trace:
 dump_stack+0x76/0xa0
 print_address_description.constprop.0+0x16/0x200
 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 __kasan_report.cold+0x37/0x7c
 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 kasan_report+0xe/0x20
 ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 ? apic_timer_interrupt+0xa/0x20
 ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k]
 ? ath5k_pci_eeprom_read+0x228/0x3c0 [ath5k]
 ath5k_eeprom_init+0x2513/0x6290 [ath5k]
 ? ath5k_…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111&lt;/p&gt;
&lt;p&gt;The bug was found during fuzzing. Stacktrace locates it in
ath5k_eeprom_convert_pcal_info_5111.
When none of the curve is selected in the loop, idx can go
up to AR5K_EEPROM_N_PD_CURVES. The line makes pd out of bound.
pd = &amp;amp;amp;chinfo[pier].pd_curves[idx];&lt;/p&gt;
&lt;p&gt;There are many OOB writes using pd later in the code. So I
added a sanity check for idx. Checks for other loops involving
AR5K_EEPROM_N_PD_CURVES are not needed as the loop index is not
used outside the loops.&lt;/p&gt;
&lt;p&gt;The patch is NOT tested with real device.&lt;/p&gt;
&lt;p&gt;The following is the fuzzing report&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
Write of size 1 at addr ffff8880174a4d60 by task modprobe/214&lt;/p&gt;
&lt;p&gt;CPU: 0 PID: 214 Comm: modprobe Not tainted 5.6.0 #1
Call Trace:
 dump_stack+0x76/0xa0
 print_address_description.constprop.0+0x16/0x200
 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 __kasan_report.cold+0x37/0x7c
 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 kasan_report+0xe/0x20
 ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k]
 ? apic_timer_interrupt+0xa/0x20
 ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k]
 ? ath5k_pci_eeprom_read+0x228/0x3c0 [ath5k]
 ath5k_eeprom_init+0x2513/0x6290 [ath5k]
 ? ath5k_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1370</guid>
    </item>
    <item>
      <title>RHSA-2025:10179 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:10179</link>
      <description>&lt;p&gt;kernel: Bluetooth: Fix use after free in hci_send_acl kernel: scsi: libfc: Fix use after free in fc_exch_abts_resp() kernel: dm ioctl: prevent potential spectre v1 gadget kernel: mt76: fix use-after-free by removing a non-RCU wcid pointer kernel: um: Fix out-of-bounds read in LDT setup&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth: Fix use after free in hci_send_acl kernel: scsi: libfc: Fix use after free in fc_exch_abts_resp() kernel: dm ioctl: prevent potential spectre v1 gadget kernel: mt76: fix use-after-free by removing a non-RCU wcid pointer kernel: um: Fix out-of-bounds read in LDT setup&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:10179</guid>
    </item>
    <item>
      <title>RHSA-2025:8743 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:8743</link>
      <description>&lt;p&gt;kernel: um: Fix out-of-bounds read in LDT setup&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: um: Fix out-of-bounds read in LDT setup&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:8743</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1293-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1293-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:1293-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49395</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49395</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 143 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: um: Fix out-of-bounds read in LDT setup syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes.  ==================================================================  BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0  Read of size 128 at addr 000000006411f6f0 by task swapper/1  CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18  Call Trace:   show_stack.cold+0x166/0x2a7   __dump_stack+0x3a/0x43   dump_stack_lvl+0x1f/0x27   print_report.cold+0xdb/0xf81   kasan_report+0x119/0x1f0   kasan_check_range+0x3a3/0x440   memcpy+0x52/0x140   syscall_stub_data+0x70/0xe0   write_ldt_entry+0xac/0x190   init_new_ldt+0x515/0x960   init_new_context+0x2c4/0x4d0   mm_init.constprop.0+0x5ed/0x760   mm_alloc+0x118/0x170   0x60033f48   do_one_initcall+0x1d7/0x860   0x60003e7b   kernel_init+0x6e/0x3d4   new_thread_handler+0x1e7/0x2c0  The buggy address belongs to stack of task swapper/1   and is located at offset 64 in frame:   init_new_ldt+0x0/0x960  This frame has 2 objects:   [32, 40) &amp;#39;addr&amp;#39;   [64, 80) &amp;#39;desc&amp;#39;  ==================================================================&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 143 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: um: Fix out-of-bounds read in LDT setup syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes.  ==================================================================  BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0  Read of size 128 at addr 000000006411f6f0 by task swapper/1  CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18  Call Trace:   show_stack.cold+0x166/0x2a7   __dump_stack+0x3a/0x43   dump_stack_lvl+0x1f/0x27   print_report.cold+0xdb/0xf81   kasan_report+0x119/0x1f0   kasan_check_range+0x3a3/0x440   memcpy+0x52/0x140   syscall_stub_data+0x70/0xe0   write_ldt_entry+0xac/0x190   init_new_ldt+0x515/0x960   init_new_context+0x2c4/0x4d0   mm_init.constprop.0+0x5ed/0x760   mm_alloc+0x118/0x170   0x60033f48   do_one_initcall+0x1d7/0x860   0x60003e7b   kernel_init+0x6e/0x3d4   new_thread_handler+0x1e7/0x2c0  The buggy address belongs to stack of task swapper/1   and is located at offset 64 in frame:   init_new_ldt+0x0/0x960  This frame has 2 objects:   [32, 40) &amp;#39;addr&amp;#39;   [64, 80) &amp;#39;desc&amp;#39;  ==================================================================&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49395</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1271 — Linux Kernel: Schwachstelle ermöglicht Denial of Service und Offenlegung von Informationen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1271</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1271</guid>
    </item>
  </channel>
</rss>
