Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.1; sources differ by 0.0.
A fix is available — apply it.
In the Linux kernel, the following vulnerability has been resolved:
iio: light: veml6075: add bounds check to veml6075_it_ms index
veml6075_it_ms has 5 elements but VEML6075_CONF_IT can yield values 0-7. If it returns a value >= 5, this causes an out-of-bounds array access. Add a bounds check and return -EINVAL if the index is out of range.
The problem values are reserved so should never be read from the register. Hence this is hardening against fault device, missprogramming or bus corruption.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
July 19, 2026
August 17, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | linux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute | 2026-09-07 | ubuntu |
| ubuntu | linux-tools-oem-7.0 (7.0.0-1013.13) @ resolute | 2026-09-07 | ubuntu |
| ubuntu | linux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble | 2026-09-07 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions) | 6.12.95-1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions) | 7.0.14-1 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 171 total refreshes for this CVE.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53387
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.