From: cy_huang <u0084500@gmail.com>
To: lee@kernel.org, matthias.bgg@gmail.com
Cc: chiaen_wu@richtek.com, andy.shevchenko@gmail.com,
cy_huang@richtek.com, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] mfd: mt6370: Add the out-of-bound check to prevent the null pointer
Date: Fri, 21 Oct 2022 10:17:41 +0800 [thread overview]
Message-ID: <1666318661-11777-1-git-send-email-u0084500@gmail.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
This potential risk could happen at regmap_raw_read() or
regmap_raw_write() when accessing the over-bound register address.
For testing, I try to reproduce it with a testing attribute file.
Below's the issue trace log.
[41.314358] pc : i2c_smbus_xfer+0x58/0x120
[41.314371] lr : i2c_smbus_read_i2c_block_data+0x74/0xc0
[41.399677] Call trace:
[41.402153] i2c_smbus_xfer+0x58/0x120
[41.405956] i2c_smbus_read_i2c_block_data+0x74/0xc0
[41.410991] mt6370_regmap_read+0x40/0x60 [mt6370]
[41.415855] _regmap_raw_read+0xe4/0x278
[41.419834] regmap_raw_read+0xec/0x240
[41.423721] rg_bound_show+0xb0/0x120 [mt6370]
[41.428226] dev_attr_show+0x3c/0x80
[41.431851] sysfs_kf_seq_show+0xc4/0x150
[41.435916] kernfs_seq_show+0x48/0x60
[41.439718] seq_read_iter+0x11c/0x450
[41.443519] kernfs_fop_read_iter+0x124/0x1c0
[41.447937] vfs_read+0x1a8/0x288
[41.451296] ksys_read+0x74/0x100
[41.454654] __arm64_sys_read+0x24/0x30
[41.458541] invoke_syscall+0x54/0x118
[41.462344] el0_svc_common.constprop.4+0x94/0x128
[41.467202] do_el0_svc+0x3c/0xd0
[41.470562] el0_svc+0x20/0x60
[41.473658] el0t_64_sync_handler+0x94/0xb8
[41.477899] el0t_64_sync+0x15c/0x160
[41.481614] Code: 54000388 f9401262 aa1303e0 52800041 (f9400042)
[41.487793] ---[ end trace 0000000000000000 ]---
Fixes: b2adf788e603 ("mfd: mt6370: Add MediaTek MT6370 support")
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
---
Dear reviewers:
In v2, I refined the patch title and commit message.
If there's still something improper, please kindly correct me.
---
drivers/mfd/mt6370.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/mfd/mt6370.c b/drivers/mfd/mt6370.c
index cf19cce..acbf960 100644
--- a/drivers/mfd/mt6370.c
+++ b/drivers/mfd/mt6370.c
@@ -190,6 +190,9 @@ static int mt6370_regmap_read(void *context, const void *reg_buf,
bank_idx = u8_buf[0];
bank_addr = u8_buf[1];
+ if (bank_idx >= MT6370_MAX_I2C)
+ return -EINVAL;
+
ret = i2c_smbus_read_i2c_block_data(info->i2c[bank_idx], bank_addr,
val_size, val_buf);
if (ret < 0)
@@ -211,6 +214,9 @@ static int mt6370_regmap_write(void *context, const void *data, size_t count)
bank_idx = u8_buf[0];
bank_addr = u8_buf[1];
+ if (bank_idx >= MT6370_MAX_I2C)
+ return -EINVAL;
+
return i2c_smbus_write_i2c_block_data(info->i2c[bank_idx], bank_addr,
len, data + MT6370_MAX_ADDRLEN);
}
--
2.7.4
next reply other threads:[~2022-10-21 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 2:17 cy_huang [this message]
2022-10-21 8:33 ` [PATCH v2] mfd: mt6370: Add the out-of-bound check to prevent the null pointer Andy Shevchenko
2022-10-21 9:02 ` ChiYuan Huang
2022-10-21 9:13 ` Andy Shevchenko
2022-10-21 9:58 ` ChiYuan Huang
2022-10-21 10:35 ` Andy Shevchenko
2022-10-26 7:04 ` ChiYuan Huang
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=1666318661-11777-1-git-send-email-u0084500@gmail.com \
--to=u0084500@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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