optee: register TEE devices only once fully initialized
Summary
| CVE | CVE-2026-99024 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-23 13:17:25 UTC |
| Updated | 2026-10-30 13:21:38 UTC |
| 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] |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.062150000 (date 2026-10-30)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 8de131e1a2ab379641bb475f1bcb472a1a1d75df git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6 git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 6b21a716ccab7fa42e8dfa3118000bc5274004ab git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 262062c01f5a817104c88bf6eacb7c6ffdc7018d git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 8cae1605be8a047ae3a62df07b9474d61462c4f6 git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 681adbc9c7a820279582a295e183fa6a1d1b4ec4 git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388 git | Not specified |
| CNA | Linux | Linux | affected 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 c108feca0a096f8db25d1b69130035025e9e936d git | Not specified |
| CNA | Linux | Linux | affected 4.12 | Not specified |
| CNA | Linux | Linux | unaffected 4.12 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.273 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.224 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.191 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.113 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.57 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.11 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/2f7240f0a6fd83df274fc0a2abf0609b4e6bd388 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8cae1605be8a047ae3a62df07b9474d61462c4f6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8de131e1a2ab379641bb475f1bcb472a1a1d75df | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6b21a716ccab7fa42e8dfa3118000bc5274004ab | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c108feca0a096f8db25d1b69130035025e9e936d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/262062c01f5a817104c88bf6eacb7c6ffdc7018d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/681adbc9c7a820279582a295e183fa6a1d1b4ec4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.