<?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-29T02:32:57.111067+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-89962</id>
    <title>CVE-2026-89962 — powerpc/kexec_file: Prevent kexec range truncation</title>
    <updated>2026-09-29T02:32:57.128517+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>powerpc/kexec_file: Prevent kexec range truncation</p>
<p>Sashiko AI review pointed out the following issue.</p>
<p>The __merge_memory_ranges() function incorrectly handles overlapping
memory ranges when merging them. Although sort_memory_ranges() sorts all
ranges by their start address in ascending order beforehand, the merge
logic remains defective in two ways:</p>
<p>1. It compares the current range's start against the previous element (i-1)
   instead of the running target index (idx)</p>
<p>2. It unconditionally overwrites 'ranges[idx].end' with 'ranges[i].end'.</p>
<p>This logic flaw leads to critical memory truncation when a larger memory
range completely subsumes subsequent smaller ranges.</p>
<p>For example, consider a sorted input array with three ranges:
  Range A (idx=0): [0x1000 - 0x9000]
  Range B (i=1):   [0x2000 - 0x5000] (completely inside Range A)
  Range C (i=2):   [0x6000 - 0x8000] (completely inside Range A)</p>
<p>1. When i=1 (Range B):
   ranges[1].start (0x2000) &lt;= ranges[0].end + 1 (0x9001) is TRUE.
   The code executes: ranges[0].end = ranges[1].end, which erroneously
   shrinks Range A's end from 0x9000 down to 0x5000.</p>
<p>2. When i=2 (Range C):
   ranges[2].start (0x6000) &lt;= ranges[1].end + 1 (0x5001) is FALSE.
   The code falls into the else block, creating a broken new range.</p>
<p>As a result, valid memory fragments [0x5001 - 0x5fff] and [0x8001 - 0x9000]
are completely lost from the kexec exclude lists, potentially allowing…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89962"/>
  </entry>
</feed>
