Application crash via unchecked NULL reallocation pointer
Published Nov 19, 2025 · Updated Nov 19, 2025
NULL pointer dereference in mruby/c 3.0 through 3.4 allows local users to crash an embedding application through mrbc_raw_realloc. The allocator passes a NULL ptr through BLOCK_ADRS pointer arithmetic, then BLOCK_SIZE dereferences the resulting invalid address. Low-privileged local code must make the embedding program invoke this path with a NULL pointer; the bounded consequence is an immediate process crash.
Summary
What happened
NULL pointer dereference in mruby/c 3.0 through 3.4 allows local users to crash an embedding application through mrbc_raw_realloc. The allocator passes a NULL ptr through BLOCK_ADRS pointer arithmetic, then BLOCK_SIZE dereferences the resulting invalid address. Low-privileged local code must make the embedding program invoke this path with a NULL pointer; the bounded consequence is an immediate process crash.
The record
- CVE
- CVE-2025-13397
- Published
- Nov 19, 2025
- Updated
- Nov 19, 2025
- Vendor
- ITOC mruby/c team
- Product
- mruby/c
- Classifications
- CWE-404, CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2025CVE publishedPublication date reported by the CVE source.
- Nov 19, 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=3.0
- Affected versionversion=3.1
- Affected versionversion=3.2
- Affected versionversion=3.3
- Affected versionversion=3.4
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
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