<?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 02:49:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21804 — PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21804</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;PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()&lt;/p&gt;
&lt;p&gt;The rcar_pcie_parse_outbound_ranges() uses the devm_request_mem_region()
macro to request a needed resource. A string variable that lives on the
stack is then used to store a dynamically computed resource name, which
is then passed on as one of the macro arguments. This can lead to
undefined behavior.&lt;/p&gt;
&lt;p&gt;Depending on the current contents of the memory, the manifestations of
errors may vary. One possible output may be as follows:&lt;/p&gt;
&lt;p&gt;$ cat /proc/iomem
  30000000-37ffffff :
  38000000-3fffffff :&lt;/p&gt;
&lt;p&gt;Sometimes, garbage may appear after the colon.&lt;/p&gt;
&lt;p&gt;In very rare cases, if no NULL-terminator is found in memory, the system
might crash because the string iterator will overrun which can lead to
access of unmapped memory above the stack.&lt;/p&gt;
&lt;p&gt;Thus, fix this by replacing outbound_name with the name of the previously
requested resource. With the changes applied, the output will be as
follows:&lt;/p&gt;
&lt;p&gt;$ cat /proc/iomem
  30000000-37ffffff : memory2
  38000000-3fffffff : memory3&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log]&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;PCI: rcar-ep: Fix incorrect variable used when calling devm_request_mem_region()&lt;/p&gt;
&lt;p&gt;The rcar_pcie_parse_outbound_ranges() uses the devm_request_mem_region()
macro to request a needed resource. A string variable that lives on the
stack is then used to store a dynamically computed resource name, which
is then passed on as one of the macro arguments. This can lead to
undefined behavior.&lt;/p&gt;
&lt;p&gt;Depending on the current contents of the memory, the manifestations of
errors may vary. One possible output may be as follows:&lt;/p&gt;
&lt;p&gt;$ cat /proc/iomem
  30000000-37ffffff :
  38000000-3fffffff :&lt;/p&gt;
&lt;p&gt;Sometimes, garbage may appear after the colon.&lt;/p&gt;
&lt;p&gt;In very rare cases, if no NULL-terminator is found in memory, the system
might crash because the string iterator will overrun which can lead to
access of unmapped memory above the stack.&lt;/p&gt;
&lt;p&gt;Thus, fix this by replacing outbound_name with the name of the previously
requested resource. With the changes applied, the output will be as
follows:&lt;/p&gt;
&lt;p&gt;$ cat /proc/iomem
  30000000-37ffffff : memory2
  38000000-3fffffff : memory3&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21804</guid>
    </item>
  </channel>
</rss>
