CVE-2024-57910
Linux Kernel 5.4.132 – 5.4.290
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HSummary
CVE-2024-57910 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 12th 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-57910 is an information disclosure vulnerability in the Linux kernel's Industrial I/O (IIO) subsystem, specifically the vcnl4035 light sensor driver. The issue arises in the triggered buffer handling where a local 'buffer' array, used to push data to userspace, fails to fully initialize its u16 data element aligned to 8 bytes. Even after writing an integer value via regmap_read(), at least 4 bytes remain uninitialized, potentially leaking kernel stack memory to userspace. The vulnerability is classified under CWE-908 (Use of Uninitialized Resource) with a CVSS v3.1 base score of 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H).
A local attacker with low privileges can exploit this vulnerability by triggering the buffer read operation in the vcnl4035 driver. Successful exploitation allows the attacker to read uninitialized kernel memory, achieving high confidentiality impact through information disclosure. The CVSS vector also indicates high availability impact, though the root cause is tied to the uninitialized data leak.
Mitigation involves applying the upstream kernel patches referenced in the stable commit logs, such as those at https://git.kernel.org/stable/c/13e56229fc81051a42731046e200493c4a7c28ff and similar URLs, which initialize the buffer array to zero before use. Security practitioners should update affected Linux kernels to incorporate these fixes.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53813
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: iio: light: vcnl4035: fix information leak in triggered buffer The 'buffer' local array is used to push data to userspace from a triggered buffer, but it does not set an…
more
initial value for the single data element, which is an u16 aligned to 8 bytes. That leaves at least 4 bytes uninitialized even after writing an integer value with regmap_read(). Initialize the array to zero before using it to avoid pushing uninitialized information to userspace.
- 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 static analysis) can find uses of uninitialized resources after they are coded.
Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.
Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.
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 activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.
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 uninitialized resource usage through dynamic analysis and fuzzing.
Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.
Application security requirements can specify mandatory initialization of variables and resources before use.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.