Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-57983 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Linux Kernel. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation of Remote Services (T1210); ranked at the 13th 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.
CVE-2024-57983 is a memory corruption vulnerability in the Linux kernel's th1520 mailbox driver, stemming from an incorrectly sized array used in the th1520_mbox_suspend_noirq and th1520_mbox_resume_noirq functions. These functions are designed to save and restore the four interrupt mask registers in the MBOX ICU0 during suspend and resume operations. Due to the array being undersized, accessing all four registers results in out-of-bounds memory writes, classified under CWE-787. The vulnerability carries a CVSS v3.1 base score of 7.8.
A local attacker with low privileges can exploit this issue with low complexity and no user interaction required, as indicated by the vector AV:L/AC:L/PR:L/UI:N/S:U. Successful exploitation enables high-impact confidentiality, integrity, and availability violations (C:H/I:H/A:H), potentially allowing arbitrary code execution, data tampering, or system crashes during kernel suspend/resume cycles on affected th1520 hardware.
The provided kernel patch references detail the mitigation: commits at https://git.kernel.org/stable/c/2cd12c7fba59f30369e8647a2b726c7280903304 and https://git.kernel.org/stable/c/db049866943a38bf46a34fa120d526663339d7a5 correct the array size to properly accommodate all four interrupt mask registers, preventing the out-of-bounds access during suspend and resume. Security practitioners should ensure systems using the th1520 mailbox driver apply these stable kernel updates promptly.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5265
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: mailbox: th1520: Fix memory corruption due to incorrect array size The functions th1520_mbox_suspend_noirq and th1520_mbox_resume_noirq are intended to save and restore the interrupt mask registers in the MBOX ICU0. However,…
more
the array used to store these registers was incorrectly sized, leading to memory corruption when accessing all four registers. This commit corrects the array size to accommodate all four interrupt mask registers, preventing memory corruption during suspend and resume operations.
- 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 evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
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-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 in development and acceptance can detect and prevent out-of-bounds write defects.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.