Double free in NPU driver of Samsung Exynos chipsets
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from CNA.
Summary
Samsung Semiconductor Exynos 1480, Exynos 2400, Exynos 1580 and Exynos 2500 are affected from 0 before November 2026. Improper pointer management in the NPU driver causes a double free (CWE-415).
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
Description from the CNA
A double free vulnerability in NPU driver due to improper pointer management (941)
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Samsung Semiconductor | Exynos 1480 | before November 2026 | November 2026 | Patch available | CNA |
| Samsung Semiconductor | Exynos 2400 | before November 2026 | November 2026 | Patch available | CNA |
| Samsung Semiconductor | Exynos 1580 | before November 2026 | November 2026 | Patch available | CNA |
| Samsung Semiconductor | Exynos 2500 | before November 2026 | November 2026 | Patch available | CNA |
- Exynos 1480 VendorSamsung Semiconductor Affected before November 2026 Fixed in November 2026 Patch available CNA
- Exynos 2400 VendorSamsung Semiconductor Affected before November 2026 Fixed in November 2026 Patch available CNA
- Exynos 1580 VendorSamsung Semiconductor Affected before November 2026 Fixed in November 2026 Patch available CNA
- Exynos 2500 VendorSamsung Semiconductor Affected before November 2026 Fixed in November 2026 Patch available CNA
Remediation
Samsung Semiconductor lists November 2026 as the fixed version for Exynos 1480, Exynos 2400, Exynos 1580 and Exynos 2500.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
- Fix · CNA Exynos 1480 (Samsung Semiconductor) Fixed in November 2026
- Fix · CNA Exynos 2400 (Samsung Semiconductor) Fixed in November 2026
- Fix · CNA Exynos 1580 (Samsung Semiconductor) Fixed in November 2026
- Fix · CNA Exynos 2500 (Samsung Semiconductor) Fixed in November 2026
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Samsung Semiconductor Exynos 1480, Exynos 2400 November 2026
9 records Highest priority Priority LOW 9 LOW
Other records, highest priority first
- TI-2026-85329 Samsung Exynos GPU driver memory corruption from improper VMID validationPriority LOW 22
- TI-2026-85328 Out-of-bounds memory access in Samsung Exynos device driverPriority LOW 22
- TI-2026-85325 Out-of-bounds write in Exynos NPU driver ioctl handlerPriority LOW 22
- Release ·
Samsung Semiconductor Exynos 1580, Exynos 2500 November 2026
8 records Highest priority Priority LOW 8 LOW
Other records, highest priority first
- TI-2026-85329 Samsung Exynos GPU driver memory corruption from improper VMID validationPriority LOW 22
- TI-2026-85328 Out-of-bounds memory access in Samsung Exynos device driverPriority LOW 22
- TI-2026-85324 Missing length field checks in Samsung Exynos GNSS firmware loaderPriority LOW 22
Timeline
- 2026-11-05 Threatist record created from CVE-2026-68994
- 2026-11-05 Alias added: GHSA-pc87-g94f-jfx4
References
More Samsung Semiconductor vulnerabilities
- TI-2026-85310 Out-of-bounds read in Samsung Exynos RRC message handling CVSS 3.1MEDIUM 5.5
- TI-2026-85330 Insufficient length validation in Samsung Exynos Modem GNSS loader CVSS —
- TI-2026-85329 Samsung Exynos GPU driver memory corruption from improper VMID validation CVSS —
- TI-2026-85328 Out-of-bounds memory access in Samsung Exynos device driver CVSS —
- TI-2026-85327 Reference count flaw in Samsung GPU driver corrupts memory CVSS —
- TI-2026-85326 Improper synchronization in Samsung Exynos GPU driver corrupts memory CVSS —
Sources
- CVE-2026-68994 · CVE Program
- CVE-2026-68994 · NVD
- FIRST EPSS
- GHSA-pc87-g94f-jfx4 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences