Look up another CVE · open CVE-2026-53386 in the interactive tracker
CVE-2026-53386
iio: adc: ti-ads1298: add bounds check to pga_settings 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-53386 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
ads1298_pga_settings has 7 elements but ADS1298_MASK_CH_PGA can yield values 0-7. If it yields a value >= 7, this causes an out-of-bounds array access. Add a bounds check and return -EINVAL if the index is out of range. Note that the remaining value b111 is reserved so should not be seen in a correctly functioning system.
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/adc/ti-ads1298.c
- What this is
- IIO SUBSYSTEM AND DRIVERSMAINTAINERS section matched on drivers/iio/ · linux-iio@vger.kernel.org · Maintained
Check it on the machine
grep -wE 'CONFIG_IIO|CONFIG_TI_ADS1298' /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_TI_ADS1298
- 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.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 2.7% 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.9 | 6.12.95 | d5793975fc3b |
| 6.9 | 6.18.37 | d08d82d83ed4 |
| 6.9 | 7.0.14 | abe0854e356b |
| 6.9 | 7.1.2 | abd776ded3e2 |
| 6.9 | 7.2 | 95e8a48d7a85 |
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 via local IIO sysfs reads of the channel scale attribute (e.g. /sys/bus/iio/devices/iio:deviceN/in_voltageX_scale), which flows through read(2) into ads1298_get_scale(); this is not reachable over any network protocol.
- AC:LAttack complexity, low
- Once the CHnSET register contains reserved PGA encoding 111 (index 7), reading the scale attribute deterministically triggers the out-of-bounds access; a privileged attacker can reliably prime this state via debugfs direct_reg_access writes to CHnSET before the sysfs read.
- PR:LPrivileges required, low
- The IIO scale sysfs attributes are world-readable (mode 0444), so any unprivileged local user can invoke ads1298_get_scale without elevated capabilities; no user namespace or real-root capability is required to reach the vulnerable code path.
- UI:NUser interaction, none
- Exploitation requires only the attacker's own read of a sysfs attribute or debugfs register write; no action by a separate victim user is needed.
- S:UScope, unchanged
- The out-of-bounds read and any resulting kernel fault occur entirely within kernel space on the same host; there is no crossing of VM, container, or IOMMU security boundaries.
- C:HConfidentiality impact, high
- The bug is a one-byte out-of-bounds read past the end of the static ads1298_pga_settings array in kernel memory, leaking adjacent .rodata contents into kernel arithmetic used to compute the scale value.
- I:HIntegrity impact, high
- The out-of-bounds byte is consumed as the PGA gain divisor in kernel arithmetic, corrupting the computed scale and potentially causing a division-by-zero if the leaked value is zero, affecting kernel execution integrity.
- A:HAvailability impact, high
- If the out-of-bounds read yields a zero gain value, the subsequent integer division in ads1298_get_scale causes a kernel divide-by-zero fault; any resulting kernel oops or panic constitutes total loss of availability.