<?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 18:05:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99024</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99024</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;optee: register TEE devices only once fully initialized&lt;/p&gt;
&lt;p&gt;optee_probe() called tee_device_register() on both the client and the
supplicant device before the rest of struct optee had been initialized.&lt;/p&gt;
&lt;p&gt;tee_device_register() calls cdev_device_add(), which does two things at
once: it creates /dev/tee0 and /dev/teepriv0, and it links the device
into the tee class so that class_find_device() can find it. From that
moment on the device is reachable both from user space via tee_open()
and from kernel space via tee_client_open_context(). The only gate in
teedev_open() is tee_device_get(), which merely checks that
teedev-&amp;gt;desc is non-NULL, which was already set by tee_device_alloc().
Therefore, there is effectively no gate at all.&lt;/p&gt;
&lt;p&gt;A context opened in that window can run against a struct optee where&lt;/p&gt;
&lt;p&gt;- optee-&amp;gt;call_queue.mutex is not initialized by optee_cq_init()
  - optee-&amp;gt;supp mutex and completions is not initialized by
    optee_supp_init()
  - optee-&amp;gt;rpmb_dev_mutex is not initialized yet,
  - the message argument cache is not initialized by
    optee_shm_arg_cache_init()
  - optee-&amp;gt;ctx is still NULL&lt;/p&gt;
&lt;p&gt;Any open session or invoke during this window takes uninitialized
mutexes and dereferences a NULL pointer.&lt;/p&gt;
&lt;p&gt;Fix it by moving both tee_device_register() calls down to the point
where all of struct optee is set up.&lt;/p&gt;
&lt;p&gt;[JW: adding fixes and cc]&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;optee: register TEE devices only once fully initialized&lt;/p&gt;
&lt;p&gt;optee_probe() called tee_device_register() on both the client and the
supplicant device before the rest of struct optee had been initialized.&lt;/p&gt;
&lt;p&gt;tee_device_register() calls cdev_device_add(), which does two things at
once: it creates /dev/tee0 and /dev/teepriv0, and it links the device
into the tee class so that class_find_device() can find it. From that
moment on the device is reachable both from user space via tee_open()
and from kernel space via tee_client_open_context(). The only gate in
teedev_open() is tee_device_get(), which merely checks that
teedev-&amp;gt;desc is non-NULL, which was already set by tee_device_alloc().
Therefore, there is effectively no gate at all.&lt;/p&gt;
&lt;p&gt;A context opened in that window can run against a struct optee where&lt;/p&gt;
&lt;p&gt;- optee-&amp;gt;call_queue.mutex is not initialized by optee_cq_init()
  - optee-&amp;gt;supp mutex and completions is not initialized by
    optee_supp_init()
  - optee-&amp;gt;rpmb_dev_mutex is not initialized yet,
  - the message argument cache is not initialized by
    optee_shm_arg_cache_init()
  - optee-&amp;gt;ctx is still NULL&lt;/p&gt;
&lt;p&gt;Any open session or invoke during this window takes uninitialized
mutexes and dereferences a NULL pointer.&lt;/p&gt;
&lt;p&gt;Fix it by moving both tee_device_register() calls down to the point
where all of struct optee is set up.&lt;/p&gt;
&lt;p&gt;[JW: adding fixes and cc]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99024</guid>
    </item>
    <item>
      <title>GHSA-qp8f-jjvm-547w</title>
      <link>https://db.gcve.eu/vuln/ghsa-qp8f-jjvm-547w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;optee: register TEE devices only once fully initialized&lt;/p&gt;
&lt;p&gt;optee_probe() called tee_device_register() on both the client and the
supplicant device before the rest of struct optee had been initialized.&lt;/p&gt;
&lt;p&gt;tee_device_register() calls cdev_device_add(), which does two things at
once: it creates /dev/tee0 and /dev/teepriv0, and it links the device
into the tee class so that class_find_device() can find it. From that
moment on the device is reachable both from user space via tee_open()
and from kernel space via tee_client_open_context(). The only gate in
teedev_open() is tee_device_get(), which merely checks that
teedev-&amp;gt;desc is non-NULL, which was already set by tee_device_alloc().
Therefore, there is effectively no gate at all.&lt;/p&gt;
&lt;p&gt;A context opened in that window can run against a struct optee where&lt;/p&gt;
&lt;p&gt;- optee-&amp;gt;call_queue.mutex is not initialized by optee_cq_init()
  - optee-&amp;gt;supp mutex and completions is not initialized by
    optee_supp_init()
  - optee-&amp;gt;rpmb_dev_mutex is not initialized yet,
  - the message argument cache is not initialized by
    optee_shm_arg_cache_init()
  - optee-&amp;gt;ctx is still NULL&lt;/p&gt;
&lt;p&gt;Any open session or invoke during this window takes uninitialized
mutexes and dereferences a NULL pointer.&lt;/p&gt;
&lt;p&gt;Fix it by moving both tee_device_register() calls down to the point
where all of struct optee is set up.&lt;/p&gt;
&lt;p&gt;[JW: adding fixes and cc]&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;optee: register TEE devices only once fully initialized&lt;/p&gt;
&lt;p&gt;optee_probe() called tee_device_register() on both the client and the
supplicant device before the rest of struct optee had been initialized.&lt;/p&gt;
&lt;p&gt;tee_device_register() calls cdev_device_add(), which does two things at
once: it creates /dev/tee0 and /dev/teepriv0, and it links the device
into the tee class so that class_find_device() can find it. From that
moment on the device is reachable both from user space via tee_open()
and from kernel space via tee_client_open_context(). The only gate in
teedev_open() is tee_device_get(), which merely checks that
teedev-&amp;gt;desc is non-NULL, which was already set by tee_device_alloc().
Therefore, there is effectively no gate at all.&lt;/p&gt;
&lt;p&gt;A context opened in that window can run against a struct optee where&lt;/p&gt;
&lt;p&gt;- optee-&amp;gt;call_queue.mutex is not initialized by optee_cq_init()
  - optee-&amp;gt;supp mutex and completions is not initialized by
    optee_supp_init()
  - optee-&amp;gt;rpmb_dev_mutex is not initialized yet,
  - the message argument cache is not initialized by
    optee_shm_arg_cache_init()
  - optee-&amp;gt;ctx is still NULL&lt;/p&gt;
&lt;p&gt;Any open session or invoke during this window takes uninitialized
mutexes and dereferences a NULL pointer.&lt;/p&gt;
&lt;p&gt;Fix it by moving both tee_device_register() calls down to the point
where all of struct optee is set up.&lt;/p&gt;
&lt;p&gt;[JW: adding fixes and cc]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qp8f-jjvm-547w</guid>
    </item>
  </channel>
</rss>
