PatchSiren cyber security CVE debrief
CVE-2026-23790 Samsung CVE debrief
A double-free vulnerability in the Samsung Exynos DPU driver due to improper pointer management during DMA buffer reallocation leads to kernel memory corruption and a potential use-after-free. This issue affects systems using Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500, 1680, and 2600. Defenders should prioritize verifying affected versions and assessing exposure. The vulnerability has a CVSS score of 4.2 and is classified as MEDIUM severity. The CVE record was published on 2026-09-14T02:17:13.537Z.
- Vendor
- Samsung
- Product
- Exynos 1280 firmware
- CVSS
- MEDIUM 4.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-14
- Original CVE updated
- 2026-09-22
- Advisory published
- 2026-09-14
- Advisory updated
- 2026-09-22
Who should care
Defenders responsible for systems using Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500, 1680, and 2600 should assess exposure and prioritize verifying affected versions and remediation details.
Why it matters
CVE-2026-23790 is a double-free vulnerability in the Samsung Exynos DPU driver that leads to kernel memory corruption and potential use-after-free conditions. Defenders should prioritize verifying affected versions, assessing exposure, and applying security updates when available.
- Verification of affected versions is required to assess exposure.
- Potential kernel memory corruption and use-after-free conditions may lead to system instability.
- Remediation priority is high for systems using affected processors.
- Exposure assessment is critical for defenders responsible for system security.
Technical summary
The Samsung Exynos DPU driver is vulnerable to a double-free issue due to improper pointer management during DMA buffer reallocation. This leads to kernel memory corruption and a potential use-after-free condition. The vulnerability affects Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500, 1680, and 2600. Defenders should prioritize verifying affected versions, assessing exposure, and applying security updates when available. The CVE record and NVD entry provide details on the double-free vulnerability.
Defensive priority
Defenders should prioritize verifying affected versions and assessing exposure in systems using Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500, 1680, and 2600. Remediation priority follows from verifying vendor-provided security updates.
Recommended defensive actions
- Verify affected versions of Samsung Mobile Processor Exynos
- Assess exposure in systems using affected processors
- Monitor for vendor-provided security updates
- Apply security updates when available
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions and retest remediated assets
Evidence notes
The CVE record and NVD entry provide details on the double-free vulnerability in the Samsung Exynos DPU driver. However, specific affected versions and remediation details require verification from official sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-23790 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-23790
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-23790 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-23790
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://semiconductor.samsung.com/support/quality-support/product-security-updates/
-
Source reference
Unverified legacy reference
URL: https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2026-23790/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.