<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:35:43.221174+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-99024</id>
    <title>BELL-CVE-2026-99024</title>
    <updated>2026-11-17T10:35:43.231269+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99024"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</id>
    <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>
    <updated>2026-11-17T10:35:43.231318+00:00</updated>
    <content>certfr-2026-avi-1537</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396130</id>
    <title>EUVD-2026-396130</title>
    <updated>2026-11-17T10:35:43.231338+00:00</updated>
    <content>EUVD-2026-396130</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396130"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99024</id>
    <title>fkie_cve-2026-99024</title>
    <updated>2026-11-17T10:35:43.231350+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>optee: register TEE devices only once fully initialized</p>
<p>optee_probe() called tee_device_register() on both the client and the
supplicant device before the rest of struct optee had been initialized.</p>
<p>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-&gt;desc is non-NULL, which was already set by tee_device_alloc().
Therefore, there is effectively no gate at all.</p>
<p>A context opened in that window can run against a struct optee where</p>
<p>- optee-&gt;call_queue.mutex is not initialized by optee_cq_init()
  - optee-&gt;supp mutex and completions is not initialized by
    optee_supp_init()
  - optee-&gt;rpmb_dev_mutex is not initialized yet,
  - the message argument cache is not initialized by
    optee_shm_arg_cache_init()
  - optee-&gt;ctx is still NULL</p>
<p>Any open session or invoke during this window takes uninitialized
mutexes and dereferences a NULL pointer.</p>
<p>Fix it by moving both tee_device_register() calls down to the point
where all of struct optee is set up.</p>
<p>[JW: adding fixes and cc]</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99024"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qp8f-jjvm-547w</id>
    <title>GHSA-qp8f-jjvm-547w</title>
    <updated>2026-11-17T10:35:43.231389+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>optee: register TEE devices only once fully initialized</p>
<p>optee_probe() called tee_device_register() on both the client and the
supplicant device before the rest of struct optee had been initialized.</p>
<p>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-&gt;desc is non-NULL, which was already set by tee_device_alloc().
Therefore, there is effectively no gate at all.</p>
<p>A context opened in that window can run against a struct optee where</p>
<p>- optee-&gt;call_queue.mutex is not initialized by optee_cq_init()
  - optee-&gt;supp mutex and completions is not initialized by
    optee_supp_init()
  - optee-&gt;rpmb_dev_mutex is not initialized yet,
  - the message argument cache is not initialized by
    optee_shm_arg_cache_init()
  - optee-&gt;ctx is still NULL</p>
<p>Any open session or invoke during this window takes uninitialized
mutexes and dereferences a NULL pointer.</p>
<p>Fix it by moving both tee_device_register() calls down to the point
where all of struct optee is set up.</p>
<p>[JW: adding fixes and cc]</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qp8f-jjvm-547w"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99024</id>
    <title>msrc_CVE-2026-99024 — optee: register TEE devices only once fully initialized</title>
    <updated>2026-11-17T10:35:43.231420+00:00</updated>
    <content>msrc_CVE-2026-99024</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99024"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99024</id>
    <title>UBUNTU-CVE-2026-99024</title>
    <updated>2026-11-17T10:35:43.231436+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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-&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-&gt;call_queue.mutex is not initialized by optee_cq_init()   - optee-&gt;supp mutex and completions is not initialized by     optee_supp_init()   - optee-&gt;rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee-&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]</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99024"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</id>
    <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-17T10:35:43.231676+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152"/>
  </entry>
</feed>
