Metrics
Affected Vendors & Products
Fri, 07 Mar 2025 21:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Linux
Linux linux Kernel |
|
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
Vendors & Products |
Linux
Linux linux Kernel |
|
Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 06 Mar 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-190 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Fri, 28 Feb 2025 02:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Thu, 27 Feb 2025 02:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In 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. | |
Title | rtc: tps6594: Fix integer overflow on 32bit systems | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-02-27T02:07:01.598Z
Updated: 2025-03-24T15:37:18.874Z
Reserved: 2025-01-19T11:50:08.381Z
Link: CVE-2024-57953

No data.

Status : Analyzed
Published: 2025-02-27T02:15:10.393
Modified: 2025-03-07T20:44:17.993
Link: CVE-2024-57953
