LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57953: rtc: tps6594: Fix integer overflow on 32bit systems

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-57953 is a Linux kernel flaw in the TPS6594 real-time clock driver. On 32-bit systems, a large offset calculation can overflow and affect availability. The public data rates it medium severity, requiring local access and low privileges, with no evidence provided of active exploitation.

Executive priority

Treat as a targeted availability risk, not a broad internet emergency. Prioritize affected 32-bit Linux embedded or operational systems where downtime matters, and fold remediation into the next kernel maintenance cycle unless local-user abuse risk is elevated.

Technical view

The issue is CWE-190 integer overflow in tps6594_rtc_set_offset(). offset is a long, while TICKS_PER_HOUR is large; multiplication can overflow before assignment to s64 on 32-bit systems. CVSS 3.1 is 5.5: local, low complexity, low privileges, no user interaction, high availability impact.

Likely exposure

Exposure appears limited to Linux systems using the TPS6594 RTC driver on 32-bit builds, especially kernels in the affected ranges named by the CVE data. General 64-bit Linux fleets or systems without this driver are less likely exposed, but distro backport status must be checked.

Exploitation context

The source bundle does not identify public exploitation, weaponized details, or CISA KEV listing. Attack prerequisites are local access and low privileges. The described impact is availability only, not confidentiality or integrity compromise.

Researcher notes

The evidence supports an integer-overflow availability issue in Linux rtc:tps6594. Exact affected/fixed distro versions are not fully specified in the bundle; validate by commit presence or vendor advisories. Do not assume exposure without 32-bit architecture and relevant driver usage.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes and exact package versions.
  • Prioritize 32-bit systems using the TPS6594 RTC driver.
  • Reduce unnecessary local account access on affected embedded or operational systems.
  • If patching is delayed, follow vendor guidance for driver-specific mitigation.

Validation and detection

  • Inventory systems running 32-bit Linux kernels.
  • Confirm whether the TPS6594 RTC driver is built, loaded, or used.
  • Compare kernel source or package changelog against the referenced stable commits.
  • Map deployed distro kernel packages to vendor-fixed versions.
  • Track remediation status separately for embedded devices and custom kernels.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-57953 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-57953Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9f67c1e63976d3403f0b250b03ffe959c890f9db, 9f67c1e63976d3403f0b250b03ffe959c890f9db, 9f67c1e63976d3403f0b250b03ffe959c890f9dbunaffected
LinuxLinux6.8, 0, 6.12.13, 6.13.2, 6.14affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.