<?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 23:53:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89926 — KVM: s390: Fix length check __import_wp_info()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89926</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: s390: Fix length check __import_wp_info()&lt;/p&gt;
&lt;p&gt;struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user
space. This is then assigned to wp_info-&amp;gt;len, which is an int. The bounds
check is done on the truncated value while the allocation uses the
untruncated one:&lt;/p&gt;
&lt;p&gt;wp_info-&amp;gt;len = bp_data-&amp;gt;len;
	[...]
	if (wp_info-&amp;gt;len &amp;lt; 0 || wp_info-&amp;gt;len &amp;gt; MAX_WP_SIZE)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;wp_info-&amp;gt;old_data = kmalloc(bp_data-&amp;gt;len, GFP_KERNEL_ACCOUNT);&lt;/p&gt;
&lt;p&gt;Use the validated value for the allocation as intended. Without this
fix userspace can trigger &amp;gt;4GB allocations which will fail and result
in a WARN due to MAX_PAGE_ORDER.&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: s390: Fix length check __import_wp_info()&lt;/p&gt;
&lt;p&gt;struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user
space. This is then assigned to wp_info-&amp;gt;len, which is an int. The bounds
check is done on the truncated value while the allocation uses the
untruncated one:&lt;/p&gt;
&lt;p&gt;wp_info-&amp;gt;len = bp_data-&amp;gt;len;
	[...]
	if (wp_info-&amp;gt;len &amp;lt; 0 || wp_info-&amp;gt;len &amp;gt; MAX_WP_SIZE)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;wp_info-&amp;gt;old_data = kmalloc(bp_data-&amp;gt;len, GFP_KERNEL_ACCOUNT);&lt;/p&gt;
&lt;p&gt;Use the validated value for the allocation as intended. Without this
fix userspace can trigger &amp;gt;4GB allocations which will fail and result
in a WARN due to MAX_PAGE_ORDER.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89926</guid>
    </item>
  </channel>
</rss>
