This isn't privileged information - you can find the same in Device Manager without admin authorization, on Windows - but why does Chrome need it?

The potential issues raised are a bit tenuous

> Indeed..Let's hope somebody doesn't find a way to hack into it from code and use it to create some vulnerability

I understand some WebUSB ustage, but why is this gets persisted across Chrome reboots?!