Skip to main content
VulnerabilityPublished

CVE-2026-68984: Samsung Semiconductor Exynos 2100 · Integer Overflow or Wraparound

Affects Samsung Semiconductor Exynos 2100Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to November 2026 soon.

Data as of 5 Nov 2026, 03:12 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
Patch
Available – fixed in November 2026

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Exynos to November 2026.

Affected software

ProductAffectedFixed in
Samsung SemiconductorExynos 2100Affected
  • =0
Fixed in
  • November 2026
Samsung SemiconductorExynos 1280Affected
  • =0
Fixed in
  • November 2026
Samsung SemiconductorExynos 2200Affected
  • =0
Fixed in
  • November 2026
Samsung SemiconductorExynos 1380Affected
  • =0
Fixed in
  • November 2026
Samsung SemiconductorExynos 1480Affected
  • =0
Fixed in
  • November 2026
Samsung SemiconductorExynos 2400Affected
  • =0
Fixed in
  • November 2026

AI-suggested

A fix for this vulnerability was released in November 2026. Users and administrators should apply the official patch from Samsung Semiconductor to remediate this issue.

Description

An integer overflow vulnerability in the Samsung Exynos NPU kernel driver for the Exynos 2100 chipset allows an unprivileged application to cause memory corruption. This flaw is identified as CWE-190 and affects version 0 of the product. A fix was released in November 2026.

References

Community reviews

Loading reviews…