Yup you are right on that, but the obvious way to check for overflow is UB so gets optimized out. Many security bugs in code people thought was correct. The correct, standard compliant non-UB way to check for the overflow requires a zero check and a division. It’s super non obvious. I like to imagine C committee has made standardized definition for the current builtins but I also have low expectations.
Eh, the undefined nature of signed overflow in C is a bit of a red herring. The most common overflow bug in practice is actually 100% well-defined and still 100% wrong: multiplying two numbers to feed into a malloc.
In practice, the undefined signed overflow really only comes into play when you're trying to explicitly check for overflow by doing the operation and then seeing if it overflowed. But, as you mention, compilers give you bultins to do this kind of checked overflow which is quite frankly a much easier way to solve the problem, especially since it's more likely to actually get matched to using hardware flag bits to check for overflow.