<?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>Tue, 29 Sep 2026 16:08:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53171 — vfio/type1: prevent underflow of locked_vm via exec()</title>
      <link>https://db.gcve.eu/vuln/cve-2023-53171</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;vfio/type1: prevent underflow of locked_vm via exec()&lt;/p&gt;
&lt;p&gt;When a vfio container is preserved across exec, the task does not change,
but it gets a new mm with locked_vm=0, and loses the count from existing
dma mappings.  If the user later unmaps a dma mapping, locked_vm underflows
to a large unsigned value, and a subsequent dma map request fails with
ENOMEM in __account_locked_vm.&lt;/p&gt;
&lt;p&gt;To avoid underflow, grab and save the mm at the time a dma is mapped.
Use that mm when adjusting locked_vm, rather than re-acquiring the saved
task&amp;#39;s mm, which may have changed.  If the saved mm is dead, do nothing.&lt;/p&gt;
&lt;p&gt;locked_vm is incremented for existing mappings in a subsequent patch.&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;vfio/type1: prevent underflow of locked_vm via exec()&lt;/p&gt;
&lt;p&gt;When a vfio container is preserved across exec, the task does not change,
but it gets a new mm with locked_vm=0, and loses the count from existing
dma mappings.  If the user later unmaps a dma mapping, locked_vm underflows
to a large unsigned value, and a subsequent dma map request fails with
ENOMEM in __account_locked_vm.&lt;/p&gt;
&lt;p&gt;To avoid underflow, grab and save the mm at the time a dma is mapped.
Use that mm when adjusting locked_vm, rather than re-acquiring the saved
task&amp;#39;s mm, which may have changed.  If the saved mm is dead, do nothing.&lt;/p&gt;
&lt;p&gt;locked_vm is incremented for existing mappings in a subsequent patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-53171</guid>
    </item>
  </channel>
</rss>
