Local process crash via null strtol argument
Published Aug 24, 2025 · Updated Aug 24, 2025
Null pointer dereference in lrzip 0.651 allows local users to crash the compression process via crafted command-line arguments. In main.c at line 440, main passes a null string argument to strtol, whose internal __GI_____strtol_l_internal implementation reads address zero and raises SIGSEGV. Low-privileged local access is required; exploitation terminates the invoked lrzip process, with no reported data disclosure or modification.
Summary
What happened
Null pointer dereference in lrzip 0.651 allows local users to crash the compression process via crafted command-line arguments. In main.c at line 440, main passes a null string argument to strtol, whose internal __GI_____strtol_l_internal implementation reads address zero and raises SIGSEGV. Low-privileged local access is required; exploitation terminates the invoked lrzip process, with no reported data disclosure or modification.
The record
- CVE
- CVE-2025-9396
- Published
- Aug 24, 2025
- Updated
- Aug 24, 2025
- Vendor
- Con Kolivas
- Product
- lrzip
- Classifications
- CWE-404, CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 24, 2025CVE publishedPublication date reported by the CVE source.
- Aug 24, 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.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_lrzip_null_dereferenceproof 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