cve.bz

CVE-2026-48178

8.8 highEPSS 0.1%

High (8.8) in samsung semiconductor. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

Out of bound access in PPC due to race condition in global variable access

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-413 Improper Resource Locking
Published
Modified
Assigned by
samsungsemiconductor (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-48178 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48178?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48178?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48178 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Samsung Semiconductor Exynos 2200before October 2026
Samsung Semiconductor Exynos 2400before October 2026
Samsung Semiconductor Exynos 2500before October 2026
Samsung Semiconductor Exynos 2600before October 2026

History

  1. Scored 8.8 high

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON