Service interruption via HTS driver race
Published Nov 4, 2025 · Updated Nov 4, 2025
Out-of-bounds write in the HTS driver in Samsung Exynos 1580, 2400, and 2500 allows remote attackers to interrupt service. Concurrent HTS driver operations can race, causing a memory write to exceed its intended bounds. Network access requires no authentication or user interaction; the documented consequence is limited to service interruption.
Summary
What happened
Out-of-bounds write in the HTS driver in Samsung Exynos 1580, 2400, and 2500 allows remote attackers to interrupt service. Concurrent HTS driver operations can race, causing a memory write to exceed its intended bounds. Network access requires no authentication or user interaction; the documented consequence is limited to service interruption.
The record
- CVE
- CVE-2025-52513
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo