# CVE-2025-40114: iio: light: Add check for array bounds in veml6075_read_int_time_ms

> A missing bounds check in the veml6075 light sensor driver could allow out-of-bounds reads, potentially causing a kernel crash or instability.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40114, DEBIAN-CVE-2025-40114, GHSA-425r-hmhf-r25x, ROOT-OS-UBUNTU-2404-CVE-2025-40114, UBUNTU-CVE-2025-40114

## What is CVE-2025-40114?

CVE-2025-40114 is a high-severity vulnerability in Linux kernel, published on 18 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2025-40114?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-40114?

Apply the vendor's patch.

## Is CVE-2025-40114 being exploited?

There is no known exploitation of CVE-2025-40114 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40114 and fix it if it is affected.

What it is: CVE-2025-40114 is a high-severity vulnerability in Linux kernel, published on 18 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40114 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40114/ (Markdown: https://insights.sbomify.com/CVE-2025-40114/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40114
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40114
- OSV: https://osv.dev/vulnerability/CVE-2025-40114

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40114/
Summaries are generated and may contain mistakes; the official description above is the record.