CVE-2024-57953: rtc: tps6594: Fix integer overflow on 32bit systems
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 09c4a610153286cef54d4f0c85398f4e32fc227e, 5127f3cbfc78a7b301b86328247230bec47e0bb3, 53b0c7b15accb18d15d95c7fe68f61630ebfd1ca.
Low priority for now. Upgrade to Linux Linux 09c4a610153286cef54d4f0c85398f4e32fc227e, 5127f3cbfc78a7b301b86328247230bec47e0bb3, 53b0c7b15accb18d15d95c7fe68f61630ebfd1ca or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-190
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.8affected
- 9f67c1e63976d3403f0b250b03ffe959c890f9db and later · before 5127f3cbfc78a7b301b86328247230bec47e0bb3affected · git
- 9f67c1e63976d3403f0b250b03ffe959c890f9db and later · before 53b0c7b15accb18d15d95c7fe68f61630ebfd1caaffected · git
- 9f67c1e63976d3403f0b250b03ffe959c890f9db and later · before 09c4a610153286cef54d4f0c85398f4e32fc227eaffected · git
- before 6.8not affected · semver
- 6.12.13 and later · up to and including 6.12.*not affected · semver
- 6.13.2 and later · up to and including 6.13.*not affected · semver
- 6.14 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.8 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.13-1 | 6.12.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49699Feb 26, 2025 · filemap: Handle sibling entries in filemap_get_read_batch()22Monitor
- ← EarlierCVE-2022-49732Feb 26, 2025 · sock: redo the psock vs ULP protection check22Monitor
- Later →CVE-2024-57978Feb 26, 2025 · media: imx-jpeg: Fix potential error pointer dereference in detach_pm()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 09c4a610153286cef54d4f0c85398f4e32fc227e | Vendor (CNA) |
| Linux Linux | 5127f3cbfc78a7b301b86328247230bec47e0bb3 | Vendor (CNA) |
| Linux Linux | 53b0c7b15accb18d15d95c7fe68f61630ebfd1ca | Vendor (CNA) |
| debian:linux | 6.12.13-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31633422 days apartrxrpc: Fix integer overflow in rxgk_verify_response()39Monitor
- CVE-2026-31649422 days apartnet: stmmac: fix integer underflow in chain mode39Monitor
- CVE-2026-31659422 days apartbatman-adv: reject oversized global TT response buffers39Monitor
- CVE-2026-43341436 days apartnet/ipv6: ioam6: prevent schema length wraparound in trace fill39Monitor
- CVE-2026-46039455 days apartrxgk: Fix potential integer overflow in length check39Monitor
- CVE-2026-46325468 days apartRDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE39Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.