Skip to main content
VulnerabilityPublished

CVE-2026-48175: Samsung Semiconductor Exynos 1280 · Improper Validation of Specified Index, Position, or Offset in Input

Affects Samsung Semiconductor Exynos 1280Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to September 2026 when convenient.

Data as of 5 Nov 2026, 03:12 UTC

Severity
Medium

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

Thin evidence

One scorer or none
Patch
Available – fixed in September 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 September 2026.

Affected software

ProductAffectedFixed in
Samsung SemiconductorExynos 1280Affected
  • =0
Fixed in
  • September 2026
Samsung SemiconductorExynos 1330Affected
  • =0
Fixed in
  • September 2026
Samsung SemiconductorExynos 1380Affected
  • =0
Fixed in
  • September 2026
Samsung SemiconductorExynos 1480Affected
  • =0
Fixed in
  • September 2026
Samsung SemiconductorExynos 2400Affected
  • =0
Fixed in
  • September 2026
Samsung SemiconductorExynos 1580Affected
  • =0
Fixed in
  • September 2026

AI-suggested

A fix for this vulnerability was released by Samsung Semiconductor in September 2026. Users and integrators of the Exynos 1280 should apply the official update to remediate this issue.

Description

CVE-2026-48175 is a vulnerability in Samsung Semiconductor's Exynos 1280 where processing a malformed RRC message causes an out-of-bounds read, leading to a denial-of-service condition. The issue is due to improper validation of specified index, position, or offset in input. A fix was released in September 2026.

References

Community reviews

Loading reviews…