<?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://cve.radiocsirt.org</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, 17 Nov 2026 10:33:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99004</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99004</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99004</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1470 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1470</link>
      <description>certfr-2026-avi-1470</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1470</guid>
    </item>
    <item>
      <title>EUVD-2026-391556</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391556</link>
      <description>EUVD-2026-391556</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391556</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99004</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/fkie_cve-2026-99004</guid>
    </item>
    <item>
      <title>GHSA-862j-6x74-2p6m</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/ghsa-862j-6x74-2p6m</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99004 — drm/imagination: Size page table preallocation by device address</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99004</link>
      <description>msrc_CVE-2026-99004</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99004</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99004</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99004</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Size page table preallocation by device address 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. Count the tables from device_addr and the inclusive end of the range. 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. [Alessio: add paragraph to point out OOM bug being fixed, cc stable]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Size page table preallocation by device address 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. Count the tables from device_addr and the inclusive end of the range. 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. [Alessio: add paragraph to point out OOM bug being fixed, cc stable]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99004</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
