<?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 10:47:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53820 — loop: loop_set_status_from_info() check before assignment</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53820</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;loop: loop_set_status_from_info() check before assignment&lt;/p&gt;
&lt;p&gt;In loop_set_status_from_info(), lo-&amp;gt;lo_offset and lo-&amp;gt;lo_sizelimit should
be checked before reassignment, because if an overflow error occurs, the
original correct value will be changed to the wrong value, and it will not
be changed back.&lt;/p&gt;
&lt;p&gt;More, the original patch did not solve the problem, the value was set and
ioctl returned an error, but the subsequent io used the value in the loop
driver, which still caused an alarm:&lt;/p&gt;
&lt;p&gt;loop_handle_cmd
 do_req_filebacked
  loff_t pos = ((loff_t) blk_rq_pos(rq) &amp;lt;&amp;lt; 9) + lo-&amp;gt;lo_offset;
  lo_rw_aio
   cmd-&amp;gt;iocb.ki_pos = pos&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;loop: loop_set_status_from_info() check before assignment&lt;/p&gt;
&lt;p&gt;In loop_set_status_from_info(), lo-&amp;gt;lo_offset and lo-&amp;gt;lo_sizelimit should
be checked before reassignment, because if an overflow error occurs, the
original correct value will be changed to the wrong value, and it will not
be changed back.&lt;/p&gt;
&lt;p&gt;More, the original patch did not solve the problem, the value was set and
ioctl returned an error, but the subsequent io used the value in the loop
driver, which still caused an alarm:&lt;/p&gt;
&lt;p&gt;loop_handle_cmd
 do_req_filebacked
  loff_t pos = ((loff_t) blk_rq_pos(rq) &amp;lt;&amp;lt; 9) + lo-&amp;gt;lo_offset;
  lo_rw_aio
   cmd-&amp;gt;iocb.ki_pos = pos&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53820</guid>
    </item>
  </channel>
</rss>
