summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorVitaly Kuznetsov <vkuznets@redhat.com>2020-04-06 12:43:26 +0200
committerWei Liu <wei.liu@kernel.org>2020-04-23 13:17:11 +0000
commit52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd (patch)
tree1889c9ac8030dcea62f5a3ed28b90b926dd9b42b /.gitignore
parentb0a284dc65b401a508dc2c5ed7d465884220f607 (diff)
downloadlwn-52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd.tar.gz
lwn-52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd.zip
Drivers: hv: check VMBus messages lengths
VMBus message handlers (channel_message_table) receive a pointer to 'struct vmbus_channel_message_header' and cast it to a structure of their choice, which is sometimes longer than the header. We, however, don't check that the message is long enough so in case hypervisor screws up we'll be accessing memory beyond what was allocated for temporary buffer. Previously, we used to always allocate and copy 256 bytes from message page to temporary buffer but this is hardly better: in case the message is shorter than we expect we'll be trying to consume garbage as some real data and no memory guarding technique will be able to identify an issue. Introduce 'min_payload_len' to 'struct vmbus_channel_message_table_entry' and check against it in vmbus_on_msg_dpc(). Note, we can't require the exact length as new hypervisor versions may add extra fields to messages, we only check that the message is not shorter than we expect. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Reviewed-by: Michael Kelley <mikelley@microsoft.com> Link: https://lore.kernel.org/r/20200406104326.45361-1-vkuznets@redhat.com Signed-off-by: Wei Liu <wei.liu@kernel.org>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions