<?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-29T14:36:48.686983+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-89568</id>
    <title>CVE-2026-89568 — kho: fix size calculation in kho_preserved_memory_reserve()</title>
    <updated>2026-09-29T14:36:48.706380+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>kho: fix size calculation in kho_preserved_memory_reserve()</p>
<p>kho_preserved_memory_reserve() calculates the size of a preservation by
doing 1 &lt;&lt; (order + PAGE_SHIFT). Since the '1' is a 32-bit integer, it
can only be shifted by 31. That is, it will only work for preservations
up to 2 GiB. Larger preservations will trigger undefined behaviour.</p>
<p>While preservations larger than 2 GiB can't be obtained via folios
currently, they can be obtained via kho_preserve_pages().</p>
<p>For example, memblock reserve_mem uses kho_preserve_pages().
Reservations larger than 2 GiB are valid and will trigger this bug if
properly aligned.</p>
<p>Fix it by using 1UL for shifting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89568"/>
  </entry>
</feed>
