Look up another CVE · open CVE-2026-53387 in the interactive tracker
CVE-2026-53387
iio: light: veml6075: add bounds check to veml6075_it_ms index
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem drivers/iio. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-53387 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.95-1 | Update the kernel and reboot. Fixed in 6.12.95-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.14-1 | Update the kernel and reboot. Fixed in 7.0.14-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.14-1 | Update the kernel and reboot. Fixed in 7.0.14-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/iio/light/veml6075.c
- What this is
- VISHAY VEML6075 UVA AND UVB LIGHT SENSOR DRIVERMAINTAINERS section matched on drivers/iio/light/veml6075.c · Maintained
Check it on the machine
grep -wE 'CONFIG_IIO|CONFIG_VEML6075' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code in 3 releases. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sidn
- ?
- not established - no Makefile entry for the affected file
- n
- not enabled on any flavour - this release does not build the code
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_IIO, CONFIG_VEML6075
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-07-19 (3 months ago)source
- CVSS
- 7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/iio
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.8 | 6.12.95 | df9127a1d2d7 |
| 6.8 | 6.18.37 | 0a89002737ee |
| 6.8 | 7.0.14 | f75beebcd5bc |
| 6.8 | 7.1.2 | e545936e06f1 |
| 6.8 | 7.2 | 307dc4240bd4 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The vulnerable code is reached only via local sysfs reads of IIO channel attributes (e.g. in_intensity_uva_raw), which require filesystem access on the target system; there is no network-facing kernel entry point.
- AC:LAttack complexity, low
- An attacker with access to /dev/i2c-* can use I2C_SLAVE_FORCE and I2C_RDWR to program reserved IT values (5–7) into the sensor configuration register, then reliably trigger the out-of-bounds read with a normal sysfs read.
- PR:LPrivileges required, low
- Triggering the bug requires only reading world-readable (0444) IIO sysfs attributes, which is available to an unprivileged local user on typical embedded/Linux deployments where /sys is accessible.
- UI:NUser interaction, none
- Exploitation requires no action by a separate victim; the attacker directly issues the sysfs read that invokes the vulnerable measurement path.
- S:UScope, unchanged
- Impact is confined to kernel driver behavior on the local system; there is no crossing of security boundaries such as VM escape, sandbox escape, or IOMMU bypass.
- C:HConfidentiality impact, high
- The bug is an out-of-bounds read of kernel memory (up to 12 bytes past a static array in .rodata) when the integration-time index is 5, 6, or 7; per kernel scoring guidance, out-of-bounds reads are rated High unless strictly bounded, and the leaked value is not returned to userspace.
- I:NIntegrity impact, none
- The flaw is a read-only out-of-bounds array access; the out-of-bounds value is consumed only by msleep() and does not modify memory or enable arbitrary writes or code execution.
- A:HAvailability impact, high
- An out-of-bounds integration-time value fed into msleep() can produce a very long uninterruptible sleep while the driver mutex is held, blocking all concurrent sensor reads and causing a denial of service on embedded/IoT systems that depend on the UV sensor.