From: Srinivas Kandagatla <srini@kernel.org>
To: "Pradhan, Sanman" <sanman.pradhan@hpe.com>,
Srinivas Kandagatla <srini@kernel.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Chunyan Zhang <zhang.lyra@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Freeman Liu <freeman.liu@unisoc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sanman Pradhan <psanman@juniper.net>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] nvmem: sprd: fix out-of-bounds read in sprd_efuse_read()
Date: Fri, 18 Sep 2026 22:56:40 +0100 [thread overview]
Message-ID: <25a17e9e-362d-4252-ac79-f78c1d98c119@kernel.org> (raw)
In-Reply-To: <20260904003815.462352-1-sanman.pradhan@hpe.com>
On 9/4/26 1:38 AM, Pradhan, Sanman wrote:
> Read and copy one block at a time, capping each copy to the bytes left
> in the block so it can never exceed sizeof(data), and account for an
> unaligned starting offset. The NVMEM core does not validate offset +
> bytes against the device size, so also reject ranges outside the normal
if it does not then fix is in nvmem core not in provider.
--srini
> eFuse area before issuing any MMIO read. Fixes: 096030e7f449 ("nvmem:
> sprd: Add Spreadtrum SoCs eFuse support") Cc:
> stable@vger.kernel.orgSigned-off-by: Sanman Pradhan
> <psanman@juniper.net>--- Compile-tested only (NVMEM_SPRD_EFUSE,
> ARCH_SPRD || COMPILE_TEST); no Spreadtrum eFuse hardware available for
> runtime testing.
prev parent reply other threads:[~2026-09-18 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 0:38 Pradhan, Sanman
2026-09-18 21:56 ` 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=25a17e9e-362d-4252-ac79-f78c1d98c119@kernel.org \
--to=srini@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=freeman.liu@unisoc.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=psanman@juniper.net \
--cc=sanman.pradhan@hpe.com \
--cc=stable@vger.kernel.org \
--cc=zhang.lyra@gmail.com \
/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®