From: Dang Vu Duc Hien <dvdh12707@gmail.com>
To: marvin24@gmx.de, gregkh@linuxfoundation.org
Cc: ac100@lists.launchpad.net, linux-tegra@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
luquijeffrey@gmail.com, Dang Vu Duc Hien <dvdh12707@gmail.com>
Subject: [PATCH] staging: nvec: fix out-of-bounds string copies
Date: Thu, 30 Jul 2026 11:12:20 +0700 [thread overview]
Message-ID: <20260730041220.1064608-1-dvdh12707@gmail.com> (raw)
In-Reply-To: <CAObkL7P+PnkEBpav6AVEPTyjiWsoOEBobUT2hrR=fay23FyO6w@mail.gmail.com>
The function `nvec_power_bat_notifier()` assumes that `res->length` is
both >= 2 and within the battery info buffers.
Technically, `res->length` is provided by the embedded controller (EC)
and is unverified (ie. a malformed response). If `res->length` < 2, the
expression `res->length - 2` evaluates to a massive size_t value which
is passed to `memcpy()`, causing severe memory corruption. Conversely,
`res->length - 2` being larger than the buffer also causes an
out-of-bounds write.
Introduce helper function `nvec_bat_str_copy()` to safely handle these
string copies by:
1. Ensuring that it returns an error to the upper layer along with a
`dev_warn()` message when `res->length` < 2.
2. Ensuring that it provides toleration by copying as much as it can
along with a `dev_warn()` when `res->length - 2` is too big.
3. Guaranteeing a properly sized, null-terminated destination string if
the copy succeeds.
Signed-off-by: Dang Vu Duc Hien <dvdh12707@gmail.com>
---
Note: Coincidentally, I have been working on this exact issue earlier
and had this patch prepared just before Lucas Jeffrey submitted his RFC.
I am sending it here to answer his protocol validation question with code.
---
drivers/staging/nvec/nvec_power.c | 41 ++++++++++++++++++++++++++-----
1 file changed, 35 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/nvec/nvec_power.c b/drivers/staging/nvec/nvec_power.c
index c514d51a9e57..12699515356d 100644
--- a/drivers/staging/nvec/nvec_power.c
+++ b/drivers/staging/nvec/nvec_power.c
@@ -117,6 +117,32 @@ static void get_bat_mfg_data(struct nvec_power *power)
}
}
+static int nvec_bat_str_copy(struct nvec_power *power,
+ struct bat_response *res, char *dst,
+ unsigned int dst_size, const char *prop_name)
+{
+ unsigned int len;
+
+ if (res->length < 2) {
+ dev_warn(power->nvec->dev,
+ "battery %s response length too short (%u)\n",
+ prop_name, res->length);
+ return -EINVAL;
+ }
+
+ len = res->length - 2;
+ if (len >= dst_size) {
+ dev_warn(power->nvec->dev,
+ "battery %s string too long (%u)\n",
+ prop_name, len);
+ len = dst_size - 1;
+ }
+
+ memcpy(dst, &res->plc, len);
+ dst[len] = '\0';
+ return 0;
+}
+
static int nvec_power_bat_notifier(struct notifier_block *nb,
unsigned long event_type, void *data)
{
@@ -193,16 +219,19 @@ static int nvec_power_bat_notifier(struct notifier_block *nb,
power->bat_temperature = res->plu - 2732;
break;
case MANUFACTURER:
- memcpy(power->bat_manu, &res->plc, res->length - 2);
- power->bat_manu[res->length - 2] = '\0';
+ if (nvec_bat_str_copy(power, res, power->bat_manu,
+ sizeof(power->bat_manu), "manufacturer") < 0)
+ break;
break;
case MODEL:
- memcpy(power->bat_model, &res->plc, res->length - 2);
- power->bat_model[res->length - 2] = '\0';
+ if (nvec_bat_str_copy(power, res, power->bat_model,
+ sizeof(power->bat_model), "model") < 0)
+ break;
break;
case TYPE:
- memcpy(power->bat_type, &res->plc, res->length - 2);
- power->bat_type[res->length - 2] = '\0';
+ if (nvec_bat_str_copy(power, res, power->bat_type,
+ sizeof(power->bat_type), "type") < 0)
+ break;
/*
* This differs a little from the spec fill in more if you find
* some.
--
2.55.0
next parent reply other threads:[~2026-07-30 4:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAObkL7P+PnkEBpav6AVEPTyjiWsoOEBobUT2hrR=fay23FyO6w@mail.gmail.com>
2026-07-30 4:12 ` Dang Vu Duc Hien [this message]
2026-07-30 7:35 ` Greg KH
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=20260730041220.1064608-1-dvdh12707@gmail.com \
--to=dvdh12707@gmail.com \
--cc=ac100@lists.launchpad.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=luquijeffrey@gmail.com \
--cc=marvin24@gmx.de \
/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®