<?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 01:18:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80675</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80675</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80675</guid>
    </item>
    <item>
      <title>EUVD-2026-361565</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361565</link>
      <description>EUVD-2026-361565</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361565</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80675</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80675</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;libbpf: Reject non-exclusive metadata maps in the signed loader&lt;/p&gt;
&lt;p&gt;The loader verifies map-&amp;gt;sha against the metadata hash in its
instructions. map-&amp;gt;sha is calculated when BPF_OBJ_GET_INFO_BY_FD is
called on the frozen map.&lt;/p&gt;
&lt;p&gt;While the map is frozen, the /signed loader/ must also ensure the map
is exclusive, as, without exclusivity (which a hostile host could just
omit when loading the loader), another BPF program with map access can
mutate the contents afterwards, so the check passes on stale data.&lt;/p&gt;
&lt;p&gt;With the extra check as part of the signed loader, it now refuses to
move on with map-&amp;gt;sha validation if the host set it up wrongly.&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;libbpf: Reject non-exclusive metadata maps in the signed loader&lt;/p&gt;
&lt;p&gt;The loader verifies map-&amp;gt;sha against the metadata hash in its
instructions. map-&amp;gt;sha is calculated when BPF_OBJ_GET_INFO_BY_FD is
called on the frozen map.&lt;/p&gt;
&lt;p&gt;While the map is frozen, the /signed loader/ must also ensure the map
is exclusive, as, without exclusivity (which a hostile host could just
omit when loading the loader), another BPF program with map access can
mutate the contents afterwards, so the check passes on stale data.&lt;/p&gt;
&lt;p&gt;With the extra check as part of the signed loader, it now refuses to
move on with map-&amp;gt;sha validation if the host set it up wrongly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80675</guid>
    </item>
    <item>
      <title>GHSA-82gv-94cv-gr24</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-82gv-94cv-gr24</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;libbpf: Reject non-exclusive metadata maps in the signed loader&lt;/p&gt;
&lt;p&gt;The loader verifies map-&amp;gt;sha against the metadata hash in its
instructions. map-&amp;gt;sha is calculated when BPF_OBJ_GET_INFO_BY_FD is
called on the frozen map.&lt;/p&gt;
&lt;p&gt;While the map is frozen, the /signed loader/ must also ensure the map
is exclusive, as, without exclusivity (which a hostile host could just
omit when loading the loader), another BPF program with map access can
mutate the contents afterwards, so the check passes on stale data.&lt;/p&gt;
&lt;p&gt;With the extra check as part of the signed loader, it now refuses to
move on with map-&amp;gt;sha validation if the host set it up wrongly.&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;libbpf: Reject non-exclusive metadata maps in the signed loader&lt;/p&gt;
&lt;p&gt;The loader verifies map-&amp;gt;sha against the metadata hash in its
instructions. map-&amp;gt;sha is calculated when BPF_OBJ_GET_INFO_BY_FD is
called on the frozen map.&lt;/p&gt;
&lt;p&gt;While the map is frozen, the /signed loader/ must also ensure the map
is exclusive, as, without exclusivity (which a hostile host could just
omit when loading the loader), another BPF program with map access can
mutate the contents afterwards, so the check passes on stale data.&lt;/p&gt;
&lt;p&gt;With the extra check as part of the signed loader, it now refuses to
move on with map-&amp;gt;sha validation if the host set it up wrongly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-82gv-94cv-gr24</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80675</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80675</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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata maps in the signed loader The loader verifies map-&amp;gt;sha against the metadata hash in its instructions. map-&amp;gt;sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now refuses to move on with map-&amp;gt;sha validation if the host set it up wrongly.&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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata maps in the signed loader The loader verifies map-&amp;gt;sha against the metadata hash in its instructions. map-&amp;gt;sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now refuses to move on with map-&amp;gt;sha validation if the host set it up wrongly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80675</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
