Local application crash via malformed GPU metrics
Published Mar 26, 2025 · Updated Apr 7, 2025
Heap corruption in Atop Project atop 2.4.0 through 2.11.0 allows local users to crash another user's atop process via crafted GPU metrics. During initialization, atop connects to atopgpud's local TCP port and parses metric strings without sufficient validation. A local unprivileged process must bind that port before another user starts atop; observed exploitation causes heap corruption and a segmentation fault.
Summary
What happened
Heap corruption in Atop Project atop 2.4.0 through 2.11.0 allows local users to crash another user's atop process via crafted GPU metrics. During initialization, atop connects to atopgpud's local TCP port and parses metric strings without sufficient validation. A local unprivileged process must bind that port before another user starts atop; observed exploitation causes heap corruption and a segmentation fault.
The record
- CVE
- CVE-2025-31160
- Published
- Mar 26, 2025
- Updated
- Apr 7, 2025
- Vendor
- Atop Project
- Product
- atop
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2025CVE publishedPublication date reported by the CVE source.
- Apr 7, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.11.0
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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