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: <171682150857.156397.13252252218897228306.b4-ty@linaro.org>
Date: Mon, 27 May 2024 16:51:51 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Hagar Hemdan <hagarhem@...zon.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Norbert Manthey <nmanthey@...zon.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] gpio: prevent potential speculation leaks in gpio_device_get_desc()

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


On Thu, 23 May 2024 08:53:32 +0000, Hagar Hemdan wrote:
> Userspace may trigger a speculative read of an address outside the gpio
> descriptor array.
> Users can do that by calling gpio_ioctl() with an offset out of range.
> Offset is copied from user and then used as an array index to get
> the gpio descriptor without sanitization in gpio_device_get_desc().
> 
> This change ensures that the offset is sanitized by using
> array_index_nospec() to mitigate any possibility of speculative
> information leaks.
> 
> [...]

Applied, thanks!

[1/1] gpio: prevent potential speculation leaks in gpio_device_get_desc()
      commit: d795848ecce24a75dfd46481aee066ae6fe39775

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ