Skip to content
Fencer Intel
high 8.8

CVE-2026-48178 json

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

published 7d ago modified yesterday also EUVD-2026-117261

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

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

Patch / fix

  • Samsung Semiconductor Exynos 2200 October 2026
  • Samsung Semiconductor Exynos 2400 October 2026
  • Samsung Semiconductor Exynos 2500 October 2026
  • Samsung Semiconductor Exynos 2600 October 2026

Is CVE-2026-48178 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
yesterday

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Samsung Semiconductor Exynos 2200
  • Samsung Semiconductor Exynos 2400
  • Samsung Semiconductor Exynos 2500
  • Samsung Semiconductor Exynos 2600

Classification

Weakness
  • CWE-413 Improper Resource Locking

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.