Re:Out-of-bounds read and write in the glibc's qsort()
by Scubabear68 on Monday February 05, 2024 @01:55PM
(#39265299)
A bit of a non-event to me, this is a bug in user code. I don’t see it much differently then freeing a block twice or using an uninitialized pointer. It’s the price of using C.
[ Parent
| on HN ]
Re:Out-of-bounds read and write in the glibc's qsort()
by NotYourLawyer on Monday February 05, 2024 @02:01PM
(#39265399)
It’s a footgun for sure though, since the “obvious” comparison function of subtracting arguments is intransitive with integer overflow.