rtc: tps6594: Fix integer overflow on 32bit systems
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.136.13.26.14In the Linux kernel, the following vulnerability has been resolved:
rtc: tps6594: Fix integer overflow on 32bit systems
The problem is this multiply in tps6594_rtc_set_offset()
tmp = offset * TICKS_PER_HOUR;
The "tmp" variable is an s64 but "offset" is a long in the (-277774)-277774 range. On 32bit systems a long can hold numbers up to approximately two billion. The number of TICKS_PER_HOUR is really large, (32768 * 3600) or roughly a hundred million. When you start multiplying by a hundred million it doesn't take long to overflow the two billion mark.
Probably the safest way to fix this is to change the type of TICKS_PER_HOUR to long long because it's such a large number.
From the CVE record · Linux
On 32-bit systems, the tps6594 RTC driver's offset calculation can overflow when setting an RTC offset. Someone able to set the offset can trigger the overflow; the input does not specify any further impact or whether authentication is required.
Engineers running the Linux kernel on 32-bit systems with the tps6594 RTC driver should check their kernel version; affected versions are not specified.