Look up another CVE · open CVE-2026-93038 in the interactive tracker
CVE-2026-93038
iio: dac: ad5686: missing NULL check on match data
Published 2026-09-17 (31 days 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-93038 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 | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | not affected | 7.2.11-1 | Nothing to do. forky never shipped the vulnerable code. |
| Debian unstablesid | not affected | 7.2.11-1 | Nothing to do. sid never shipped the vulnerable code. |
The vulnerability
What the bug is
Verify that chip_info pointer is not NULL. If a user binds the driver using driver_override via sysfs with a device name not present in the id_table or of_match_table, match data will be NULL.
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/dac/ad5686-spi.c
drivers/iio/dac/ad5696-i2c.c
- What this is
- ANALOG DEVICES INC IIO DRIVERSMAINTAINERS section matched on drivers/iio/*/ad* · linux@analog.com · Supported
- Kernel module
- ad5686_spi
Check it on the machine
grep -wE 'CONFIG_AD5686_SPI|CONFIG_IIO' /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.
lsmod | grep -w ad5686_spiPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_AD5686_SPI, CONFIG_IIO
- 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-09-17 (31 days ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.20%, higher than 8.9% 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 |
|---|---|---|
| 7.2 | 7.2.6 | cdaa9cb77eb6 |
| 7.2 | 7.3 | 572a00852635 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-93038, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.