Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 262062c01f5a817104c88bf6eacb7c6ffdc7018d, 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388, 681adbc9c7a820279582a295e183fa6a1d1b4ec4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 262062c01f5a817104c88bf6eacb7c6ffdc7018d, 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388, 681adbc9c7a820279582a295e183fa6a1d1b4ec4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

—No exploit Fix available
Published
Oct 23, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99024

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.12affected
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 8de131e1a2ab379641bb475f1bcb472a1a1d75dfaffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before db36c37a2c3f13d5fd0f1afd8e2391d6c50793e6affected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 6b21a716ccab7fa42e8dfa3118000bc5274004abaffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 262062c01f5a817104c88bf6eacb7c6ffdc7018daffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 8cae1605be8a047ae3a62df07b9474d61462c4f6affected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 681adbc9c7a820279582a295e183fa6a1d1b4ec4affected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 2f7240f0a6fd83df274fc0a2abf0609b4e6bd388affected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before c108feca0a096f8db25d1b69130035025e9e936daffected · git
    • before 4.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.11-17.2.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99022Oct 23, 2026 · regulator: ltc3676: don't read the write-only HRST and CLIRQ registers
    0Monitor
  • ← EarlierCVE-2026-99023Oct 23, 2026 · power: sequencing: pcie-m2: Fix leaking array from of_regulator_bulk_get_all()
    0Monitor
  • Later →CVE-2026-99025Oct 23, 2026 · openvswitch: fix soft lockup in the netlink flow dump
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux262062c01f5a817104c88bf6eacb7c6ffdc7018dVendor (CNA)
Linux Linux2f7240f0a6fd83df274fc0a2abf0609b4e6bd388Vendor (CNA)
Linux Linux681adbc9c7a820279582a295e183fa6a1d1b4ec4Vendor (CNA)
Linux Linux6b21a716ccab7fa42e8dfa3118000bc5274004abVendor (CNA)
Linux Linux8cae1605be8a047ae3a62df07b9474d61462c4f6Vendor (CNA)
Linux Linux8de131e1a2ab379641bb475f1bcb472a1a1d75dfVendor (CNA)
Linux Linuxc108feca0a096f8db25d1b69130035025e9e936dVendor (CNA)
Linux Linuxdb36c37a2c3f13d5fd0f1afd8e2391d6c50793e6Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 11, 2026+19 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records