<?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://db.gcve.eu</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>Sat, 24 Oct 2026 22:29:09 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99004</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99004</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/imagination: Size page table preallocation by device address&lt;/p&gt;
&lt;p&gt;Commit 0a8224058a58 (&amp;#34;drm/imagination: Fix page count for page table for
map() interface&amp;#34;) passed the device address to
pvr_mmu_op_context_create(), but the preallocation is still sized from
device_addr + sgt_offset with an exclusive end. The offset into the
object&amp;#39;s pages has no place in a device-virtual range, and the exclusive
end allocates one table too many when the range ends on a table
boundary.&lt;/p&gt;
&lt;p&gt;Count the tables from device_addr and the inclusive end of the range.&lt;/p&gt;
&lt;p&gt;The new calculation does not take page table indices into account. This
fixes another issue with the previous implementation, where the
difference between start and end indices could underflow when a mapping
crossed a page table boundary. This would lead to the driver
preallocating a huge number of MMU pages, exhausting system memory and
triggering an out of memory panic.&lt;/p&gt;
&lt;p&gt;[Alessio: add paragraph to point out OOM bug being fixed, cc stable]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/imagination: Size page table preallocation by device address&lt;/p&gt;
&lt;p&gt;Commit 0a8224058a58 (&amp;#34;drm/imagination: Fix page count for page table for
map() interface&amp;#34;) passed the device address to
pvr_mmu_op_context_create(), but the preallocation is still sized from
device_addr + sgt_offset with an exclusive end. The offset into the
object&amp;#39;s pages has no place in a device-virtual range, and the exclusive
end allocates one table too many when the range ends on a table
boundary.&lt;/p&gt;
&lt;p&gt;Count the tables from device_addr and the inclusive end of the range.&lt;/p&gt;
&lt;p&gt;The new calculation does not take page table indices into account. This
fixes another issue with the previous implementation, where the
difference between start and end indices could underflow when a mapping
crossed a page table boundary. This would lead to the driver
preallocating a huge number of MMU pages, exhausting system memory and
triggering an out of memory panic.&lt;/p&gt;
&lt;p&gt;[Alessio: add paragraph to point out OOM bug being fixed, cc stable]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99004</guid>
    </item>
    <item>
      <title>GHSA-862j-6x74-2p6m</title>
      <link>https://db.gcve.eu/vuln/ghsa-862j-6x74-2p6m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/imagination: Size page table preallocation by device address&lt;/p&gt;
&lt;p&gt;Commit 0a8224058a58 (&amp;#34;drm/imagination: Fix page count for page table for
map() interface&amp;#34;) passed the device address to
pvr_mmu_op_context_create(), but the preallocation is still sized from
device_addr + sgt_offset with an exclusive end. The offset into the
object&amp;#39;s pages has no place in a device-virtual range, and the exclusive
end allocates one table too many when the range ends on a table
boundary.&lt;/p&gt;
&lt;p&gt;Count the tables from device_addr and the inclusive end of the range.&lt;/p&gt;
&lt;p&gt;The new calculation does not take page table indices into account. This
fixes another issue with the previous implementation, where the
difference between start and end indices could underflow when a mapping
crossed a page table boundary. This would lead to the driver
preallocating a huge number of MMU pages, exhausting system memory and
triggering an out of memory panic.&lt;/p&gt;
&lt;p&gt;[Alessio: add paragraph to point out OOM bug being fixed, cc stable]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/imagination: Size page table preallocation by device address&lt;/p&gt;
&lt;p&gt;Commit 0a8224058a58 (&amp;#34;drm/imagination: Fix page count for page table for
map() interface&amp;#34;) passed the device address to
pvr_mmu_op_context_create(), but the preallocation is still sized from
device_addr + sgt_offset with an exclusive end. The offset into the
object&amp;#39;s pages has no place in a device-virtual range, and the exclusive
end allocates one table too many when the range ends on a table
boundary.&lt;/p&gt;
&lt;p&gt;Count the tables from device_addr and the inclusive end of the range.&lt;/p&gt;
&lt;p&gt;The new calculation does not take page table indices into account. This
fixes another issue with the previous implementation, where the
difference between start and end indices could underflow when a mapping
crossed a page table boundary. This would lead to the driver
preallocating a huge number of MMU pages, exhausting system memory and
triggering an out of memory panic.&lt;/p&gt;
&lt;p&gt;[Alessio: add paragraph to point out OOM bug being fixed, cc stable]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-862j-6x74-2p6m</guid>
    </item>
  </channel>
</rss>
