This issue isn't that big of a deal for those who dealt with secure boot on Linux before. You just need to sign the modules yourself using the certificates you generated to use with `shim-signed` (Ubuntu does this for you if you install a software that uses DKMS to build its kernel modules), or those you enrolled in your secure boot database.
Here's a quick snippet for Ubuntu users who generated and enrolled the certificates on their installs already;
for i in vm{mon,net}; do
sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.{priv,der} /usr/lib/modules/$(uname -r)/misc/$i.ko
done
The directory name "shim-signed" might be different on distros other than Ubuntu.
If you did generate certificates but didn't enroll them yet, you can do so with "mokutil". If you didn't generate such certificates at all, you will have to generate a pair and enroll it. Look into your distro wiki pages/blog posts for more info. Arch Wiki is a good starting point for topics like this.
If you're a developer working on VMware kernel modules, I would strongly recommend you to add support for this either by using DKMS or within "vmware-modconfig".