From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master] rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read
Date: Fri, 20 Dec 2024 09:51:25 +0100 [thread overview]
Message-ID: <173468468571.3151844.6436759867454614595.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241217115253.3211836-1-a.fatoum@pengutronix.de>
On Tue, 17 Dec 2024 12:52:52 +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.pengutronix.de/cgit/barebox/commit/?id=e3de867716e9 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-12-20 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 11:52 Ahmad Fatoum
2024-12-20 8:51 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173468468571.3151844.6436759867454614595.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox