rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read
authorOleksij Rempel <o.rempel@pengutronix.de>
Wed, 18 Dec 2024 19:34:58 +0000 (20:34 +0100)
committerAlexandre Belloni <alexandre.belloni@bootlin.com>
Sun, 12 Jan 2025 23:26:54 +0000 (00:26 +0100)
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.

Fixes: fadfd092ee91 ("rtc: pcf85063: add nvram support")
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Link: https://lore.kernel.org/r/20241218-rtc-pcf85063-stack-corruption-v1-1-12fd0ee0f046@pengutronix.de
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
drivers/rtc/rtc-pcf85063.c

index fdbc07f14036aff0399c15adf71d89a30fe7e2cb..905986c616559b87826d1102dbc25614f7dcbcbb 100644 (file)
@@ -322,7 +322,16 @@ static const struct rtc_class_ops pcf85063_rtc_ops = {
 static int pcf85063_nvmem_read(void *priv, unsigned int offset,
                               void *val, size_t bytes)
 {
-       return regmap_read(priv, PCF85063_REG_RAM, val);
+       unsigned int tmp;
+       int ret;
+
+       ret = regmap_read(priv, PCF85063_REG_RAM, &tmp);
+       if (ret < 0)
+               return ret;
+
+       *(u8 *)val = tmp;
+
+       return 0;
 }
 
 static int pcf85063_nvmem_write(void *priv, unsigned int offset,