* [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows
@ 2026-07-28 10:17 Thomas Weißschuh
2026-07-28 10:24 ` sashiko-bot
2026-07-28 15:02 ` Guenter Roeck
0 siblings, 2 replies; 3+ messages in thread
From: Thomas Weißschuh @ 2026-07-28 10:17 UTC (permalink / raw)
To: Guenter Roeck, Benson Leung
Cc: Guenter Roeck, chrome-platform, linux-hwmon, linux-kernel,
Thomas Weißschuh
The calculations converting between the different temperature units can
overflow on 32-bit systems, resulting in incorrect data.
Detect these overflows and handle them.
The code is written in a way that there is a single conversion function
and the compiler can recognize when overflows are impossible (on 64-bit
and in cros_ec_hwmon_temp_to_millicelsius()). If the compiler detects
this, it will optimize away the overflow checks.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Changes in v2:
- Drop already applied patch 1.
- Also handle overflow of u32 -> long.
- Clarify commit message wrt compiler optimizations.
- Use __always_inline over __flatten to allow the compiler to optimize
away more unnecessary overflow checks.
- Link to v1: https://patch.msgid.link/20260630-cros_ec-hwmon-overflow-v1-0-3d2ecd3eb0f2@weissschuh.net
---
drivers/hwmon/cros_ec_hwmon.c | 31 ++++++++++++++++++++++++++-----
1 file changed, 26 insertions(+), 5 deletions(-)
diff --git a/drivers/hwmon/cros_ec_hwmon.c b/drivers/hwmon/cros_ec_hwmon.c
index 1337b646e022..004a8180b665 100644
--- a/drivers/hwmon/cros_ec_hwmon.c
+++ b/drivers/hwmon/cros_ec_hwmon.c
@@ -5,11 +5,13 @@
* Copyright (C) 2024 Thomas Weißschuh <linux@weissschuh.net>
*/
+#include <linux/build_bug.h>
#include <linux/cleanup.h>
#include <linux/device.h>
#include <linux/hwmon.h>
#include <linux/math.h>
#include <linux/module.h>
+#include <linux/overflow.h>
#include <linux/platform_device.h>
#include <linux/platform_data/cros_ec_commands.h>
#include <linux/platform_data/cros_ec_proto.h>
@@ -151,14 +153,28 @@ static bool cros_ec_hwmon_is_error_temp(u8 temp)
/* This differs slightly from the variant in units.h to avoid rounding inconsistencies. */
#define CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS (-273000)
-static long cros_ec_hwmon_kelvin_to_millicelsius(long t)
+static __always_inline bool cros_ec_hwmon_kelvin_to_millicelsius_overflow(long t, long *ret)
{
- return t * MILLIDEGREE_PER_DEGREE + CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS;
+ if (check_mul_overflow(t, MILLIDEGREE_PER_DEGREE, ret))
+ return true;
+
+ if (check_add_overflow(*ret, CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS, ret))
+ return true;
+
+ return false;
}
static long cros_ec_hwmon_temp_to_millicelsius(u8 temp)
{
- return cros_ec_hwmon_kelvin_to_millicelsius((((long)temp) + EC_TEMP_SENSOR_OFFSET));
+ long ret;
+
+ if (check_add_overflow(temp, EC_TEMP_SENSOR_OFFSET, &ret))
+ BUILD_BUG();
+
+ if (cros_ec_hwmon_kelvin_to_millicelsius_overflow(ret, &ret))
+ BUILD_BUG();
+
+ return ret;
}
static bool cros_ec_hwmon_attr_is_temp_threshold(u32 attr)
@@ -236,8 +252,13 @@ static int cros_ec_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
ret = cros_ec_hwmon_read_temp_threshold(priv->cros_ec, channel,
cros_ec_hwmon_attr_to_thres(attr),
&threshold);
- if (ret == 0)
- *val = cros_ec_hwmon_kelvin_to_millicelsius(threshold);
+ if (ret == 0) {
+ if (overflows_type(threshold, long))
+ *val = LONG_MAX;
+
+ if (cros_ec_hwmon_kelvin_to_millicelsius_overflow(threshold, val))
+ *val = LONG_MAX;
+ }
}
}
---
base-commit: 0109905cfdf4b64da014596f31c2ee5029ef0870
change-id: 20260630-cros_ec-hwmon-overflow-0381c8509df3
Best regards,
--
Thomas Weißschuh <linux@weissschuh.net>
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows
2026-07-28 10:17 [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows Thomas Weißschuh
@ 2026-07-28 10:24 ` sashiko-bot
2026-07-28 15:02 ` Guenter Roeck
1 sibling, 0 replies; 3+ messages in thread
From: sashiko-bot @ 2026-07-28 10:24 UTC (permalink / raw)
To: Thomas Weißschuh; +Cc: linux-hwmon
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing `else` statement causes clamped threshold values to be incorrectly overwritten by the fallback calculation on 32-bit systems.
--
--- Patch [1]: [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows ---
commit 89530e9a6ba047e5c308ed9d02243a168afc676c
Author: Thomas Weißschuh <linux@weissschuh.net>
hwmon: (cros_ec) Handle temperature conversion overflows
This commit detects potential arithmetic overflows when converting between
different temperature units on 32-bit systems and aims to clamp the returned
values to avoid reporting incorrect data.
> diff --git a/drivers/hwmon/cros_ec_hwmon.c b/drivers/hwmon/cros_ec_hwmon.c
> index 1337b646e0228..004a8180b665e 100644
> --- a/drivers/hwmon/cros_ec_hwmon.c
> +++ b/drivers/hwmon/cros_ec_hwmon.c
[ ... ]
> @@ -236,8 +252,13 @@ static int cros_ec_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
> ret = cros_ec_hwmon_read_temp_threshold(priv->cros_ec, channel,
> cros_ec_hwmon_attr_to_thres(attr),
> &threshold);
> - if (ret == 0)
> - *val = cros_ec_hwmon_kelvin_to_millicelsius(threshold);
> + if (ret == 0) {
> + if (overflows_type(threshold, long))
> + *val = LONG_MAX;
> +
> + if (cros_ec_hwmon_kelvin_to_millicelsius_overflow(threshold, val))
> + *val = LONG_MAX;
[Severity: High]
Does the lack of an else statement here cause the clamped LONG_MAX value to
be overwritten?
If the threshold is a large u32 value (e.g., 0xFFFFFFFF) on a 32-bit system,
overflows_type() returns true and sets *val to LONG_MAX. However, because
there is no else clause before the next check,
cros_ec_hwmon_kelvin_to_millicelsius_overflow() is unconditionally evaluated.
Since threshold is implicitly cast to long when passed into the function, the
large u32 value can become a small negative number (like -1) on 32-bit
architectures. The subsequent arithmetic inside the function would not
overflow, and the out-parameter assignment overwrites the LONG_MAX in *val
with an incorrect negative value (such as -274000).
> + }
> }
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728-cros_ec-hwmon-overflow-v2-1-d24e24d0792b@weissschuh.net?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows
2026-07-28 10:17 [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows Thomas Weißschuh
2026-07-28 10:24 ` sashiko-bot
@ 2026-07-28 15:02 ` Guenter Roeck
1 sibling, 0 replies; 3+ messages in thread
From: Guenter Roeck @ 2026-07-28 15:02 UTC (permalink / raw)
To: Thomas Weißschuh, Benson Leung
Cc: Guenter Roeck, chrome-platform, linux-hwmon, linux-kernel
On 7/28/26 03:17, Thomas Weißschuh wrote:
> The calculations converting between the different temperature units can
> overflow on 32-bit systems, resulting in incorrect data.
>
> Detect these overflows and handle them.
>
> The code is written in a way that there is a single conversion function
> and the compiler can recognize when overflows are impossible (on 64-bit
> and in cros_ec_hwmon_temp_to_millicelsius()). If the compiler detects
> this, it will optimize away the overflow checks.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Changes in v2:
> - Drop already applied patch 1.
> - Also handle overflow of u32 -> long.
> - Clarify commit message wrt compiler optimizations.
> - Use __always_inline over __flatten to allow the compiler to optimize
> away more unnecessary overflow checks.
> - Link to v1: https://patch.msgid.link/20260630-cros_ec-hwmon-overflow-v1-0-3d2ecd3eb0f2@weissschuh.net
> ---
> drivers/hwmon/cros_ec_hwmon.c | 31 ++++++++++++++++++++++++++-----
> 1 file changed, 26 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/hwmon/cros_ec_hwmon.c b/drivers/hwmon/cros_ec_hwmon.c
> index 1337b646e022..004a8180b665 100644
> --- a/drivers/hwmon/cros_ec_hwmon.c
> +++ b/drivers/hwmon/cros_ec_hwmon.c
> @@ -5,11 +5,13 @@
> * Copyright (C) 2024 Thomas Weißschuh <linux@weissschuh.net>
> */
>
> +#include <linux/build_bug.h>
> #include <linux/cleanup.h>
> #include <linux/device.h>
> #include <linux/hwmon.h>
> #include <linux/math.h>
> #include <linux/module.h>
> +#include <linux/overflow.h>
> #include <linux/platform_device.h>
> #include <linux/platform_data/cros_ec_commands.h>
> #include <linux/platform_data/cros_ec_proto.h>
> @@ -151,14 +153,28 @@ static bool cros_ec_hwmon_is_error_temp(u8 temp)
> /* This differs slightly from the variant in units.h to avoid rounding inconsistencies. */
> #define CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS (-273000)
>
> -static long cros_ec_hwmon_kelvin_to_millicelsius(long t)
> +static __always_inline bool cros_ec_hwmon_kelvin_to_millicelsius_overflow(long t, long *ret)
> {
> - return t * MILLIDEGREE_PER_DEGREE + CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS;
> + if (check_mul_overflow(t, MILLIDEGREE_PER_DEGREE, ret))
> + return true;
> +
> + if (check_add_overflow(*ret, CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS, ret))
> + return true;
> +
> + return false;
return check_add_overflow(*ret, CROS_EC_HWMON_ABSOLUTE_ZERO_MILLICELSIUS, ret);
> }
>
> static long cros_ec_hwmon_temp_to_millicelsius(u8 temp)
The maximum value of "temp" is 255.
> {
> - return cros_ec_hwmon_kelvin_to_millicelsius((((long)temp) + EC_TEMP_SENSOR_OFFSET));
255 + 200 = 455.
455 * 1000 = 455000 (not even counting the conversion from kelvin to C).
How could this ever overflow ?
> + long ret;
> +
> + if (check_add_overflow(temp, EC_TEMP_SENSOR_OFFSET, &ret))
> + BUILD_BUG();
> +
> + if (cros_ec_hwmon_kelvin_to_millicelsius_overflow(ret, &ret))
> + BUILD_BUG();
> +
> + return ret;
> }
>
> static bool cros_ec_hwmon_attr_is_temp_threshold(u32 attr)
> @@ -236,8 +252,13 @@ static int cros_ec_hwmon_read(struct device *dev, enum hwmon_sensor_types type,
> ret = cros_ec_hwmon_read_temp_threshold(priv->cros_ec, channel,
> cros_ec_hwmon_attr_to_thres(attr),
> &threshold);
> - if (ret == 0)
> - *val = cros_ec_hwmon_kelvin_to_millicelsius(threshold);
> + if (ret == 0) {
> + if (overflows_type(threshold, long))
> + *val = LONG_MAX;
> +
> + if (cros_ec_hwmon_kelvin_to_millicelsius_overflow(threshold, val))
> + *val = LONG_MAX;
> + }
I agree with Sashiko - it does not make sense to call cros_ec_hwmon_kelvin_to_millicelsius_overflow()
if it is already known that threshold overflowed.
Personally I think this is way too complicated. An overflowing temperature above 255 degrees C
does not make any sense, and returning LONG_MAX as temperature seems a bit odd.
I would just have checked for some reasonable limit, such as
if (threshold > 255 + 273)
*val = 255000;
else
*val = cros_ec_hwmon_kelvin_to_millicelsius(threshold);
If it does make sense to return LONG_MAX as temperature for some reason, that should
be explained.
Thanks,
Guenter
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-07-28 15:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-28 10:17 [PATCH v2] hwmon: (cros_ec) Handle temperature conversion overflows Thomas Weißschuh
2026-07-28 10:24 ` sashiko-bot
2026-07-28 15:02 ` Guenter Roeck
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.