Why can a valid looking pointer still corrupt unrelated data?

A strong answer

A strong candidate frames Why can a valid looking pointer still corrupt unrelated data? around the exact memory layout, compiler semantics, and hardware execution model covered in Dangling Pointers and Use-After-Free. Trace dangling pointers through free and reuse to show silent corruption and defenses.

Lesson 9 covered forgetting to free memory. The opposite mistake is freeing it, or losing it, while someone still holds its address. A pointer, or a reference, to an object that no longer exists is called dangling. Here is code that looks harmless:

The caller receives a pointer into a stack frame that was popped when the function returned, as lesson 6 of module 2 described. Compilers warn about this simple form with -Wreturn-local-addr, but the same bug has subtler forms, and the stale pointer still looks like a perfectly good address.

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

• Mastery of core invariant: Identify the common ways in which a pointer or reference becomes dangling.
• Mastery of core invariant: Trace what happens when a freed block is reused while a stale pointer still exists.
• Mastery of core invariant: Explain why setting one pointer to nullptr after delete does not make a program safe.
• Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
• Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

• Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
• Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.