Code execution or crash via calloc overflow
Published Aug 17, 2021 · Updated Aug 22, 2025
Integer overflow in the C runtime library of BlackBerry QNX products allows remote attackers to execute code or crash affected devices. The calloc() implementation fails to detect overflow when multiplying attacker-controlled element counts and sizes, causing an undersized allocation before later memory access. Exploitation requires control of the calloc() parameters and subsequent memory access; network reachability enables remote attack when a vulnerable device is internet-exposed.
Summary
What happened
Integer overflow in the C runtime library of BlackBerry QNX products allows remote attackers to execute code or crash affected devices. The calloc() implementation fails to detect overflow when multiplying attacker-controlled element counts and sizes, causing an undersized allocation before later memory access. Exploitation requires control of the calloc() parameters and subsequent memory access; network reachability enables remote attack when a vulnerable device is internet-exposed.
The record
- CVE
- CVE-2021-22156
- Published
- Aug 17, 2021
- Updated
- Aug 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, CAPEC-92
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 22, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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