Note that what you talk about has nothing to do with the underlying bug. UEFI provides a mechanism where any installed operating system can store and use named variables. The Samsung firmware fails if the size is more than trivial but not unreasonable amount.
Linux just happened to be first to hit the problem because on a kernel panic, it writes diagnostic information to UEFI variables (only 10kb - well within the spec). The panic happened to be caused by Samsung driver written to Samsung's specs, but that is coincidental.
Microsoft panics can be minidump format which are up to 64kb in size (also within the spec) so if they did the same thing then they'd hit the same issue. Or if Microsoft decided to throw some other stuff in there (eg information during upgrades, recovery information) they could cause exactly the same problem.