* [PATCH AUTOSEL 5.15 66/82] iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() [not found] <20211109221641.1233217-1-sashal@kernel.org> @ 2021-11-09 22:16 ` Sasha Levin 2021-11-12 17:33 ` Jonathan Cameron 0 siblings, 1 reply; 2+ messages in thread From: Sasha Levin @ 2021-11-09 22:16 UTC (permalink / raw) To: linux-kernel, stable Cc: Teng Qi, TOTE Robot, Lorenzo Bianconi, Jonathan Cameron, Sasha Levin, jic23, linux-iio From: Teng Qi <starmiku1207184332@gmail.com> [ Upstream commit 94be878c882d8d784ff44c639bf55f3b029f85af ] The length of hw->settings->odr_table is 2 and ref_sensor->id is an enum variable whose value is between 0 and 5. However, the value ST_LSM6DSX_ID_MAX (i.e. 5) is not caught properly in switch (sensor->id) { If ref_sensor->id is ST_LSM6DSX_ID_MAX, an array overflow will ocurrs in function st_lsm6dsx_check_odr(): odr_table = &sensor->hw->settings->odr_table[sensor->id]; and in function st_lsm6dsx_set_odr(): reg = &hw->settings->odr_table[ref_sensor->id].reg; To avoid this array overflow, handle ST_LSM6DSX_ID_GYRO explicitly and return -EINVAL for the default case. The enum value ST_LSM6DSX_ID_MAX is only present as an easy way to check the limit and as such is never used, however this is not locally obvious. Reported-by: TOTE Robot <oslab@tsinghua.edu.cn> Signed-off-by: Teng Qi <starmiku1207184332@gmail.com> Acked-by: Lorenzo Bianconi <lorenzo@kernel.org> Link: https://lore.kernel.org/r/20211011114003.976221-1-starmiku1207184332@gmail.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Signed-off-by: Sasha Levin <sashal@kernel.org> --- drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c index db45f1fc0b817..8dbf744c5651f 100644 --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c @@ -1279,6 +1279,8 @@ st_lsm6dsx_set_odr(struct st_lsm6dsx_sensor *sensor, u32 req_odr) int err; switch (sensor->id) { + case ST_LSM6DSX_ID_GYRO: + break; case ST_LSM6DSX_ID_EXT0: case ST_LSM6DSX_ID_EXT1: case ST_LSM6DSX_ID_EXT2: @@ -1304,8 +1306,8 @@ st_lsm6dsx_set_odr(struct st_lsm6dsx_sensor *sensor, u32 req_odr) } break; } - default: - break; + default: /* should never occur */ + return -EINVAL; } if (req_odr > 0) { -- 2.33.0 ^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH AUTOSEL 5.15 66/82] iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() 2021-11-09 22:16 ` [PATCH AUTOSEL 5.15 66/82] iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() Sasha Levin @ 2021-11-12 17:33 ` Jonathan Cameron 0 siblings, 0 replies; 2+ messages in thread From: Jonathan Cameron @ 2021-11-12 17:33 UTC (permalink / raw) To: Sasha Levin Cc: linux-kernel, stable, Teng Qi, TOTE Robot, Lorenzo Bianconi, Jonathan Cameron, linux-iio On Tue, 9 Nov 2021 17:16:24 -0500 Sasha Levin <sashal@kernel.org> wrote: > From: Teng Qi <starmiku1207184332@gmail.com> > > [ Upstream commit 94be878c882d8d784ff44c639bf55f3b029f85af ] > > The length of hw->settings->odr_table is 2 and ref_sensor->id is an enum > variable whose value is between 0 and 5. > However, the value ST_LSM6DSX_ID_MAX (i.e. 5) is not caught properly in > switch (sensor->id) { > > If ref_sensor->id is ST_LSM6DSX_ID_MAX, an array overflow will ocurrs in > function st_lsm6dsx_check_odr(): > odr_table = &sensor->hw->settings->odr_table[sensor->id]; > > and in function st_lsm6dsx_set_odr(): > reg = &hw->settings->odr_table[ref_sensor->id].reg; > > To avoid this array overflow, handle ST_LSM6DSX_ID_GYRO explicitly and > return -EINVAL for the default case. > > The enum value ST_LSM6DSX_ID_MAX is only present as an easy way to check > the limit and as such is never used, however this is not locally obvious. > > Reported-by: TOTE Robot <oslab@tsinghua.edu.cn> > Signed-off-by: Teng Qi <starmiku1207184332@gmail.com> > Acked-by: Lorenzo Bianconi <lorenzo@kernel.org> > Link: https://lore.kernel.org/r/20211011114003.976221-1-starmiku1207184332@gmail.com > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > Signed-off-by: Sasha Levin <sashal@kernel.org> This is really just noise for stable. There wasn't a bug here though the change is doing some hardening and improving local readability by saving anyone having to confirm it can't occur by looking at the enum values. I don't mind it going into stable though if others feel it's worthwhile. Jonathan > --- > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c > index db45f1fc0b817..8dbf744c5651f 100644 > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c > @@ -1279,6 +1279,8 @@ st_lsm6dsx_set_odr(struct st_lsm6dsx_sensor *sensor, u32 req_odr) > int err; > > switch (sensor->id) { > + case ST_LSM6DSX_ID_GYRO: > + break; > case ST_LSM6DSX_ID_EXT0: > case ST_LSM6DSX_ID_EXT1: > case ST_LSM6DSX_ID_EXT2: > @@ -1304,8 +1306,8 @@ st_lsm6dsx_set_odr(struct st_lsm6dsx_sensor *sensor, u32 req_odr) > } > break; > } > - default: > - break; > + default: /* should never occur */ > + return -EINVAL; > } > > if (req_odr > 0) { ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-11-12 17:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20211109221641.1233217-1-sashal@kernel.org>
2021-11-09 22:16 ` [PATCH AUTOSEL 5.15 66/82] iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() Sasha Levin
2021-11-12 17:33 ` Jonathan Cameron
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox