<?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>Thu, 29 Oct 2026 17:23:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99097 — tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99097</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;tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()&lt;/p&gt;
&lt;p&gt;tee_dyn_shm_alloc_helper() derives nr_pages from a caller-supplied size
and passes it to alloc_pages_exact() without checking it. For size == 0
nr_pages is 0, and alloc_pages_exact(0) calls get_order(0), which is
documented as undefined and returns BITS_PER_LONG - PAGE_SHIFT. The page
allocator then trips its order &amp;gt; MAX_PAGE_ORDER warning and fails the
allocation; on a panic_on_warn kernel that ends the boot.&lt;/p&gt;
&lt;p&gt;This can be triggered by TEE_IOC_SHM_ALLOC with struct
tee_ioctl_shm_alloc_data where size is 0.&lt;/p&gt;
&lt;p&gt;Reject a zero page count, as register_shm_helper() already does for the
register path.&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;tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()&lt;/p&gt;
&lt;p&gt;tee_dyn_shm_alloc_helper() derives nr_pages from a caller-supplied size
and passes it to alloc_pages_exact() without checking it. For size == 0
nr_pages is 0, and alloc_pages_exact(0) calls get_order(0), which is
documented as undefined and returns BITS_PER_LONG - PAGE_SHIFT. The page
allocator then trips its order &amp;gt; MAX_PAGE_ORDER warning and fails the
allocation; on a panic_on_warn kernel that ends the boot.&lt;/p&gt;
&lt;p&gt;This can be triggered by TEE_IOC_SHM_ALLOC with struct
tee_ioctl_shm_alloc_data where size is 0.&lt;/p&gt;
&lt;p&gt;Reject a zero page count, as register_shm_helper() already does for the
register path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99097</guid>
    </item>
  </channel>
</rss>
