CVE-2026-99024

optee: 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]

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.177% likely to be exploited in the next 30 days, higher than 7.375% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding 8de131e1a2ab379641bb475f1bcb472a1a1d75df (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6 (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding 6b21a716ccab7fa42e8dfa3118000bc5274004ab (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding 262062c01f5a817104c88bf6eacb7c6ffdc7018d (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding 8cae1605be8a047ae3a62df07b9474d61462c4f6 (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding 681adbc9c7a820279582a295e183fa6a1d1b4ec4 (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388 (affected)
  • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 up to but excluding c108feca0a096f8db25d1b69130035025e9e936d (affected)
LinuxLinux
  • Default status: affected
  • 4.12 (affected)
  • 0 up to but excluding 4.12 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References