Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99024optee: register TEE devices only once fully initialized

Description

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->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->call_queue.mutex is not initialized by optee_cq_init() - optee->supp mutex and completions is not initialized by optee_supp_init() - optee->rpmb_dev_mutex is not initialized yet, - the message argument cache is not initialized by optee_shm_arg_cache_init() - optee->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]

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < 8de131e1a2ab379641bb475f1bcb472a1a1d75df
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < 6b21a716ccab7fa42e8dfa3118000bc5274004ab
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < 262062c01f5a817104c88bf6eacb7c6ffdc7018d
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < 8cae1605be8a047ae3a62df07b9474d61462c4f6
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < 681adbc9c7a820279582a295e183fa6a1d1b4ec4
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388
    • affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 – < c108feca0a096f8db25d1b69130035025e9e936d
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99024 badge
[![CVE-2026-99024](https://cveledger.app/badge/CVE-2026-99024.svg)](https://cveledger.app/cve/CVE-2026-99024)

Record last updated .