<?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>Sun, 04 Oct 2026 18:54:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38636 — rv: Use strings in da monitors tracepoints</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38636</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;rv: Use strings in da monitors tracepoints&lt;/p&gt;
&lt;p&gt;Using DA monitors tracepoints with KASAN enabled triggers the following
warning:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
 Read of size 32 at addr ffffffffaada8980 by task ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
 [...]
  do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
  ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10
  ? trace_event_sncid+0x83/0x200
  trace_event_sncid+0x163/0x200
 [...]
 The buggy address belongs to the variable:
  automaton_snep+0x4e0/0x5e0&lt;/p&gt;
&lt;p&gt;This is caused by the tracepoints reading 32 bytes __array instead of
__string from the automata definition. Such strings are literals and
reading 32 bytes ends up in out of bound memory accesses (e.g. the next
automaton&amp;#39;s data in this case).
The error is harmless as, while printing the string, we stop at the null
terminator, but it should still be fixed.&lt;/p&gt;
&lt;p&gt;Use the __string facilities while defining the tracepoints to avoid
reading out of bound memory.&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;rv: Use strings in da monitors tracepoints&lt;/p&gt;
&lt;p&gt;Using DA monitors tracepoints with KASAN enabled triggers the following
warning:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
 Read of size 32 at addr ffffffffaada8980 by task ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
 [...]
  do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0
  ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10
  ? trace_event_sncid+0x83/0x200
  trace_event_sncid+0x163/0x200
 [...]
 The buggy address belongs to the variable:
  automaton_snep+0x4e0/0x5e0&lt;/p&gt;
&lt;p&gt;This is caused by the tracepoints reading 32 bytes __array instead of
__string from the automata definition. Such strings are literals and
reading 32 bytes ends up in out of bound memory accesses (e.g. the next
automaton&amp;#39;s data in this case).
The error is harmless as, while printing the string, we stop at the null
terminator, but it should still be fixed.&lt;/p&gt;
&lt;p&gt;Use the __string facilities while defining the tracepoints to avoid
reading out of bound memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38636</guid>
    </item>
  </channel>
</rss>
