<?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:57:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-08059</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-08059</link>
      <description>bdu:2025-08059</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-08059</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-40915</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-40915</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-40915</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>EUVD-2026-312942</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312942</link>
      <description>EUVD-2026-312942</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312942</guid>
    </item>
    <item>
      <title>fkie_cve-2024-40915</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-40915</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context&lt;/p&gt;
&lt;p&gt;__kernel_map_pages() is a debug function which clears the valid bit in page
table entry for deallocated pages to detect illegal memory accesses to
freed pages.&lt;/p&gt;
&lt;p&gt;This function set/clear the valid bit using __set_memory(). __set_memory()
acquires init_mm&amp;#39;s semaphore, and this operation may sleep. This is
problematic, because  __kernel_map_pages() can be called in atomic context,
and thus is illegal to sleep. An example warning that this causes:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd
preempt_count: 2, expected: 0
CPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[&amp;lt;ffffffff800060dc&amp;gt;] dump_backtrace+0x1c/0x24
[&amp;lt;ffffffff8091ef6e&amp;gt;] show_stack+0x2c/0x38
[&amp;lt;ffffffff8092baf8&amp;gt;] dump_stack_lvl+0x5a/0x72
[&amp;lt;ffffffff8092bb24&amp;gt;] dump_stack+0x14/0x1c
[&amp;lt;ffffffff8003b7ac&amp;gt;] __might_resched+0x104/0x10e
[&amp;lt;ffffffff8003b7f4&amp;gt;] __might_sleep+0x3e/0x62
[&amp;lt;ffffffff8093276a&amp;gt;] down_write+0x20/0x72
[&amp;lt;ffffffff8000cf00&amp;gt;] __set_memory+0x82/0x2fa
[&amp;lt;ffffffff8000d324&amp;gt;] __kernel_map_pages+0x5a/0xd4
[&amp;lt;ffffffff80196cca&amp;gt;] __alloc_pages_bulk+0x3b2/0x43a
[&amp;lt;ffffffff8018ee82&amp;gt;] __vmalloc_node_range+0x196/0x6ba
[&amp;lt;ffffffff80011904&amp;gt;] copy_process+0x72c/0x17ec
[&amp;lt;ffffffff80012ab4&amp;gt;] kernel_clone+0x60/0x2fe
[&amp;lt;fff…&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;riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context&lt;/p&gt;
&lt;p&gt;__kernel_map_pages() is a debug function which clears the valid bit in page
table entry for deallocated pages to detect illegal memory accesses to
freed pages.&lt;/p&gt;
&lt;p&gt;This function set/clear the valid bit using __set_memory(). __set_memory()
acquires init_mm&amp;#39;s semaphore, and this operation may sleep. This is
problematic, because  __kernel_map_pages() can be called in atomic context,
and thus is illegal to sleep. An example warning that this causes:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd
preempt_count: 2, expected: 0
CPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[&amp;lt;ffffffff800060dc&amp;gt;] dump_backtrace+0x1c/0x24
[&amp;lt;ffffffff8091ef6e&amp;gt;] show_stack+0x2c/0x38
[&amp;lt;ffffffff8092baf8&amp;gt;] dump_stack_lvl+0x5a/0x72
[&amp;lt;ffffffff8092bb24&amp;gt;] dump_stack+0x14/0x1c
[&amp;lt;ffffffff8003b7ac&amp;gt;] __might_resched+0x104/0x10e
[&amp;lt;ffffffff8003b7f4&amp;gt;] __might_sleep+0x3e/0x62
[&amp;lt;ffffffff8093276a&amp;gt;] down_write+0x20/0x72
[&amp;lt;ffffffff8000cf00&amp;gt;] __set_memory+0x82/0x2fa
[&amp;lt;ffffffff8000d324&amp;gt;] __kernel_map_pages+0x5a/0xd4
[&amp;lt;ffffffff80196cca&amp;gt;] __alloc_pages_bulk+0x3b2/0x43a
[&amp;lt;ffffffff8018ee82&amp;gt;] __vmalloc_node_range+0x196/0x6ba
[&amp;lt;ffffffff80011904&amp;gt;] copy_process+0x72c/0x17ec
[&amp;lt;ffffffff80012ab4&amp;gt;] kernel_clone+0x60/0x2fe
[&amp;lt;fff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-40915</guid>
    </item>
    <item>
      <title>GHSA-cxf4-996m-v4m3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cxf4-996m-v4m3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context&lt;/p&gt;
&lt;p&gt;__kernel_map_pages() is a debug function which clears the valid bit in page
table entry for deallocated pages to detect illegal memory accesses to
freed pages.&lt;/p&gt;
&lt;p&gt;This function set/clear the valid bit using __set_memory(). __set_memory()
acquires init_mm&amp;#39;s semaphore, and this operation may sleep. This is
problematic, because  __kernel_map_pages() can be called in atomic context,
and thus is illegal to sleep. An example warning that this causes:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd
preempt_count: 2, expected: 0
CPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[&amp;lt;ffffffff800060dc&amp;gt;] dump_backtrace+0x1c/0x24
[&amp;lt;ffffffff8091ef6e&amp;gt;] show_stack+0x2c/0x38
[&amp;lt;ffffffff8092baf8&amp;gt;] dump_stack_lvl+0x5a/0x72
[&amp;lt;ffffffff8092bb24&amp;gt;] dump_stack+0x14/0x1c
[&amp;lt;ffffffff8003b7ac&amp;gt;] __might_resched+0x104/0x10e
[&amp;lt;ffffffff8003b7f4&amp;gt;] __might_sleep+0x3e/0x62
[&amp;lt;ffffffff8093276a&amp;gt;] down_write+0x20/0x72
[&amp;lt;ffffffff8000cf00&amp;gt;] __set_memory+0x82/0x2fa
[&amp;lt;ffffffff8000d324&amp;gt;] __kernel_map_pages+0x5a/0xd4
[&amp;lt;ffffffff80196cca&amp;gt;] __alloc_pages_bulk+0x3b2/0x43a
[&amp;lt;ffffffff8018ee82&amp;gt;] __vmalloc_node_range+0x196/0x6ba
[&amp;lt;ffffffff80011904&amp;gt;] copy_process+0x72c/0x17ec
[&amp;lt;ffffffff80012ab4&amp;gt;] kernel_clone+0x60/0x2fe
[&amp;lt;fff…&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;riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context&lt;/p&gt;
&lt;p&gt;__kernel_map_pages() is a debug function which clears the valid bit in page
table entry for deallocated pages to detect illegal memory accesses to
freed pages.&lt;/p&gt;
&lt;p&gt;This function set/clear the valid bit using __set_memory(). __set_memory()
acquires init_mm&amp;#39;s semaphore, and this operation may sleep. This is
problematic, because  __kernel_map_pages() can be called in atomic context,
and thus is illegal to sleep. An example warning that this causes:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd
preempt_count: 2, expected: 0
CPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[&amp;lt;ffffffff800060dc&amp;gt;] dump_backtrace+0x1c/0x24
[&amp;lt;ffffffff8091ef6e&amp;gt;] show_stack+0x2c/0x38
[&amp;lt;ffffffff8092baf8&amp;gt;] dump_stack_lvl+0x5a/0x72
[&amp;lt;ffffffff8092bb24&amp;gt;] dump_stack+0x14/0x1c
[&amp;lt;ffffffff8003b7ac&amp;gt;] __might_resched+0x104/0x10e
[&amp;lt;ffffffff8003b7f4&amp;gt;] __might_sleep+0x3e/0x62
[&amp;lt;ffffffff8093276a&amp;gt;] down_write+0x20/0x72
[&amp;lt;ffffffff8000cf00&amp;gt;] __set_memory+0x82/0x2fa
[&amp;lt;ffffffff8000d324&amp;gt;] __kernel_map_pages+0x5a/0xd4
[&amp;lt;ffffffff80196cca&amp;gt;] __alloc_pages_bulk+0x3b2/0x43a
[&amp;lt;ffffffff8018ee82&amp;gt;] __vmalloc_node_range+0x196/0x6ba
[&amp;lt;ffffffff80011904&amp;gt;] copy_process+0x72c/0x17ec
[&amp;lt;ffffffff80012ab4&amp;gt;] kernel_clone+0x60/0x2fe
[&amp;lt;fff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cxf4-996m-v4m3</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-40915 — riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-40915</link>
      <description>msrc_CVE-2024-40915</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-40915</guid>
    </item>
    <item>
      <title>OESA-2024-1941 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1941</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
clk: sunxi-ng: Unregister clocks/resets when unbinding&#13;
&#13;
Currently, unbinding a CCU driver unmaps the device&amp;amp;apos;s MMIO region, while
leaving its clocks/resets and their providers registered. This can cause
a page fault later when some clock operation tries to perform MMIO. Fix
this by separating the CCU initialization from the memory allocation,
and then using a devres callback to unregister the clocks and resets.&#13;
&#13;
This also fixes a memory leak of the `struct ccu_reset`, and uses the
correct owner (the specific platform driver) for the clocks and resets.&#13;
&#13;
Early OF clock providers are never unregistered, and limited error
handling is possible, so they are mostly unchanged. The error reporting
is made more consistent by moving the message inside of_sunxi_ccu_probe.(CVE-2021-47205)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR&#13;
&#13;
In some case, the GDDV returns a package with a buffer which has
zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).&#13;
&#13;
Then the data_vault_read() got NULL point dereference problem when
accessing the 0x10 value in data_vault.&#13;
&#13;
[   71.024560] BUG: kernel NULL pointer dereference, address:
0000000000000010&#13;
&#13;
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or
NULL value…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1941</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-40915</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-40915</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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context __kernel_map_pages() is a debug function which clears the valid bit in page table entry for deallocated pages to detect illegal memory accesses to freed pages. This function set/clear the valid bit using __set_memory(). __set_memory() acquires init_mm&amp;#39;s semaphore, and this operation may sleep. This is problematic, because  __kernel_map_pages() can be called in atomic context, and thus is illegal to sleep. An example warning that this causes: BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd preempt_count: 2, expected: 0 CPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37 Hardware name: riscv-virtio,qemu (DT) Call Trace: [&amp;lt;ffffffff800060dc&amp;gt;] dump_backtrace+0x1c/0x24 [&amp;lt;ffffffff8091ef6e&amp;gt;] show_stack+0x2c/0x38 [&amp;lt;ffffffff8092baf8&amp;gt;] dump_stack_lvl+0x5a/0x72 [&amp;lt;ffffffff8092bb24&amp;gt;] dump_stack+0x14/0x1c [&amp;lt;ffffffff8003b7ac&amp;gt;] __might_resched+0x104/0x10e [&amp;lt;ffffffff8003b7f4&amp;gt;] __might_sleep+0x3e/0x62 [&amp;lt;ffffffff8093276a&amp;gt;] down_write+0x20/0x72 [&amp;lt;ffffffff8000cf00&amp;gt;] __set_memory+0x82/0x2fa [&amp;lt;ffffffff8000d324&amp;gt;] __kernel_map_pages+0x5a/0xd4 [&amp;lt;ffffffff80196cca&amp;gt;] __alloc_pages_bulk+0x3b2/0x43a [&amp;lt;ffffffff8018ee82&amp;gt;] __vmalloc_node_range+0x196/0x6ba [&amp;lt;ffffffff80011904&amp;gt;] copy_process+0x72c/0x17ec [&amp;lt;ffffffff80012ab4&amp;gt;] kernel_clone+0x60/0x2fe [&amp;lt;fffffff…&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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: riscv: rewrite __kernel_map_pages() to fix sleeping in invalid context __kernel_map_pages() is a debug function which clears the valid bit in page table entry for deallocated pages to detect illegal memory accesses to freed pages. This function set/clear the valid bit using __set_memory(). __set_memory() acquires init_mm&amp;#39;s semaphore, and this operation may sleep. This is problematic, because  __kernel_map_pages() can be called in atomic context, and thus is illegal to sleep. An example warning that this causes: BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1578 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2, name: kthreadd preempt_count: 2, expected: 0 CPU: 0 PID: 2 Comm: kthreadd Not tainted 6.9.0-g1d4c6d784ef6 #37 Hardware name: riscv-virtio,qemu (DT) Call Trace: [&amp;lt;ffffffff800060dc&amp;gt;] dump_backtrace+0x1c/0x24 [&amp;lt;ffffffff8091ef6e&amp;gt;] show_stack+0x2c/0x38 [&amp;lt;ffffffff8092baf8&amp;gt;] dump_stack_lvl+0x5a/0x72 [&amp;lt;ffffffff8092bb24&amp;gt;] dump_stack+0x14/0x1c [&amp;lt;ffffffff8003b7ac&amp;gt;] __might_resched+0x104/0x10e [&amp;lt;ffffffff8003b7f4&amp;gt;] __might_sleep+0x3e/0x62 [&amp;lt;ffffffff8093276a&amp;gt;] down_write+0x20/0x72 [&amp;lt;ffffffff8000cf00&amp;gt;] __set_memory+0x82/0x2fa [&amp;lt;ffffffff8000d324&amp;gt;] __kernel_map_pages+0x5a/0xd4 [&amp;lt;ffffffff80196cca&amp;gt;] __alloc_pages_bulk+0x3b2/0x43a [&amp;lt;ffffffff8018ee82&amp;gt;] __vmalloc_node_range+0x196/0x6ba [&amp;lt;ffffffff80011904&amp;gt;] copy_process+0x72c/0x17ec [&amp;lt;ffffffff80012ab4&amp;gt;] kernel_clone+0x60/0x2fe [&amp;lt;fffffff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-40915</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1607 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1607</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1607</guid>
    </item>
  </channel>
</rss>
