From: Jiale Yao <yaojiale02@163.com>
To: "Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rodrigo Alencar" <rodrigo.alencar@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Anshul Dalal" <anshulusr@gmail.com>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Herve Codina" <herve.codina@bootlin.com>,
"Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>,
"Shi Hao" <i.shihao.999@gmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Angel Iglesias" <ang.iglesiasg@gmail.com>,
linux@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Jiale Yao <yaojiale02@163.com>
Subject: [PATCH 0/7] iio: validate SPI match data before use
Date: Fri, 25 Sep 2026 21:17:29 +0800 [thread overview]
Message-ID: <20260925131738.2200612-1-yaojiale02@163.com> (raw)
SPI driver_override can bind a device without a matching entry in the
driver's ID tables. spi_get_device_match_data() then returns NULL.
These seven IIO drivers use that result without checking it, causing a
NULL pointer dereference during probe. Add the missing checks before
the match data is used.
Jiale Yao (7):
iio: amplifiers: ad8366: reject devices without match data
iio: dac: ad5755: validate SPI match data
iio: dac: mcp4821: reject devices without match data
iio: frequency: adf4377: reject devices without match data
iio: imu: adis16400: validate SPI match data
iio: potentiometer: x9250: reject devices without match data
iio: pressure: bmp280: validate SPI match data
drivers/iio/amplifiers/ad8366.c | 2 ++
drivers/iio/dac/ad5755.c | 3 +++
drivers/iio/dac/mcp4821.c | 7 +++++--
drivers/iio/frequency/adf4377.c | 3 +++
drivers/iio/imu/adis16400.c | 3 +++
drivers/iio/potentiometer/x9250.c | 7 ++++++-
drivers/iio/pressure/bmp280-spi.c | 2 ++
7 files changed, 24 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2026-09-25 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:17 Jiale Yao [this message]
2026-09-25 13:17 ` [PATCH 1/7] iio: amplifiers: ad8366: reject devices without match data Jiale Yao
2026-09-25 13:17 ` [PATCH 2/7] iio: dac: ad5755: validate SPI " Jiale Yao
2026-09-25 13:17 ` [PATCH 3/7] iio: dac: mcp4821: reject devices without " Jiale Yao
2026-09-25 13:17 ` [PATCH 4/7] iio: frequency: adf4377: " Jiale Yao
2026-09-25 13:17 ` [PATCH 5/7] iio: imu: adis16400: validate SPI " Jiale Yao
2026-09-25 13:17 ` [PATCH 6/7] iio: potentiometer: x9250: reject devices without " Jiale Yao
2026-09-25 13:17 ` [PATCH 7/7] iio: pressure: bmp280: validate SPI " Jiale Yao
2026-09-26 1:11 ` [PATCH 0/7] iio: validate SPI match data before use Jonathan Cameron
2026-09-26 6:13 ` Uwe Kleine-König (The Capable Hub)
2026-09-27 17:20 ` Jonathan Cameron
2026-09-28 8:14 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260925131738.2200612-1-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=ang.iglesiasg@gmail.com \
--cc=anshulusr@gmail.com \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=herve.codina@bootlin.com \
--cc=i.shihao.999@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=nuno.sa@analog.com \
--cc=rodrigo.alencar@analog.com \
--cc=u.kleine-koenig@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®