<?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 23:25:52 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-94202</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-94202</link>
      <description>&lt;p&gt;The Module Manager&amp;#39;s block-pool create dispatcher proved that two `ALIGN_TYPE` words of the extra-parameter array a memory-protected module supplies lay inside the module&amp;#39;s data, and then used indices 0 through 3 of that array.&lt;/p&gt;
&lt;p&gt;One of the two unproved words is read by the dispatcher&amp;#39;s own buffer check, which takes index 1 as the pool start and index 2 as the length to range-check it over. So the out-of-bounds read is performed by the validation code itself, before the kernel service is reached, and the size the caller&amp;#39;s pool start is then validated against is a word the manager has not proved the module owns. The other unproved word is read when the service&amp;#39;s argument list is built.&lt;/p&gt;
&lt;p&gt;Vulnerable function: `_txm_module_manager_tx_block_pool_create_dispatch`, in `common_modules/module_manager/inc/txm_module_manager_dispatch.h`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Module Manager&amp;#39;s block-pool create dispatcher proved that two `ALIGN_TYPE` words of the extra-parameter array a memory-protected module supplies lay inside the module&amp;#39;s data, and then used indices 0 through 3 of that array.&lt;/p&gt;
&lt;p&gt;One of the two unproved words is read by the dispatcher&amp;#39;s own buffer check, which takes index 1 as the pool start and index 2 as the length to range-check it over. So the out-of-bounds read is performed by the validation code itself, before the kernel service is reached, and the size the caller&amp;#39;s pool start is then validated against is a word the manager has not proved the module owns. The other unproved word is read when the service&amp;#39;s argument list is built.&lt;/p&gt;
&lt;p&gt;Vulnerable function: `_txm_module_manager_tx_block_pool_create_dispatch`, in `common_modules/module_manager/inc/txm_module_manager_dispatch.h`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-94202</guid>
    </item>
  </channel>
</rss>
