Skip to main content
VulnerabilityPublished

CVE-2026-48183: Samsung Semiconductor Exynos 1480 · Improper Preservation of Permissions

Affects Samsung Semiconductor Exynos 1480Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to October 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 October 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 October 2026.

Affected software

ProductAffectedFixed in
Samsung SemiconductorExynos 1480Affected
  • =0
Fixed in
  • October 2026
Samsung SemiconductorExynos 2400Affected
  • =0
Fixed in
  • October 2026
Samsung SemiconductorExynos 1580Affected
  • =0
Fixed in
  • October 2026
Samsung SemiconductorExynos 2500Affected
  • =0
Fixed in
  • October 2026
Samsung SemiconductorExynos 2600Affected
  • =0
Fixed in
  • October 2026
Samsung SemiconductorExynos 1680Affected
  • =0
Fixed in
  • October 2026

AI-suggested

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

Description

CVE-2026-48183 is a vulnerability in the Samsung Semiconductor Exynos 1480 chipset involving improper permission handling during buffer operations. This flaw allows untrusted applications to create memory mappings with inappropriate permissions, potentially leading to unauthorized access or privilege escalation. A fix for this issue was released in October 2026.

References

Community reviews

Loading reviews…