[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aGBMDFLH7aJGFyQ2@shikoro>
Date: Sat, 28 Jun 2025 22:09:48 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Alex Guo <alexguo1023@...il.com>
Cc: conor.dooley@...rochip.com, daire.mcnamara@...rochip.com,
andi.shyti@...nel.org, linux-riscv@...ts.infradead.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: busses: Fix out-of-bounds bug in
mchp_corei2c_smbus_xfer
On Sun, Jun 15, 2025 at 07:49:19PM -0400, Alex Guo wrote:
> The data->block[0] variable comes from user. Without proper check,
> the variable may be very large to cause an out-of-bounds bug.
Okay, okay, instead of adding these limits to all these drivers, let me
start adding SMBus3 support to the kernel which allows for bigger block
sizes. I probably won't have time to export this to user space yet, but
let's at least make sure the kernel, and thus the drivers, won't suffer
from buffer overflows anymore.
Powered by blists - more mailing lists