CVE-2025-54952
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-54952 is a critical-severity Integer Overflow to Buffer Overflow (CWE-680) vulnerability in Facebook (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An integer overflow vulnerability exists in the model loading process of ExecuTorch, where malformed inputs can trigger allocation of smaller-than-expected memory regions. The flaw is tracked as CWE-680 and affects all versions prior to commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b. It carries a CVSS 3.1 score of 9.8, reflecting its potential for severe impact during deserialization of untrusted model files.
Remote attackers can exploit the issue over the network without authentication or user interaction by supplying a crafted ExecuTorch model. Successful exploitation may result in arbitrary code execution, memory corruption, or other unintended behavior within the loading context.
The referenced GitHub commit and Meta security advisory identify the fix as an update to the affected model-loading code; practitioners should upgrade ExecuTorch to a build that includes commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b. The associated EPSS score has remained flat at 0.0110 with no observed rise after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-23960
Vulnerability Data
An integer overflow vulnerability in the loading of ExecuTorch models can cause smaller-than-expected memory regions to be allocated, potentially resulting in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit 8f062d3f661e20bb19b24b767b9a9a46e8359f2b.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis (static, dynamic, fuzzing) finds integer-overflow-to-allocation defects before deployment.
Mandates documented development standards and tools that enforce secure coding rules against unsafe integer arithmetic.
Requires engineering principles such as safe arithmetic and bounds-checked allocation that directly stop integer overflow during memory-size computation.
Validates untrusted size/offset inputs before they reach allocation calculations, structurally blocking the integer overflow path.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent integer-overflow flaws during development, but eliminating only this CWE covers only part of the broad control intent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect integer-overflow-to-buffer-overflow conditions during development.
Secure development life cycle mandates practices that can catch integer overflows before deployment.
Application security requirements can specify safe integer handling and bounds checking.
Secure architecture principles encourage use of safe arithmetic libraries and overflow detection.
Secure coding standards directly require prevention of integer overflows that lead to buffer overflows.