I just don't even know what else needs to be said about a bunch of people who are presumably pretty good at what they do -- the glibc maintainers -- still managing to introduce a *new* buffer overflow bug (new circa 2022) into one of the most important codebases anywhere, which in turn leads to multiple CVEs.

Like, if you're still writing C of any kind in the 21st century, you have to ask yourself "am I better at manual memory safety than the glibc team?" And if the answer is no, then you're probably also writing these kinds of bugs.

RE: https://infosec.exchange/users/BleepingComputer/statuses/111847408179020212