<?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>Sat, 03 Oct 2026 19:09:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03398</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03398</link>
      <description>bdu:2026-03398</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03398</guid>
    </item>
    <item>
      <title>EUVD-2026-310997</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310997</link>
      <description>EUVD-2026-310997</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310997</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50075</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50075</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing/eprobes: Have event probes be consistent with kprobes and uprobes&lt;/p&gt;
&lt;p&gt;Currently, if a symbol &amp;#34;@&amp;#34; is attempted to be used with an event probe
(eprobes), it will cause a NULL pointer dereference crash.&lt;/p&gt;
&lt;p&gt;Both kprobes and uprobes can reference data other than the main registers.
Such as immediate address, symbols and the current task name. Have eprobes
do the same thing.&lt;/p&gt;
&lt;p&gt;For &amp;#34;comm&amp;#34;, if &amp;#34;comm&amp;#34; is used and the event being attached to does not
have the &amp;#34;comm&amp;#34; field, then make it the &amp;#34;$comm&amp;#34; that kprobes has. This is
consistent to the way histograms and filters work.&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;tracing/eprobes: Have event probes be consistent with kprobes and uprobes&lt;/p&gt;
&lt;p&gt;Currently, if a symbol &amp;#34;@&amp;#34; is attempted to be used with an event probe
(eprobes), it will cause a NULL pointer dereference crash.&lt;/p&gt;
&lt;p&gt;Both kprobes and uprobes can reference data other than the main registers.
Such as immediate address, symbols and the current task name. Have eprobes
do the same thing.&lt;/p&gt;
&lt;p&gt;For &amp;#34;comm&amp;#34;, if &amp;#34;comm&amp;#34; is used and the event being attached to does not
have the &amp;#34;comm&amp;#34; field, then make it the &amp;#34;$comm&amp;#34; that kprobes has. This is
consistent to the way histograms and filters work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50075</guid>
    </item>
    <item>
      <title>GHSA-xpmp-pq5g-mgh6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xpmp-pq5g-mgh6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing/eprobes: Have event probes be consistent with kprobes and uprobes&lt;/p&gt;
&lt;p&gt;Currently, if a symbol &amp;#34;@&amp;#34; is attempted to be used with an event probe
(eprobes), it will cause a NULL pointer dereference crash.&lt;/p&gt;
&lt;p&gt;Both kprobes and uprobes can reference data other than the main registers.
Such as immediate address, symbols and the current task name. Have eprobes
do the same thing.&lt;/p&gt;
&lt;p&gt;For &amp;#34;comm&amp;#34;, if &amp;#34;comm&amp;#34; is used and the event being attached to does not
have the &amp;#34;comm&amp;#34; field, then make it the &amp;#34;$comm&amp;#34; that kprobes has. This is
consistent to the way histograms and filters work.&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;tracing/eprobes: Have event probes be consistent with kprobes and uprobes&lt;/p&gt;
&lt;p&gt;Currently, if a symbol &amp;#34;@&amp;#34; is attempted to be used with an event probe
(eprobes), it will cause a NULL pointer dereference crash.&lt;/p&gt;
&lt;p&gt;Both kprobes and uprobes can reference data other than the main registers.
Such as immediate address, symbols and the current task name. Have eprobes
do the same thing.&lt;/p&gt;
&lt;p&gt;For &amp;#34;comm&amp;#34;, if &amp;#34;comm&amp;#34; is used and the event being attached to does not
have the &amp;#34;comm&amp;#34; field, then make it the &amp;#34;$comm&amp;#34; that kprobes has. This is
consistent to the way histograms and filters work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xpmp-pq5g-mgh6</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50075</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50075</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 94 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent with kprobes and uprobes Currently, if a symbol &amp;#34;@&amp;#34; is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash. Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing. For &amp;#34;comm&amp;#34;, if &amp;#34;comm&amp;#34; is used and the event being attached to does not have the &amp;#34;comm&amp;#34; field, then make it the &amp;#34;$comm&amp;#34; that kprobes has. This is consistent to the way histograms and filters work.&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 94 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent with kprobes and uprobes Currently, if a symbol &amp;#34;@&amp;#34; is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash. Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing. For &amp;#34;comm&amp;#34;, if &amp;#34;comm&amp;#34; is used and the event being attached to does not have the &amp;#34;comm&amp;#34; field, then make it the &amp;#34;$comm&amp;#34; that kprobes has. This is consistent to the way histograms and filters work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50075</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
