<?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>Thu, 01 Oct 2026 15:15:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31590 — KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31590</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;KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION&lt;/p&gt;
&lt;p&gt;Drop the WARN in sev_pin_memory() on npages overflowing an int, as the
WARN is comically trivially to trigger from userspace, e.g. by doing:&lt;/p&gt;
&lt;p&gt;struct kvm_enc_region range = {
          .addr = 0,
          .size = -1ul,
  };&lt;/p&gt;
&lt;p&gt;__vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, &amp;amp;range);&lt;/p&gt;
&lt;p&gt;Note, the checks in sev_mem_enc_register_region() that presumably exist to
verify the incoming address+size are completely worthless, as both &amp;#34;addr&amp;#34;
and &amp;#34;size&amp;#34; are u64s and SEV is 64-bit only, i.e. they _can&amp;#39;t_ be greater
than ULONG_MAX.  That wart will be cleaned up in the near future.&lt;/p&gt;
&lt;p&gt;if (range-&amp;gt;addr &amp;gt; ULONG_MAX || range-&amp;gt;size &amp;gt; ULONG_MAX)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;Opportunistically add a comment to explain why the code calculates the
number of pages the &amp;#34;hard&amp;#34; way, e.g. instead of just shifting @ulen.&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;KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION&lt;/p&gt;
&lt;p&gt;Drop the WARN in sev_pin_memory() on npages overflowing an int, as the
WARN is comically trivially to trigger from userspace, e.g. by doing:&lt;/p&gt;
&lt;p&gt;struct kvm_enc_region range = {
          .addr = 0,
          .size = -1ul,
  };&lt;/p&gt;
&lt;p&gt;__vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, &amp;amp;range);&lt;/p&gt;
&lt;p&gt;Note, the checks in sev_mem_enc_register_region() that presumably exist to
verify the incoming address+size are completely worthless, as both &amp;#34;addr&amp;#34;
and &amp;#34;size&amp;#34; are u64s and SEV is 64-bit only, i.e. they _can&amp;#39;t_ be greater
than ULONG_MAX.  That wart will be cleaned up in the near future.&lt;/p&gt;
&lt;p&gt;if (range-&amp;gt;addr &amp;gt; ULONG_MAX || range-&amp;gt;size &amp;gt; ULONG_MAX)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;Opportunistically add a comment to explain why the code calculates the
number of pages the &amp;#34;hard&amp;#34; way, e.g. instead of just shifting @ulen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31590</guid>
    </item>
  </channel>
</rss>
