Quick answers
- Is CVE-2026-21068 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-21068 being exploited in the wild.
- How severe is CVE-2026-21068?
- High severity, with a CVSS score of 7.8, published 10 August 2026.
- Which products and versions are affected?
- Samsung Mobile Firmware before August 2026 SMR Release 1.
- Is there a fix for CVE-2026-21068?
- A patch was published on 2026-08: SMR Aug-2026 Release 1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-21068 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-21068?
- Check whether you run Samsung Mobile Firmware at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow exists in libril_sem.so prior to the August 2026 SMR Release 1. The vulnerability is triggered by local attack vectors and requires privilege escalation or an already-privileged execution context. An attacker with local access and sufficient privileges can overflow the stack to overwrite return addresses or other control flow data, achieving arbitrary code execution. The vulnerability affects Samsung mobile firmware versions before the August 2026 security patch; patches are available in SMR Aug-2026 Release 1 and later.
Affected products
- Samsung Mobile Firmware before August 2026 SMR Release 1
Timeline
- 2026-08-10: disclosed
- 2026-08: patched: SMR Aug-2026 Release 1