CVE-2025-40114: iio: light: Add check for array bounds in veml6075_read_int_time_ms
In the Linux kernel, the following vulnerability has been resolved:
iio: light: Add check for array bounds in veml6075_read_int_time_ms
The array contains only 5 elements, but the index calculated by
veml6075_read_int_time_index can range from 0 to 7,
which could lead to out-of-bounds access. The check prevents this issue.
Coverity Issue
CID 1574309: (#1 of 1): Out-of-bounds read (OVERRUN)
overrun-local: Overrunning array veml6075_it_ms of 5 4-byte
elements at element index 7 (byte offset 31) using
index int_index (which evaluates to 7)
This is hardening against potentially broken hardware. Good to have
but not necessary to backport.
Security readout for executives and security teams
Plain-English summary
CVE-2025-40114 is a Linux kernel bounds-checking flaw in the VEML6075 light sensor driver. A calculated index can exceed a five-element array. The source describes this as hardening for potentially broken hardware and says it was not necessary to backport, which lowers business urgency for most environments.
Executive priority
Treat this as a targeted Linux kernel maintenance item, not an emergency internet-facing incident. Patch through normal kernel update channels, with higher priority for embedded, IoT, or workstation fleets that use light sensors. Escalate only if your environment depends on this driver or receives urgent vendor guidance.
Technical view
The flaw is CWE-129 in veml6075_read_int_time_ms: veml6075_read_int_time_index may return indexes 0 through 7, while veml6075_it_ms has five entries. The fix adds an array-bounds check. CVSS is 7.8 with local, low-complexity, low-privilege access and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Linux systems using or loading the VEML6075 IIO light sensor driver, especially where the relevant hardware is present or can return unexpected values. General servers without this device or driver are less likely exposed. The provided bundle does not identify specific distributions or appliances.
Exploitation context
No active exploitation is supported by the provided sources, and the CVE is not listed as KEV in the bundle. The CVSS vector requires local low-privilege access. The kernel description frames the issue as protection against potentially broken hardware, not a known remote attack path.
Researcher notes
The bundle provides the root cause and fix intent but not a detailed affected-version matrix, distribution status, or exploitability proof. The unusually high CVSS impact should be balanced against the local attack vector and the upstream note that the change is hardening for potentially broken hardware.
Mitigation direction
Check vendor kernel advisories for fixed packages containing the referenced stable commits.
Prioritize updates on Linux devices using VEML6075 light sensors or IIO sensor stacks.
Disable or avoid loading the VEML6075 driver where the hardware is not required.
Track distribution backports instead of assuming upstream version numbers map directly.
Validation and detection
Inventory kernels and determine whether the VEML6075 driver is built or loadable.
Check whether affected systems include VEML6075 hardware or related device-tree entries.
Compare installed kernel source or package changelog against the referenced stable commits.
Confirm no operational dependency exists before disabling the driver.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-129: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-129 · source CWE mapping
Improper Validation of Array Index
Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.