Skip to content
Fencer Intel
no cvss —

CVE-2025-66366 json

Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash

published 4d ago modified 3h ago also EUVD-2025-211265

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash

Patch / fix

  • Samsung Semiconductor Exynos 1280 July 2026
  • Samsung Semiconductor Exynos 1330 July 2026
  • Samsung Semiconductor Exynos 1380 July 2026
  • Samsung Semiconductor Exynos 1480 July 2026
  • Samsung Semiconductor Exynos 2400 July 2026
  • Samsung Semiconductor Exynos 1580 July 2026
  • Samsung Semiconductor Exynos 2500 July 2026
  • Samsung Semiconductor Exynos Modem 5300 July 2026
  • Samsung Semiconductor Exynos Modem 5400 July 2026
  • Samsung Semiconductor Exynos Modem 5410 July 2026

Is CVE-2025-66366 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

Exploit prediction

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

Affected products

  • Samsung Semiconductor Exynos 1280
  • Samsung Semiconductor Exynos 1330
  • Samsung Semiconductor Exynos 1380
  • Samsung Semiconductor Exynos 1480
  • Samsung Semiconductor Exynos 2400
  • Samsung Semiconductor Exynos 1580
  • Samsung Semiconductor Exynos 2500
  • Samsung Semiconductor Exynos Modem 5300
  • Samsung Semiconductor Exynos Modem 5400
  • Samsung Semiconductor Exynos Modem 5410

Classification

Weakness
  • CWE-129 Improper Validation of Array Index

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.