<?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:35:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99024</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99024</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-99024</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396130</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396130</link>
      <description>EUVD-2026-396130</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396130</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99024</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/fkie_cve-2026-99024</guid>
    </item>
    <item>
      <title>GHSA-qp8f-jjvm-547w</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/ghsa-qp8f-jjvm-547w</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99024 — optee: register TEE devices only once fully initialized</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99024</link>
      <description>msrc_CVE-2026-99024</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99024</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99024</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99024</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 249 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: optee: register TEE devices only once fully initialized optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized. 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. A context opened in that window can run against a struct optee where   - 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 Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer. Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up. [JW: adding fixes and cc]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 249 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: optee: register TEE devices only once fully initialized optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized. 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. A context opened in that window can run against a struct optee where   - 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 Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer. Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up. [JW: adding fixes and cc]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99024</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>
