On Tue, 21 Oct 2025 16:54:13 +0200, Ahmad Fatoum wrote:
> If the realloc call unexpectedly succeeds, the p pointer is invalidated,
> but it's free'd unconditionally later on, which triggers a
> user-after-free.
>
> Account for this by zeroing p when it becomes stale.
>
>
> [...]
Applied, thanks!
[1/2] test: self: malloc: fix double free after expect_alloc_fail
https://git.pengutronix.de/cgit/barebox/commit/?id=745c925fa79e (link may
not be stable)
[2/2] test: self: malloc: fix false positive when malloc store is registered
https://git.pengutronix.de/cgit/barebox/commit/?id=e11c2f618876 (link may
not be stable)
Best regards,
--
Sascha Hauer <[email protected]>
