<?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-04T03:18:42.866227+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/bdu:2026-03971</id>
    <title>bdu:2026-03971</title>
    <updated>2026-10-04T03:18:42.939865+00:00</updated>
    <content>bdu:2026-03971</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-03971"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529</id>
    <title>certfr-2025-avi-0529 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-10-04T03:18:42.939912+00:00</updated>
    <content>certfr-2025-avi-0529</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-344326</id>
    <title>EUVD-2026-344326</title>
    <updated>2026-10-04T03:18:42.939932+00:00</updated>
    <content>EUVD-2026-344326</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-344326"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-36791</id>
    <title>fkie_cve-2020-36791</title>
    <updated>2026-10-04T03:18:42.939944+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>net_sched: keep alloc_hash updated after hash allocation</p>
<p>In commit 599be01ee567 ("net_sched: fix an OOB access in cls_tcindex")
I moved cp-&gt;hash calculation before the first
tcindex_alloc_perfect_hash(), but cp-&gt;alloc_hash is left untouched.
This difference could lead to another out of bound access.</p>
<p>cp-&gt;alloc_hash should always be the size allocated, we should
update it after this tcindex_alloc_perfect_hash().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-36791"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5pxm-fr3g-jf32</id>
    <title>GHSA-5pxm-fr3g-jf32</title>
    <updated>2026-10-04T03:18:42.939978+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>net_sched: keep alloc_hash updated after hash allocation</p>
<p>In commit 599be01ee567 ("net_sched: fix an OOB access in cls_tcindex")
I moved cp-&gt;hash calculation before the first
tcindex_alloc_perfect_hash(), but cp-&gt;alloc_hash is left untouched.
This difference could lead to another out of bound access.</p>
<p>cp-&gt;alloc_hash should always be the size allocated, we should
update it after this tcindex_alloc_perfect_hash().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5pxm-fr3g-jf32"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-36791</id>
    <title>gsd-2020-36791</title>
    <updated>2026-10-04T03:18:42.939998+00:00</updated>
    <content>gsd-2020-36791</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-36791"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:01982-1</id>
    <title>SUSE-SU-2025:01982-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T03:18:42.940009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2025:01982-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-36791</id>
    <title>UBUNTU-CVE-2020-36791</title>
    <updated>2026-10-04T03:18:42.940067+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:16.04:LTS: linux, Ubuntu:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-aws-hwe, Ubuntu:16.04:LTS: linux-azure, Ubuntu:16.04:LTS: linux-gcp, Ubuntu:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-kvm and 87 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net_sched: keep alloc_hash updated after hash allocation In commit 599be01ee567 ("net_sched: fix an OOB access in cls_tcindex") I moved cp-&gt;hash calculation before the first tcindex_alloc_perfect_hash(), but cp-&gt;alloc_hash is left untouched. This difference could lead to another out of bound access. cp-&gt;alloc_hash should always be the size allocated, we should update it after this tcindex_alloc_perfect_hash().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-36791"/>
  </entry>
</feed>
