<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 01:36:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50075 — tracing/eprobes: Have event probes be consistent with kprobes and uprobes</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50075</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2022-50075</guid>
    </item>
  </channel>
</rss>
