The only hang-up is this is entirely OS independent. Generally, this information is flashed into the processor's microcode (or firmware). Every OS is designed so it reads exactly what the chip manufacturer flashed into the CPU information in the factory, nothing more, nothing less. Linux and Mac OS X will show the same thing as will CPUID and other tools made for reading a CPU's hardware information. If this is an issue, Intel will need to send out a microcode update for the CPU and this is typically distributed via BIOS updates.
Fortunately, it is also entirely possible that the processor in this prototype is an engineering sample (basically, a prototype) from Intel, in which case this issue might not exist at all in production versions of the processor. In other words, it appears Intel may have changed the name of the Core M processor midway while sending out engineering samples of these new Kaby Lake processors to customers like Eve.
This problem appears in a few different benchmarks that list this processor with not one but both names in their databases. We are probably looking at early engineering samples of this processor in here that accounts for this. Here is one example of this. Note that Intel Core m7-7Y75 and Intel Core i7-7Y75 both exist in SiSoftware's benchmark database. The m7 entries are from early 2016 while the i7 entries are from this year. In other words, it appears Intel may have changed the name of the Core M processor midway while sending out engineering samples of these Kaby Lake Processors to customers like Eve:
Intel Core m7-7Y75
Intel Core i7-7Y75
Here is another example of the Core m5-7Y54 and Core i5-7Y54 both present in the Geekbench benchmark database:
@Team: Did you notice this odd naming at all?