From: Srinivas Kandagatla <srini@kernel.org>
To: Janne Grunau <j@jannau.net>,
Srinivas Kandagatla <srini@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: core: Fix OOB read for bit offsets of more than one byte
Date: Sun, 20 Sep 2026 17:19:51 +0100 [thread overview]
Message-ID: <0a778130-1e88-4dbc-b3c5-346195b54701@kernel.org> (raw)
In-Reply-To: <20250901-nvmem-read-oob-bit-offset-v1-1-b610e18cdd3c@jannau.net>
On 9/1/25 8:29 AM, Janne Grunau wrote:
> When the bit offset is BITS_PER_BYTE or larger the read position is
> advanced by `bytes_offset`. This is not taken into account in the
> per-byte read loop which still reads `cell->bytes` resulting in an out of
> bounds read of `bytes_offset` bytes. The information read OOB does not
> leak directly as the erroneously read bits are cleared.
>
> Detected by KASAN while looking for a use-after-free in simplefb.c.
>
> Fixes: 7a06ef7510779 ("nvmem: core: fix bit offsets of more than one byte")
12 chars sha pl
Missing CC Stable.
> Signed-off-by: Janne Grunau <j@jannau.net>
> ---
> drivers/nvmem/core.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index 387c88c55259541446901f0e539bbb0dd8c4c3de..19be16943ee66e845860192b8f008539873f6f7f 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -1618,12 +1618,14 @@ static void nvmem_shift_read_buffer_in_place(struct nvmem_cell_entry *cell, void
> *p = *b++ >> bit_offset;
>
> /* setup rest of the bytes if any */
> - for (i = 1; i < cell->bytes; i++) {
> + for (i = 1; i < (cell->bytes - bytes_offset); i++) {
> /* Get bits from next byte and shift them towards msb */
> *p++ |= *b << (BITS_PER_BYTE - bit_offset);
>
> *p = *b++ >> bit_offset;
> }
> + /* point to end of the buffer unused bits will be cleared */
> + p = buf + cell->bytes - 1;
> } else if (p != b) {
> memmove(p, b, cell->bytes - bytes_offset);
> p += cell->bytes - 1;
>
> ---
> base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
> change-id: 20250901-nvmem-read-oob-bit-offset-dc1c2f39af6c
>
> Best regards,
prev parent reply other threads:[~2026-09-20 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 7:29 Janne Grunau
2025-09-01 7:40 ` Greg Kroah-Hartman
2026-09-19 18:56 ` Dmitry Sinyavin
2026-09-20 16:33 ` Janne Grunau
2026-09-20 16:19 ` Srinivas Kandagatla [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=0a778130-1e88-4dbc-b3c5-346195b54701@kernel.org \
--to=srini@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=j@jannau.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.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
all inboxes | Powered by JetHome®