On 23.06.2022 13:24, Julien Grall wrote:
> From: Julien Grall <jgr...@amazon.com>
>
> At the moment, corrupt() is neither checking for allocation failure
> nor freeing the allocated memory.
>
> Harden the code by printing ENOMEM if the allocation failed and
> free 'str' after the last use.
>
> This is not considered to be a security issue because corrupt() should
> only be called when Xenstored thinks the database is corrupted. Note
> that the trigger (i.e. a guest reliably provoking the call) would be
> a security issue.
>
> Fixes: 06d17943f0cd ("Added a basic integrity checker, and some basic ability
> to recover from store")
> Signed-off-by: Julien Grall <jgr...@amazon.com>
Is this something which would want queuing for backport?
Jan
