linux-kernel - Re: [PATCH v3] eeprom: at24: fix memory corruption race condition

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: <171386010055.10921.7297413066417044638.b4-ty@linaro.org>
Date: Tue, 23 Apr 2024 10:15:18 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Bartosz Golaszewski <brgl@...ev.pl>,
	Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Daniel Okazaki <dtokazaki@...gle.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	kernel-team@...roid.com,
	linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] eeprom: at24: fix memory corruption race condition

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


On Mon, 22 Apr 2024 17:43:36 +0000, Daniel Okazaki wrote:
> If the eeprom is not accessible, an nvmem device will be registered, the
> read will fail, and the device will be torn down. If another driver
> accesses the nvmem device after the teardown, it will reference
> invalid memory.
> 
> Move the failure point before registering the nvmem device.
> 
> [...]

Applied, thanks!

[1/1] eeprom: at24: fix memory corruption race condition
      commit: f42c97027fb75776e2e9358d16bf4a99aeb04cf2

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