CVE-2026-48183: Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Samsung Semiconductor Exynos 1480 October 2026; Samsung Semiconductor Exynos 1580 October 2026; Samsung Semiconductor Exynos 1680 October 2026.
Low priority for now. Upgrade to Samsung Semiconductor Exynos 1480 October 2026; Samsung Semiconductor Exynos 1580 October 2026; Samsung Semiconductor Exynos 1680 October 2026 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Nov 5, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-281
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (samsungsemiconductor). Independent of NVD's CPE analysis and usually ahead of it.
Samsung Semiconductor Exynos 1480
- before October 2026affected · date
Samsung Semiconductor Exynos 1580
- before October 2026affected · date
Samsung Semiconductor Exynos 1680
- before October 2026affected · date
Samsung Semiconductor Exynos 2400
- before October 2026affected · date
Samsung Semiconductor Exynos 2500
- before October 2026affected · date
Samsung Semiconductor Exynos 2600
- before October 2026affected · date
Same product
samsung semiconductor: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-69050Out-of-bounds memory access in a device driver due to improper resource state tracking.39Monitor
- CVE-2026-68991In the Samsung Exynos ENN NeuralNetworks HAL, improper input validation during request processing can cause memory corruption and lead to a…39Monitor
- CVE-2026-68990In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading…31Monitor
Published before and after this one in the same product
- Later →CVE-2026-68993Nov 5, 2026 · A double free vulnerability in NPU driver due to improper pointer management (940)25Monitor
- Later →CVE-2026-68994Nov 5, 2026 · A double free vulnerability in NPU driver due to improper pointer management (941)29Monitor
- Later →CVE-2026-69005Nov 5, 2026 · Integer overflow in NPU driver parameter processing due to insufficient bounds checking.29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Samsung Semiconductor Exynos 1480 | October 2026 | Vendor (CNA) |
| Samsung Semiconductor Exynos 1580 | October 2026 | Vendor (CNA) |
| Samsung Semiconductor Exynos 1680 | October 2026 | Vendor (CNA) |
| Samsung Semiconductor Exynos 2400 | October 2026 | Vendor (CNA) |
| Samsung Semiconductor Exynos 2500 | October 2026 | Vendor (CNA) |
| Samsung Semiconductor Exynos 2600 | October 2026 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+7 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-281 · Improper Preservation of PermissionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 9.1
- Severity— → critical
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.