<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T21:29:59.653011+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-89926</id>
    <title>CVE-2026-89926 — KVM: s390: Fix length check __import_wp_info()</title>
    <updated>2026-09-29T21:29:59.655101+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>KVM: s390: Fix length check __import_wp_info()</p>
<p>struct kvm_hw_breakpoint::len is a __u64 that is fully controlled by user
space. This is then assigned to wp_info-&gt;len, which is an int. The bounds
check is done on the truncated value while the allocation uses the
untruncated one:</p>
<p>wp_info-&gt;len = bp_data-&gt;len;
	[...]
	if (wp_info-&gt;len &lt; 0 || wp_info-&gt;len &gt; MAX_WP_SIZE)
		return -EINVAL;</p>
<p>wp_info-&gt;old_data = kmalloc(bp_data-&gt;len, GFP_KERNEL_ACCOUNT);</p>
<p>Use the validated value for the allocation as intended. Without this
fix userspace can trigger &gt;4GB allocations which will fail and result
in a WARN due to MAX_PAGE_ORDER.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89926"/>
  </entry>
</feed>
