<?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>Sun, 04 Oct 2026 02:04:40 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:11486 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:11486</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 53 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: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (CVE-2024-27399)
  * kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE (CVE-2024-38564)
  * kernel: bpf: Fix a kernel verifier crash in stacksafe() (CVE-2024-45020)
  * kernel: nfsd: ensure that nfsd4_fattr_args.context is zeroed out (CVE-2024-46697)
  * kernel: bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (CVE-2024-47675)
  * kernel: bpf: Fix a sdiv overflow issue (CVE-2024-49888)
  * kernel: arm64: probes: Remove broken LDR (literal) uprobe support (CVE-2024-50099)
  * kernel: xfrm: fix one more kernel-infoleak in algo dumping (CVE-2024-50110)
  * kernel: Bluetooth: SCO: Fix UAF on sco_sock_timeout (CVE-2024-50125)
  * kernel: Bluetooth: ISO: Fix UAF on iso_sock_timeout (CVE-2024-50124)
  * kernel: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory (CVE-2024-50115)
  * kernel: xfrm: validate new SA&amp;amp;#39;s prefixlen using SA family when sel.family is unset (CVE-2024-50142)
  * kernel: Bluetooth: bnep: fix wild-memory-access in proto_unregister (CVE-2024-50148)
  * kernel: irqchip/gic-v4: Don&amp;#39;t allow a VMOVP on a dying VPE (CVE-2024-50192)
  * kernel: Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs (CVE-2024-50255)
  * kernel: sched/numa: Fix the potential null pointer dereference in task_numa_work() (CVE-2024-50223)
  * kerne…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 53 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: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (CVE-2024-27399)
  * kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE (CVE-2024-38564)
  * kernel: bpf: Fix a kernel verifier crash in stacksafe() (CVE-2024-45020)
  * kernel: nfsd: ensure that nfsd4_fattr_args.context is zeroed out (CVE-2024-46697)
  * kernel: bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() (CVE-2024-47675)
  * kernel: bpf: Fix a sdiv overflow issue (CVE-2024-49888)
  * kernel: arm64: probes: Remove broken LDR (literal) uprobe support (CVE-2024-50099)
  * kernel: xfrm: fix one more kernel-infoleak in algo dumping (CVE-2024-50110)
  * kernel: Bluetooth: SCO: Fix UAF on sco_sock_timeout (CVE-2024-50125)
  * kernel: Bluetooth: ISO: Fix UAF on iso_sock_timeout (CVE-2024-50124)
  * kernel: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory (CVE-2024-50115)
  * kernel: xfrm: validate new SA&amp;amp;#39;s prefixlen using SA family when sel.family is unset (CVE-2024-50142)
  * kernel: Bluetooth: bnep: fix wild-memory-access in proto_unregister (CVE-2024-50148)
  * kernel: irqchip/gic-v4: Don&amp;#39;t allow a VMOVP on a dying VPE (CVE-2024-50192)
  * kernel: Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs (CVE-2024-50255)
  * kernel: sched/numa: Fix the potential null pointer dereference in task_numa_work() (CVE-2024-50223)
  * kerne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:11486</guid>
    </item>
    <item>
      <title>bdu:2025-01785</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01785</link>
      <description>bdu:2025-01785</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01785</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-45020</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-45020</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-45020</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0870 — 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-0870</link>
      <description>certfr-2024-avi-0870</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0870</guid>
    </item>
    <item>
      <title>cnvd-2024-39479</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-39479</link>
      <description>cnvd-2024-39479</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-39479</guid>
    </item>
    <item>
      <title>EUVD-2026-346077</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346077</link>
      <description>EUVD-2026-346077</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346077</guid>
    </item>
    <item>
      <title>fkie_cve-2024-45020</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-45020</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix a kernel verifier crash in stacksafe()&lt;/p&gt;
&lt;p&gt;Daniel Hodges reported a kernel verifier crash when playing with sched-ext.
Further investigation shows that the crash is due to invalid memory access
in stacksafe(). More specifically, it is the following code:&lt;/p&gt;
&lt;p&gt;if (exact != NOT_EXACT &amp;amp;&amp;amp;
        old-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] !=
        cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE])
            return false;&lt;/p&gt;
&lt;p&gt;The &amp;#39;i&amp;#39; iterates old-&amp;gt;allocated_stack.
If cur-&amp;gt;allocated_stack &amp;lt; old-&amp;gt;allocated_stack the out-of-bound
access will happen.&lt;/p&gt;
&lt;p&gt;To fix the issue add &amp;#39;i &amp;gt;= cur-&amp;gt;allocated_stack&amp;#39; check such that if
the condition is true, stacksafe() should fail. Otherwise,
cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.&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;bpf: Fix a kernel verifier crash in stacksafe()&lt;/p&gt;
&lt;p&gt;Daniel Hodges reported a kernel verifier crash when playing with sched-ext.
Further investigation shows that the crash is due to invalid memory access
in stacksafe(). More specifically, it is the following code:&lt;/p&gt;
&lt;p&gt;if (exact != NOT_EXACT &amp;amp;&amp;amp;
        old-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] !=
        cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE])
            return false;&lt;/p&gt;
&lt;p&gt;The &amp;#39;i&amp;#39; iterates old-&amp;gt;allocated_stack.
If cur-&amp;gt;allocated_stack &amp;lt; old-&amp;gt;allocated_stack the out-of-bound
access will happen.&lt;/p&gt;
&lt;p&gt;To fix the issue add &amp;#39;i &amp;gt;= cur-&amp;gt;allocated_stack&amp;#39; check such that if
the condition is true, stacksafe() should fail. Otherwise,
cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-45020</guid>
    </item>
    <item>
      <title>GHSA-jf76-2c3p-rhc5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jf76-2c3p-rhc5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix a kernel verifier crash in stacksafe()&lt;/p&gt;
&lt;p&gt;Daniel Hodges reported a kernel verifier crash when playing with sched-ext.
Further investigation shows that the crash is due to invalid memory access
in stacksafe(). More specifically, it is the following code:&lt;/p&gt;
&lt;p&gt;if (exact != NOT_EXACT &amp;amp;&amp;amp;
        old-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] !=
        cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE])
            return false;&lt;/p&gt;
&lt;p&gt;The &amp;#39;i&amp;#39; iterates old-&amp;gt;allocated_stack.
If cur-&amp;gt;allocated_stack &amp;lt; old-&amp;gt;allocated_stack the out-of-bound
access will happen.&lt;/p&gt;
&lt;p&gt;To fix the issue add &amp;#39;i &amp;gt;= cur-&amp;gt;allocated_stack&amp;#39; check such that if
the condition is true, stacksafe() should fail. Otherwise,
cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.&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;bpf: Fix a kernel verifier crash in stacksafe()&lt;/p&gt;
&lt;p&gt;Daniel Hodges reported a kernel verifier crash when playing with sched-ext.
Further investigation shows that the crash is due to invalid memory access
in stacksafe(). More specifically, it is the following code:&lt;/p&gt;
&lt;p&gt;if (exact != NOT_EXACT &amp;amp;&amp;amp;
        old-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] !=
        cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE])
            return false;&lt;/p&gt;
&lt;p&gt;The &amp;#39;i&amp;#39; iterates old-&amp;gt;allocated_stack.
If cur-&amp;gt;allocated_stack &amp;lt; old-&amp;gt;allocated_stack the out-of-bound
access will happen.&lt;/p&gt;
&lt;p&gt;To fix the issue add &amp;#39;i &amp;gt;= cur-&amp;gt;allocated_stack&amp;#39; check such that if
the condition is true, stacksafe() should fail. Otherwise,
cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jf76-2c3p-rhc5</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-45020 — bpf: Fix a kernel verifier crash in stacksafe()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-45020</link>
      <description>msrc_CVE-2024-45020</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-45020</guid>
    </item>
    <item>
      <title>OESA-2024-2154 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
jfs: fix null ptr deref in dtInsertEntry&#13;
&#13;
[syzbot reported]
general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 5061 Comm: syz-executor404 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:dtInsertEntry+0xd0c/0x1780 fs/jfs/jfs_dtree.c:3713
...
[Analyze]
In dtInsertEntry(), when the pointer h has the same value as p, after writing
name in UniStrncpy_to_le(), p-&amp;amp;gt;header.flag will be cleared. This will cause the
previously true judgment &amp;amp;quot;p-&amp;amp;gt;header.flag &amp;amp;amp; BT-LEAF&amp;amp;quot; to change to no after writing
the name operation, this leads to entering an incorrect branch and accessing the
uninitialized object ih when judging this condition for the second time.&#13;
&#13;
[Fix]
After got the page, check freelist first, if freelist == 0 then exit dtInsert()
and return -EINVAL.(CVE-2024-44939)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: gadget: core: Check for unset descriptor&#13;
&#13;
Make sure the descriptor has been set before looking at maxpacket.
This fixes a null pointer panic in this case.&#13;
&#13;
This may happen if the gadget doesn&amp;amp;apos;t properly set up the endpoint
f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
jfs: fix null ptr deref in dtInsertEntry&#13;
&#13;
[syzbot reported]
general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 5061 Comm: syz-executor404 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:dtInsertEntry+0xd0c/0x1780 fs/jfs/jfs_dtree.c:3713
...
[Analyze]
In dtInsertEntry(), when the pointer h has the same value as p, after writing
name in UniStrncpy_to_le(), p-&amp;amp;gt;header.flag will be cleared. This will cause the
previously true judgment &amp;amp;quot;p-&amp;amp;gt;header.flag &amp;amp;amp; BT-LEAF&amp;amp;quot; to change to no after writing
the name operation, this leads to entering an incorrect branch and accessing the
uninitialized object ih when judging this condition for the second time.&#13;
&#13;
[Fix]
After got the page, check freelist first, if freelist == 0 then exit dtInsert()
and return -EINVAL.(CVE-2024-44939)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: gadget: core: Check for unset descriptor&#13;
&#13;
Make sure the descriptor has been set before looking at maxpacket.
This fixes a null pointer panic in this case.&#13;
&#13;
This may happen if the gadget doesn&amp;amp;apos;t properly set up the endpoint
f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2154</guid>
    </item>
    <item>
      <title>RHSA-2024:11486 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:11486</link>
      <description>&lt;p&gt;kernel: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE kernel: bpf: Fix a kernel verifier crash in stacksafe() kernel: nfsd: ensure that nfsd4_fattr_args.context is zeroed out kernel: bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() kernel: bpf: Fix a sdiv overflow issue kernel: arm64: probes: Remove broken LDR (literal) uprobe support kernel: xfrm: fix one more kernel-infoleak in algo dumping kernel: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory kernel: Bluetooth: ISO: Fix UAF on iso_sock_timeout kernel: Bluetooth: SCO: Fix UAF on sco_sock_timeout kernel: xfrm: validate new SA&amp;amp;#39;s prefixlen using SA family when sel.family is unset kernel: Bluetooth: bnep: fix wild-memory-access in proto_unregister kernel: irqchip/gic-v4: Don&amp;#39;t allow a VMOVP on a dying VPE kernel: sched/numa: Fix the potential null pointer dereference in task_numa_work() kernel: Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs kernel: bpf: Fix out-of-bounds write in trie_get_next_key()&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE kernel: bpf: Fix a kernel verifier crash in stacksafe() kernel: nfsd: ensure that nfsd4_fattr_args.context is zeroed out kernel: bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() kernel: bpf: Fix a sdiv overflow issue kernel: arm64: probes: Remove broken LDR (literal) uprobe support kernel: xfrm: fix one more kernel-infoleak in algo dumping kernel: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory kernel: Bluetooth: ISO: Fix UAF on iso_sock_timeout kernel: Bluetooth: SCO: Fix UAF on sco_sock_timeout kernel: xfrm: validate new SA&amp;amp;#39;s prefixlen using SA family when sel.family is unset kernel: Bluetooth: bnep: fix wild-memory-access in proto_unregister kernel: irqchip/gic-v4: Don&amp;#39;t allow a VMOVP on a dying VPE kernel: sched/numa: Fix the potential null pointer dereference in task_numa_work() kernel: Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs kernel: bpf: Fix out-of-bounds write in trie_get_next_key()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:11486</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3551-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3551-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:3551-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-45020</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45020</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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a kernel verifier crash in stacksafe() Daniel Hodges reported a kernel verifier crash when playing with sched-ext. Further investigation shows that the crash is due to invalid memory access in stacksafe(). More specifically, it is the following code:     if (exact != NOT_EXACT &amp;amp;&amp;amp;         old-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] !=         cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE])             return false; The &amp;#39;i&amp;#39; iterates old-&amp;gt;allocated_stack. If cur-&amp;gt;allocated_stack &amp;lt; old-&amp;gt;allocated_stack the out-of-bound access will happen. To fix the issue add &amp;#39;i &amp;gt;= cur-&amp;gt;allocated_stack&amp;#39; check such that if the condition is true, stacksafe() should fail. Otherwise, cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.&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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a kernel verifier crash in stacksafe() Daniel Hodges reported a kernel verifier crash when playing with sched-ext. Further investigation shows that the crash is due to invalid memory access in stacksafe(). More specifically, it is the following code:     if (exact != NOT_EXACT &amp;amp;&amp;amp;         old-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] !=         cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE])             return false; The &amp;#39;i&amp;#39; iterates old-&amp;gt;allocated_stack. If cur-&amp;gt;allocated_stack &amp;lt; old-&amp;gt;allocated_stack the out-of-bound access will happen. To fix the issue add &amp;#39;i &amp;gt;= cur-&amp;gt;allocated_stack&amp;#39; check such that if the condition is true, stacksafe() should fail. Otherwise, cur-&amp;gt;stack[spi].slot_type[i % BPF_REG_SIZE] memory access is legal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45020</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2124 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2124</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen 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 einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2124</guid>
    </item>
  </channel>
</rss>
