CVE-2025-40114: iio: light: Add check for array bounds in veml6075_read_int_time_ms
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 18a08b5632809faa671279b3cd27d5f96cc5a3f0, 7a40b52d4442178bee0cf1c36bc450ab951cef0f, 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692.
Low priority for now. Upgrade to Linux Linux 18a08b5632809faa671279b3cd27d5f96cc5a3f0, 7a40b52d4442178bee0cf1c36bc450ab951cef0f, 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-129
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.8affected
- 3b82f43238aecd73464aeacc9c73407079511533 and later · before 7a40b52d4442178bee0cf1c36bc450ab951cef0faffected · git
- 3b82f43238aecd73464aeacc9c73407079511533 and later · before 18a08b5632809faa671279b3cd27d5f96cc5a3f0affected · git
- 3b82f43238aecd73464aeacc9c73407079511533 and later · before 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692affected · git
- 3b82f43238aecd73464aeacc9c73407079511533 and later · before ee735aa33db16c1fb5ebccbaf84ad38f5583f3ccaffected · git
- before 6.8not affected · semver
- 6.12.23 and later · up to and including 6.12.*not affected · semver
- 6.13.11 and later · up to and including 6.13.*not affected · semver
- 6.14.2 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.8 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39930Apr 18, 2025 · ASoC: simple-card-utils: Don't use __free(device_node) at graph_util_parse_dai()22Monitor
- ← EarlierCVE-2025-40014Apr 18, 2025 · objtool, spi: amd: Fix out-of-bounds stack access in amd_set_spi_freq()31Monitor
- Later →CVE-2025-37785Apr 18, 2025 · ext4: fix OOB read when checking dotdot dir28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 18a08b5632809faa671279b3cd27d5f96cc5a3f0 | Vendor (CNA) |
| Linux Linux | 7a40b52d4442178bee0cf1c36bc450ab951cef0f | Vendor (CNA) |
| Linux Linux | 9c40a68b7f97fa487e6c7e67fcf4f846a1f96692 | Vendor (CNA) |
| Linux Linux | ee735aa33db16c1fb5ebccbaf84ad38f5583f3cc | Vendor (CNA) |
| debian:linux | 6.12.25-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-47548329 days apartethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()39Monitor
- CVE-2026-64018457 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access37Monitor
- CVE-2026-23246334 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration35Monitor
- CVE-2026-43110383 days apartwifi: brcmfmac: validate bsscfg indices in IF events35Monitor
- CVE-2026-43172383 days apartwifi: iwlwifi: fix 22000 series SMEM parsing35Monitor
- CVE-2025-400140 days apartobjtool, spi: amd: Fix out-of-bounds stack access in amd_set_spi_freq()31Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.