Memory corruption via bracket-parser double-free
Published Jul 23, 2025 · Updated Nov 4, 2025
Double-free in glibc 2.4 through 2.41 allows local users to manipulate memory via crafted regular expressions and allocation failure. The parse_bracket_exp function frees a charset before checking a failed work_tree allocation, and error cleanup then frees that charset again. Triggering the flaw requires heap exhaustion at that allocation or an interposed allocator that injects the failure; the resulting corruption affects the calling process.
Summary
What happened
Double-free in glibc 2.4 through 2.41 allows local users to manipulate memory via crafted regular expressions and allocation failure. The parse_bracket_exp function frees a charset before checking a failed work_tree allocation, and error cleanup then frees that charset again. Triggering the flaw requires heap exhaustion at that allocation or an interposed allocator that injects the failure; the resulting corruption affects the calling process.
The record
- CVE
- CVE-2025-8058
- Published
- Jul 23, 2025
- Updated
- Nov 4, 2025
- Vendor
- The GnuPG Project
- Product
- glibc
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.4 <2.42
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