Local process crash via freed thread array
Published Feb 10, 2026 · Updated Feb 10, 2026
Null pointer dereference in lrzip 0.651 allows local users to crash decompression by testing a crafted archive with multiple threads. During a decompression error, clear_rulist frees sinfo->ucthreads while a concurrent ucompthread still indexes that pointer, causing a zero-page read. A user able to run lrzip against the crafted archive can terminate that lrzip process; no confidentiality or integrity impact is reported.
Summary
What happened
Null pointer dereference in lrzip 0.651 allows local users to crash decompression by testing a crafted archive with multiple threads. During a decompression error, clear_rulist frees sinfo->ucthreads while a concurrent ucompthread still indexes that pointer, causing a zero-page read. A user able to run lrzip against the crafted archive can terminate that lrzip process; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2025-15571
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- Con Kolivas
- Product
- lrzip
- Classifications
- CWE-404, CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record 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.651
What conditions does exploitation require?
What is affected?
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
- PoC_NPD crafted lrzip archiveproof of concept · demonstrated
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