<?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://db.gcve.eu</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>Wed, 30 Sep 2026 21:59:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53709 — ring-buffer: Handle race between rb_move_tail and rb_check_pages</title>
      <link>https://db.gcve.eu/vuln/cve-2023-53709</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;ring-buffer: Handle race between rb_move_tail and rb_check_pages&lt;/p&gt;
&lt;p&gt;It seems a data race between ring_buffer writing and integrity check.
That is, RB_FLAG of head_page is been updating, while at same time
RB_FLAG was cleared when doing integrity check rb_check_pages():&lt;/p&gt;
&lt;p&gt;rb_check_pages()            rb_handle_head_page():
  --------                    --------
  rb_head_page_deactivate()
                              rb_head_page_set_normal()
  rb_head_page_activate()&lt;/p&gt;
&lt;p&gt;We do intergrity test of the list to check if the list is corrupted and
it is still worth doing it. So, let&amp;#39;s refactor rb_check_pages() such that
we no longer clear and set flag during the list sanity checking.&lt;/p&gt;
&lt;p&gt;[1] and [2] are the test to reproduce and the crash report respectively.&lt;/p&gt;
&lt;p&gt;1:
``` read_trace.sh
  while true;
  do
    # the &amp;#34;trace&amp;#34; file is closed after read
    head -1 /sys/kernel/tracing/trace &amp;gt; /dev/null
  done
```
``` repro.sh
  sysctl -w kernel.panic_on_warn=1
  # function tracer will writing enough data into ring_buffer
  echo function &amp;gt; /sys/kernel/tracing/current_tracer
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
```&lt;/p&gt;
&lt;p&gt;2:
------------[ cut here ]------------
WARNING: CPU: 9 PID: 62 at kernel/trace/ring_buffer.c:2653
rb_move_tail+0x450/0x470
Modules linked in:
CPU: 9 PID: 62 Comm: ksoftirqd/9 Tainted: G        W…&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;ring-buffer: Handle race between rb_move_tail and rb_check_pages&lt;/p&gt;
&lt;p&gt;It seems a data race between ring_buffer writing and integrity check.
That is, RB_FLAG of head_page is been updating, while at same time
RB_FLAG was cleared when doing integrity check rb_check_pages():&lt;/p&gt;
&lt;p&gt;rb_check_pages()            rb_handle_head_page():
  --------                    --------
  rb_head_page_deactivate()
                              rb_head_page_set_normal()
  rb_head_page_activate()&lt;/p&gt;
&lt;p&gt;We do intergrity test of the list to check if the list is corrupted and
it is still worth doing it. So, let&amp;#39;s refactor rb_check_pages() such that
we no longer clear and set flag during the list sanity checking.&lt;/p&gt;
&lt;p&gt;[1] and [2] are the test to reproduce and the crash report respectively.&lt;/p&gt;
&lt;p&gt;1:
``` read_trace.sh
  while true;
  do
    # the &amp;#34;trace&amp;#34; file is closed after read
    head -1 /sys/kernel/tracing/trace &amp;gt; /dev/null
  done
```
``` repro.sh
  sysctl -w kernel.panic_on_warn=1
  # function tracer will writing enough data into ring_buffer
  echo function &amp;gt; /sys/kernel/tracing/current_tracer
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
  ./read_trace.sh &amp;amp;
```&lt;/p&gt;
&lt;p&gt;2:
------------[ cut here ]------------
WARNING: CPU: 9 PID: 62 at kernel/trace/ring_buffer.c:2653
rb_move_tail+0x450/0x470
Modules linked in:
CPU: 9 PID: 62 Comm: ksoftirqd/9 Tainted: G        W…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-53709</guid>
    </item>
  </channel>
</rss>
