Quick answers
- Is CVE-2026-82926 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82926 being exploited in the wild.
- How severe is CVE-2026-82926?
- Medium severity, with a CVSS score of 5.5, published 1 September 2026.
- Which products and versions are affected?
- Samsung mTower before afef59aa6f55c5d5ebf9b14bc020bf1c2c37489a.
- Is there a fix for CVE-2026-82926?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82926 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-82926?
- Check whether you run Samsung mTower 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 NULL pointer dereference vulnerability exists in the tee_ioctl_invoke() function within tee/kernel/entry_std.c. The vulnerability occurs because the function does not validate the return value from tee_ta_get_session() before passing the session pointer to tee_ta_invoke_command(), which unconditionally dereferences it via sess->ctx->ops->enter_invoke_cmd(). An unauthenticated local attacker can trigger this by sending TEE_IOC_INVOKE ioctl calls with invalid, zero, or stale session identifiers, causing a NULL pointer dereference in the secure world and resulting in denial of service. The attack is reachable through the live cmse_nonsecure_entry ioctl veneer and requires no special privileges. The fix, merged in commit afef59aa6f55c5d5ebf9b14bc020bf1c2c37489a, adds proper null-pointer checks to reject invalid sessions.
Affected products
- Samsung mTower before afef59aa6f55c5d5ebf9b14bc020bf1c2c37489a
Timeline
- 2026-09-01: disclosed