RE: [PATCH v2 3/3] hv_netvsc: Use vmbus_requestor to generate transaction IDs for VMBus hardening
From: Haiyang Zhang <haiyangz@microsoft.com>
Date: 2020-06-29 21:33:34
Also in:
linux-hyperv, lkml
From: Haiyang Zhang <haiyangz@microsoft.com>
Date: 2020-06-29 21:33:34
Also in:
linux-hyperv, lkml
-----Original Message----- From: Andres Beltran <redacted> Sent: Monday, June 29, 2020 4:02 PM To: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang [off-list ref]; Stephen Hemminger [off-list ref]; wei.liu@kernel.org Cc: linux-hyperv@vger.kernel.org; linux-kernel@vger.kernel.org; Michael Kelley [off-list ref]; parri.andrea@gmail.com; Andres Beltran [off-list ref]; David S . Miller [off-list ref]; Jakub Kicinski [off-list ref]; netdev@vger.kernel.org Subject: [PATCH v2 3/3] hv_netvsc: Use vmbus_requestor to generate transaction IDs for VMBus hardening Currently, pointers to guest memory are passed to Hyper-V as transaction IDs in netvsc. In the face of errors or malicious behavior in Hyper-V, netvsc should not expose or trust the transaction IDs returned by Hyper-V to be valid guest memory addresses. Instead, use small integers generated by vmbus_requestor as requests (transaction) IDs. Cc: David S. Miller <davem@davemloft.net> Cc: Jakub Kicinski <kuba@kernel.org> Cc: netdev@vger.kernel.org Signed-off-by: Andres Beltran <redacted>
Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>