<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T20:02:56.195531+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-72110</id>
    <title>BELL-CVE-2026-72110</title>
    <updated>2026-10-04T20:02:56.317820+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-72110"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</id>
    <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>
    <updated>2026-10-04T20:02:56.317876+00:00</updated>
    <content>certfr-2026-avi-1163</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-357885</id>
    <title>EUVD-2026-357885</title>
    <updated>2026-10-04T20:02:56.317898+00:00</updated>
    <content>EUVD-2026-357885</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-357885"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72110</id>
    <title>fkie_cve-2026-72110</title>
    <updated>2026-10-04T20:02:56.317911+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf,fork: wipe -&gt;bpf_storage before bailouts that access it</p>
<p>Currently, copy_process() can bail out to free_task() before p-&gt;bpf_storage
has been initialized, with this call graph (shown here for the
!CONFIG_MEMCG case):</p>
<p>copy_process
  dup_task_struct
    arch_dup_task_struct
      [copies the entire task_struct, including -&gt;bpf_storage member]
  [RLIMIT_NPROC check fails]
  delayed_free_task
    free_task
      bpf_task_storage_free
        rcu_dereference(task-&gt;bpf_storage)
        bpf_local_storage_destroy</p>
<p>In this case, the nascent task's -&gt;bpf_storage member that
bpf_local_storage_destroy() operates on is a plain copy of the parent's
-&gt;bpf_storage pointer, not a real initialized pointer.
This leads to badness (kernel hangs, UAF).</p>
<p>This is reachable as long as the process calling fork() has been inserted
into a task storage map.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-72110"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9wff-g7fh-998r</id>
    <title>GHSA-9wff-g7fh-998r</title>
    <updated>2026-10-04T20:02:56.317946+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf,fork: wipe -&gt;bpf_storage before bailouts that access it</p>
<p>Currently, copy_process() can bail out to free_task() before p-&gt;bpf_storage
has been initialized, with this call graph (shown here for the
!CONFIG_MEMCG case):</p>
<p>copy_process
  dup_task_struct
    arch_dup_task_struct
      [copies the entire task_struct, including -&gt;bpf_storage member]
  [RLIMIT_NPROC check fails]
  delayed_free_task
    free_task
      bpf_task_storage_free
        rcu_dereference(task-&gt;bpf_storage)
        bpf_local_storage_destroy</p>
<p>In this case, the nascent task's -&gt;bpf_storage member that
bpf_local_storage_destroy() operates on is a plain copy of the parent's
-&gt;bpf_storage pointer, not a real initialized pointer.
This leads to badness (kernel hangs, UAF).</p>
<p>This is reachable as long as the process calling fork() has been inserted
into a task storage map.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9wff-g7fh-998r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-3704</id>
    <title>OESA-2026-3704 — kernel security update</title>
    <updated>2026-10-04T20:02:56.317971+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: hns3: add VLAN id validation before using</p>
<p>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.</p>
<p>Therefore, VLAN id needs to be checked to ensure it is within
the range of VLAN_N_VID.(CVE-2025-71112)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: fix string copying in parse_apply_sb_mount_options()</p>
<p>strscpy_pad() can&amp;apos;t be used to copy a non-NUL-term string into a NUL-term
string of possibly bigger size.  Commit 0efc5990bca5 (&amp;quot;string.h: Introduce
memtostr() and memtostr_pad()&amp;quot;) provides additional information in that
regard.  So if this happens, the following warning is observed:</p>
<p>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;lt;TASK&amp;gt;
 __fortify_panic+0x1f/0x30 lib/s…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-3704"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72110</id>
    <title>UBUNTU-CVE-2026-72110</title>
    <updated>2026-10-04T20:02:56.318818+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe -&gt;bpf_storage before bailouts that access it Currently, copy_process() can bail out to free_task() before p-&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 -&gt;bpf_storage member]   [RLIMIT_NPROC check fails]   delayed_free_task     free_task       bpf_task_storage_free         rcu_dereference(task-&gt;bpf_storage)         bpf_local_storage_destroy In this case, the nascent task's -&gt;bpf_storage member that bpf_local_storage_destroy() operates on is a plain copy of the parent's -&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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72110"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</id>
    <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T20:02:56.319080+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852"/>
  </entry>
</feed>
