linux-kernel - Re: [PATCH] rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <173672442028.1487900.17913987088323810689.b4-ty@bootlin.com>
Date: Mon, 13 Jan 2025 00:27:09 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Ahmad Fatoum <a.fatoum@...gutronix.de>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
	linux-rtc@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel@...gutronix.de, Oleksij Rempel <o.rempel@...gutronix.de>
Subject: Re: [PATCH] rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM
 read

On Wed, 18 Dec 2024 20:34:58 +0100, Ahmad Fatoum wrote:
> The nvmem interface supports variable buffer sizes, while the regmap
> interface operates with fixed-size storage. If an nvmem client uses a
> buffer size less than 4 bytes, regmap_read will write out of bounds
> as it expects the buffer to point at an unsigned int.
> 
> Fix this by using an intermediary unsigned int to hold the value.
> 
> [...]

Applied, thanks!

[1/1] rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read
      https://git.kernel.org/abelloni/c/3ab8c5ed4f84

Best regards,

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com