CVE-2026-99024 — optee: register TEE devices only once fully initialized
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]
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < 262062c01f5a817104c88bf6eacb7c6ffdc7018d≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < 8cae1605be8a047ae3a62df07b9474d61462c4f6≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < 681adbc9c7a820279582a295e183fa6a1d1b4ec4≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < c108feca0a096f8db25d1b69130035025e9e936dversion 4.12≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < 8de131e1a2ab379641bb475f1bcb472a1a1d75df≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6 and 1 more≥ 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and < 6b21a716ccab7fa42e8dfa3118000bc5274004ab |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 23, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
10 on the record
- git.kernel.org/stable/c/8de131e1a2ab379641bb475f1bcb472a1a1d75df
- git.kernel.org/stable/c/db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6
- github.com/advisories/GHSA-qp8f-jjvm-547w
- git.kernel.org/stable/c/6b21a716ccab7fa42e8dfa3118000bc5274004ab
- git.kernel.org/stable/c/2f7240f0a6fd83df274fc0a2abf0609b4e6bd388
- git.kernel.org/stable/c/262062c01f5a817104c88bf6eacb7c6ffdc7018d
- nvd.nist.gov/vuln/detail/CVE-2026-99024
- git.kernel.org/stable/c/681adbc9c7a820279582a295e183fa6a1d1b4ec4
- git.kernel.org/stable/c/c108feca0a096f8db25d1b69130035025e9e936d
- git.kernel.org/stable/c/8cae1605be8a047ae3a62df07b9474d61462c4f6
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-99024 is "optee: register TEE devices only once fully initialized", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.