Skip to content
Fencer Vulns
medium 6.3

CVE-2017-7936 json

A stack-based buffer overflow issue was discovered in NXP i.MX 50, i.MX 53, i.MX 6ULL, i.MX 6UltraLite, i.MX 6SoloLite, i.MX 6Solo, i.MX 6D…

published 2017-08-07 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16907

cvss
6.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

A stack-based buffer overflow issue was discovered in NXP i.MX 50, i.MX 53, i.MX 6ULL, i.MX 6UltraLite, i.MX 6SoloLite, i.MX 6Solo, i.MX 6DualLite, i.MX 6SoloX, i.MX 6Dual, i.MX 6Quad, i.MX 6DualPlus, i.MX 6QuadPlus, Vybrid VF3xx, Vybrid VF5xx, and Vybrid VF6xx. When the device is configured in security enabled configuration, SDP could be used to download a small section of code to an unprotected region of memory.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-17-152-02 updated cvss 5.3

NXP i.MX Product Family

  • i.MX .MX 7Solo i.MX 6Dual i.MX 6DualLite i.MX 6DualPlus i.MX 6Quad i.MX 6QuadPlus
    +12 more products
    i.MX 6Solo i.MX 6SoloLite i.MX 6SoloX i.MX 6ULL i.MX 6UltraLit i.MX 7Dual i.MX 28 i.MX 50 i.MX 53 i.MX Vybrid VF3xx i.MX Vybrid VF5xx i.MX Vybrid VF6xx
    affected: mitigation “Because this is a hardware vulnerability, there are no software workarounds available.”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 6.3 CVSS:3.0/AV:P/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.4 AV:L/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • n/a NXP i.MX Product Family

Classification

Weakness
  • CWE-121 Stack-based Buffer Overflow
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns 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.