ACK: [SRU][O/N/J][PATCH 0/1] CVE-2024-53103

Magali Lemes magali.lemes at canonical.com
Wed Dec 18 19:06:48 UTC 2024


On 13/12/2024 17:13, Bethany Jamison wrote:
> [Impact]
> 
> hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
> 
> When hvs is released, there is a possibility that vsk->trans may not
> be initialized to NULL, which could lead to a dangling pointer.
> This issue is resolved by initializing vsk->trans to NULL.
> 
> [Fix]
> 
> Oracular: Clean cherry-pick
> Noble:	  Oracular patch applied cleanly
> Jammmy:	  Oracuaar patch applied cleanly
> Focal:	  Patch already applied via stable team (0d3fe569af8205a3c8f96b54b1a5a7a14c5f5250)
> Bionic:	  Fix sent to esm ML
> Xenial:	  not-affected
> Trusty:	  not-affected
> 
> [Test Case]
> 
> Compile and boot tested.
> 
> [Where problems could occur]
> 
> This fix affects those who use Hyper-B transport for vsock, an issue with
> this fix would be visible to the user via memory corruption or a system
> crash.
> 
> Hyunwoo Kim (1):
>    hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
> 
>   net/vmw_vsock/hyperv_transport.c | 1 +
>   1 file changed, 1 insertion(+)
> 

Acked-by: Magali Lemes <magali.lemes at canonical.com>



More information about the kernel-team mailing list