<?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 03:54:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53622 — gfs2: Fix possible data races in gfs2_show_options()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53622</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;gfs2: Fix possible data races in gfs2_show_options()&lt;/p&gt;
&lt;p&gt;Some fields such as gt_logd_secs of the struct gfs2_tune are accessed
without holding the lock gt_spin in gfs2_show_options():&lt;/p&gt;
&lt;p&gt;val = sdp-&amp;gt;sd_tune.gt_logd_secs;
  if (val != 30)
    seq_printf(s, &amp;#34;,commit=%d&amp;#34;, val);&lt;/p&gt;
&lt;p&gt;And thus can cause data races when gfs2_show_options() and other functions
such as gfs2_reconfigure() are concurrently executed:&lt;/p&gt;
&lt;p&gt;spin_lock(&amp;amp;gt-&amp;gt;gt_spin);
  gt-&amp;gt;gt_logd_secs = newargs-&amp;gt;ar_commit;&lt;/p&gt;
&lt;p&gt;To fix these possible data races, the lock sdp-&amp;gt;sd_tune.gt_spin is
acquired before accessing the fields of gfs2_tune and released after these
accesses.&lt;/p&gt;
&lt;p&gt;Further changes by Andreas:&lt;/p&gt;
&lt;p&gt;- Don&amp;#39;t hold the spin lock over the seq_printf operations.&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;gfs2: Fix possible data races in gfs2_show_options()&lt;/p&gt;
&lt;p&gt;Some fields such as gt_logd_secs of the struct gfs2_tune are accessed
without holding the lock gt_spin in gfs2_show_options():&lt;/p&gt;
&lt;p&gt;val = sdp-&amp;gt;sd_tune.gt_logd_secs;
  if (val != 30)
    seq_printf(s, &amp;#34;,commit=%d&amp;#34;, val);&lt;/p&gt;
&lt;p&gt;And thus can cause data races when gfs2_show_options() and other functions
such as gfs2_reconfigure() are concurrently executed:&lt;/p&gt;
&lt;p&gt;spin_lock(&amp;amp;gt-&amp;gt;gt_spin);
  gt-&amp;gt;gt_logd_secs = newargs-&amp;gt;ar_commit;&lt;/p&gt;
&lt;p&gt;To fix these possible data races, the lock sdp-&amp;gt;sd_tune.gt_spin is
acquired before accessing the fields of gfs2_tune and released after these
accesses.&lt;/p&gt;
&lt;p&gt;Further changes by Andreas:&lt;/p&gt;
&lt;p&gt;- Don&amp;#39;t hold the spin lock over the seq_printf operations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53622</guid>
    </item>
  </channel>
</rss>
