<?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 10:23:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72110</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72110</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-2026-72110</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1163 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</link>
      <description>certfr-2026-avi-1163</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</guid>
    </item>
    <item>
      <title>EUVD-2026-357885</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357885</link>
      <description>EUVD-2026-357885</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357885</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72110</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72110</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf,fork: wipe -&amp;gt;bpf_storage before bailouts that access it&lt;/p&gt;
&lt;p&gt;Currently, copy_process() can bail out to free_task() before p-&amp;gt;bpf_storage
has been initialized, with this call graph (shown here for the
!CONFIG_MEMCG case):&lt;/p&gt;
&lt;p&gt;copy_process
  dup_task_struct
    arch_dup_task_struct
      [copies the entire task_struct, including -&amp;gt;bpf_storage member]
  [RLIMIT_NPROC check fails]
  delayed_free_task
    free_task
      bpf_task_storage_free
        rcu_dereference(task-&amp;gt;bpf_storage)
        bpf_local_storage_destroy&lt;/p&gt;
&lt;p&gt;In this case, the nascent task&amp;#39;s -&amp;gt;bpf_storage member that
bpf_local_storage_destroy() operates on is a plain copy of the parent&amp;#39;s
-&amp;gt;bpf_storage pointer, not a real initialized pointer.
This leads to badness (kernel hangs, UAF).&lt;/p&gt;
&lt;p&gt;This is reachable as long as the process calling fork() has been inserted
into a task storage map.&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,fork: wipe -&amp;gt;bpf_storage before bailouts that access it&lt;/p&gt;
&lt;p&gt;Currently, copy_process() can bail out to free_task() before p-&amp;gt;bpf_storage
has been initialized, with this call graph (shown here for the
!CONFIG_MEMCG case):&lt;/p&gt;
&lt;p&gt;copy_process
  dup_task_struct
    arch_dup_task_struct
      [copies the entire task_struct, including -&amp;gt;bpf_storage member]
  [RLIMIT_NPROC check fails]
  delayed_free_task
    free_task
      bpf_task_storage_free
        rcu_dereference(task-&amp;gt;bpf_storage)
        bpf_local_storage_destroy&lt;/p&gt;
&lt;p&gt;In this case, the nascent task&amp;#39;s -&amp;gt;bpf_storage member that
bpf_local_storage_destroy() operates on is a plain copy of the parent&amp;#39;s
-&amp;gt;bpf_storage pointer, not a real initialized pointer.
This leads to badness (kernel hangs, UAF).&lt;/p&gt;
&lt;p&gt;This is reachable as long as the process calling fork() has been inserted
into a task storage map.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72110</guid>
    </item>
    <item>
      <title>GHSA-9wff-g7fh-998r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9wff-g7fh-998r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf,fork: wipe -&amp;gt;bpf_storage before bailouts that access it&lt;/p&gt;
&lt;p&gt;Currently, copy_process() can bail out to free_task() before p-&amp;gt;bpf_storage
has been initialized, with this call graph (shown here for the
!CONFIG_MEMCG case):&lt;/p&gt;
&lt;p&gt;copy_process
  dup_task_struct
    arch_dup_task_struct
      [copies the entire task_struct, including -&amp;gt;bpf_storage member]
  [RLIMIT_NPROC check fails]
  delayed_free_task
    free_task
      bpf_task_storage_free
        rcu_dereference(task-&amp;gt;bpf_storage)
        bpf_local_storage_destroy&lt;/p&gt;
&lt;p&gt;In this case, the nascent task&amp;#39;s -&amp;gt;bpf_storage member that
bpf_local_storage_destroy() operates on is a plain copy of the parent&amp;#39;s
-&amp;gt;bpf_storage pointer, not a real initialized pointer.
This leads to badness (kernel hangs, UAF).&lt;/p&gt;
&lt;p&gt;This is reachable as long as the process calling fork() has been inserted
into a task storage map.&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,fork: wipe -&amp;gt;bpf_storage before bailouts that access it&lt;/p&gt;
&lt;p&gt;Currently, copy_process() can bail out to free_task() before p-&amp;gt;bpf_storage
has been initialized, with this call graph (shown here for the
!CONFIG_MEMCG case):&lt;/p&gt;
&lt;p&gt;copy_process
  dup_task_struct
    arch_dup_task_struct
      [copies the entire task_struct, including -&amp;gt;bpf_storage member]
  [RLIMIT_NPROC check fails]
  delayed_free_task
    free_task
      bpf_task_storage_free
        rcu_dereference(task-&amp;gt;bpf_storage)
        bpf_local_storage_destroy&lt;/p&gt;
&lt;p&gt;In this case, the nascent task&amp;#39;s -&amp;gt;bpf_storage member that
bpf_local_storage_destroy() operates on is a plain copy of the parent&amp;#39;s
-&amp;gt;bpf_storage pointer, not a real initialized pointer.
This leads to badness (kernel hangs, UAF).&lt;/p&gt;
&lt;p&gt;This is reachable as long as the process calling fork() has been inserted
into a task storage map.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9wff-g7fh-998r</guid>
    </item>
    <item>
      <title>OESA-2026-3704 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3704</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: 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;net: hns3: add VLAN id validation before using&lt;/p&gt;
&lt;p&gt;Currently, the VLAN id may be used without validation when
receive a VLAN configuration mailbox from VF. The length of
vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause
out-of-bounds memory access once the VLAN id is bigger than
or equal to VLAN_N_VID.&lt;/p&gt;
&lt;p&gt;Therefore, VLAN id needs to be checked to ensure it is within
the range of VLAN_N_VID.(CVE-2025-71112)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix string copying in parse_apply_sb_mount_options()&lt;/p&gt;
&lt;p&gt;strscpy_pad() can&amp;amp;apos;t be used to copy a non-NUL-term string into a NUL-term
string of possibly bigger size.  Commit 0efc5990bca5 (&amp;amp;quot;string.h: Introduce
memtostr() and memtostr_pad()&amp;amp;quot;) provides additional information in that
regard.  So if this happens, the following warning is observed:&lt;/p&gt;
&lt;p&gt;strnlen: detected buffer overflow: 65 byte read of buffer size 64
WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Modules linked in:
CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 __fortify_panic+0x1f/0x30 lib/s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: 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;net: hns3: add VLAN id validation before using&lt;/p&gt;
&lt;p&gt;Currently, the VLAN id may be used without validation when
receive a VLAN configuration mailbox from VF. The length of
vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause
out-of-bounds memory access once the VLAN id is bigger than
or equal to VLAN_N_VID.&lt;/p&gt;
&lt;p&gt;Therefore, VLAN id needs to be checked to ensure it is within
the range of VLAN_N_VID.(CVE-2025-71112)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix string copying in parse_apply_sb_mount_options()&lt;/p&gt;
&lt;p&gt;strscpy_pad() can&amp;amp;apos;t be used to copy a non-NUL-term string into a NUL-term
string of possibly bigger size.  Commit 0efc5990bca5 (&amp;amp;quot;string.h: Introduce
memtostr() and memtostr_pad()&amp;amp;quot;) provides additional information in that
regard.  So if this happens, the following warning is observed:&lt;/p&gt;
&lt;p&gt;strnlen: detected buffer overflow: 65 byte read of buffer size 64
WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Modules linked in:
CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 __fortify_panic+0x1f/0x30 lib/s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3704</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72110</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72110</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe -&amp;gt;bpf_storage before bailouts that access it Currently, copy_process() can bail out to free_task() before p-&amp;gt;bpf_storage has been initialized, with this call graph (shown here for the !CONFIG_MEMCG case): copy_process   dup_task_struct     arch_dup_task_struct       [copies the entire task_struct, including -&amp;gt;bpf_storage member]   [RLIMIT_NPROC check fails]   delayed_free_task     free_task       bpf_task_storage_free         rcu_dereference(task-&amp;gt;bpf_storage)         bpf_local_storage_destroy In this case, the nascent task&amp;#39;s -&amp;gt;bpf_storage member that bpf_local_storage_destroy() operates on is a plain copy of the parent&amp;#39;s -&amp;gt;bpf_storage pointer, not a real initialized pointer. This leads to badness (kernel hangs, UAF). This is reachable as long as the process calling fork() has been inserted into a task storage map.&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe -&amp;gt;bpf_storage before bailouts that access it Currently, copy_process() can bail out to free_task() before p-&amp;gt;bpf_storage has been initialized, with this call graph (shown here for the !CONFIG_MEMCG case): copy_process   dup_task_struct     arch_dup_task_struct       [copies the entire task_struct, including -&amp;gt;bpf_storage member]   [RLIMIT_NPROC check fails]   delayed_free_task     free_task       bpf_task_storage_free         rcu_dereference(task-&amp;gt;bpf_storage)         bpf_local_storage_destroy In this case, the nascent task&amp;#39;s -&amp;gt;bpf_storage member that bpf_local_storage_destroy() operates on is a plain copy of the parent&amp;#39;s -&amp;gt;bpf_storage pointer, not a real initialized pointer. This leads to badness (kernel hangs, UAF). This is reachable as long as the process calling fork() has been inserted into a task storage map.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72110</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
