linux-kernel - Re: [PATCH v1] gpio: fix potential out-of-bound write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <174713408244.11101.2931169841658120912.b4-ty@linaro.org>
Date: Tue, 13 May 2025 13:02:19 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: linux-kernel@...r.kernel.org,
	Markus Burri <markus.burri@...com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	linux-gpio@...r.kernel.org,
	Markus Burri <markus.burri@....ch>,
	kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v1] gpio: fix potential out-of-bound write

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Fri, 09 May 2025 17:04:59 +0200, Markus Burri wrote:
> Check that the input size does not exceed the buffer size.
> If a caller write more characters, count is truncated to the max available
> space in "simple_write_to_buffer".
> Write a zero termination afterwards.
> 
> 

I tweaked the subject line: should have been: "gpio: virtuser: ...".

Also: you sent it as v1 but it was in fact v2, please keep the series
numbering even when splitting patches out of a bigger one.

[1/1] gpio: fix potential out-of-bound write
      https://git.kernel.org/brgl/linux/c/7118be7c6072f40391923543fdd1563b8d56377c

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>