CVE-2026-48183
CVE-2026-48183 — Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions
Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions
Published Updated Sources: NVD, Samsung Semiconductor (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Public exploit
exploit code published, no use observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
Unscored
no source published a base score
Remediation
The vendor's own words where we have them.
Upgrade Exynos 1480 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Samsung Semiconductor | Exynos 1480 | 0 | Vulnerable |
| Samsung Semiconductor | Exynos 2400 | 0 | Vulnerable |
| Samsung Semiconductor | Exynos 1580 | 0 | Vulnerable |
| Samsung Semiconductor | Exynos 2500 | 0 | Vulnerable |
| Samsung Semiconductor | Exynos 2600 | 0 | Vulnerable |
| Samsung Semiconductor | Exynos 1680 | 0 | Vulnerable |
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-281 · Improper Preservation of Permissions
- Read Application Data
- Modify Application Data::
Weakness & attack patterns
- CWE-281
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
PoC repos
1
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Initial · CVE published
Nov 5, 2026 · NVD
CVE published by MITRE.
Nov 5, 2026 · SOCRadar CTI
References
1 on the record
- semiconductor.samsung.com/support/quality-support/product-security-updates/
Vendor Advisory, NIST
Elsewhere on this site
- Samsung Semiconductorevery CVE for this vendor
- Unclassifiedsame class
- CWE-281other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-48183 is Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions, a unscored vulnerability affecting Exynos 1480, Exynos 2400, Exynos 1580, Exynos 2500, Exynos 2600, Exynos 1680 from Samsung Semiconductor. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-48183. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.