Release candidate for Blocek 1.75 (Announce)
> > I found two obvious bugs in the code causing writtig into already
> > dealocated memory block.
>
> Hehe, many yrs ago I was also hunting such kind of bug in my DJGPP program
> that wrote to freed memory. And it also behaves differently under different
> OSes, on some running fine on others crashed (not freedos but MS-DOS and
> Windows)...
Is that a 'use-after-free' like I keep seeing in the bug fixes of Linux programs ?
+--------------------------+
Tue Oct 24 22:26:20 UTC 2023
ap/vim-9.0.2063-x86_64-1.txz: Upgraded.
Fixed use-after-free security issue.
Thanks to marav for the heads-up.
For more information, see:
https://www.cve.org/CVERecord?id=CVE-2023-5535
(* Security fix *)
__________
---
--
http://glennmcc.org/
Complete thread:
- Release candidate for Blocek 1.75 - Laaca, 14.10.2023, 13:37 (Announce)
- Release candidate for Blocek 1.75 - Laaca, 20.10.2023, 13:16
- Release candidate for Blocek 1.75 - RayeR, 27.10.2023, 06:42
- Release candidate for Blocek 1.75 - Laaca, 27.10.2023, 19:29
- Release candidate for Blocek 1.75 - RayeR, 28.10.2023, 01:39
- Release candidate for Blocek 1.75 - glennmcc, 28.10.2023, 06:30
- Release candidate for Blocek 1.75 - Laaca, 28.10.2023, 08:56
- Release candidate for Blocek 1.75 - RayeR, 31.10.2023, 23:54
- Release candidate for Blocek 1.75 - Laaca, 28.10.2023, 08:56
- Release candidate for Blocek 1.75 - glennmcc, 28.10.2023, 06:30
- Release candidate for Blocek 1.75 - RayeR, 28.10.2023, 01:39
- Release candidate for Blocek 1.75 - Laaca, 27.10.2023, 19:29
- Release candidate for Blocek 1.75 - RayeR, 27.10.2023, 06:42
- Release candidate for Blocek 1.75 - Laaca, 20.10.2023, 13:16