# CVE-2026-71968: OP-TEE OS 4.10.0 Use-After-Free via Trusted Application Loader TA_FLAG_CONCURRENT

> Attackers with signed TA loading capabilities can corrupt secure-world kernel memory via a use-after-free in the TA loader, potentially leading to code execution or privilege escalation.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-71968, GHSA-p84g-83m7-53p6, UBUNTU-CVE-2026-71968

## What is CVE-2026-71968?

CVE-2026-71968 is a high-severity use after free vulnerability in OP-TEE optee_os, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OP-TEE OS through 4.10.0, fixed in commit 8794043, contains a use-after-free vulnerability in the Trusted Application loader that allows attackers with the ability to load a signed Trusted Application to corrupt secure-world kernel memory by setting the TA_FLAG_CONCURRENT flag in a user TA signed header. Attackers can cause two concurrent sessions to operate on the same shared context without locking, corrupting the uctx->vm_info.regions list during memref parameter mapping and unmapping to free vm_region nodes still in use, resulting in a use-after-free in S-EL1 secure-world kernel memory.

Weakness: CWE-416 (Use After Free), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-71968?


## How do I fix CVE-2026-71968?

No fix has been published for CVE-2026-71968 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71968 being exploited?

There is no known exploitation of CVE-2026-71968 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71968 and fix it if it is affected.

What it is: CVE-2026-71968 is a high-severity use after free vulnerability in OP-TEE optee_os, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71968 in the wild and no public exploit code.

Affected product: OP-TEE optee_os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71968/ (Markdown: https://insights.sbomify.com/CVE-2026-71968/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71968
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71968
- OSV: https://osv.dev/vulnerability/CVE-2026-71968

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71968/
Summaries are generated and may contain mistakes; the official description above is the record.