| Previous | Next |
| ERROR_USER_PROFILE_LOAD | ERROR_PIPE_CONNECTED |
ERROR_ARITHMETIC_OVERFLOW
An arithmetic result exceeded the supported range
ERROR_ARITHMETIC_OVERFLOW means an integer calculation or conversion could not be represented in the destination width. The classic message mentions 32 bits, but the practical issue is unsafe range conversion.
Common sources
- Multiplying counts by element sizes without checking overflow.
- Converting file sizes, offsets, or timestamps to a narrower type.
- Mixing signed and unsigned values.
- Computing buffer sizes from untrusted input.
Diagnosis
Log operands, source and destination types, and the exact conversion point. Test boundary values, zero, negative inputs, and values near the maximum representable size. Static analysis and compiler overflow checks can identify many paths.
Correct handling
Use checked-arithmetic helpers before allocation or I/O. Reject impossible requests rather than wrapping or saturating silently. Keep sizes and offsets in types wide enough for the platform and API contract.
Security importance
Unchecked overflow can turn a large logical size into a small allocation, leading to buffer corruption. Treat overflow errors at trust boundaries as validation failures, not exceptional edge cases.
References
Looking for a different code? Search another status or error code.