I thought Chrome was protecting me against Flash bugs running Flash in a sandbox. If so, this exploit needs to break through Chrome's sandbox and it seems legitimate to call it a Chrome exploit.
"Chrome's sandbox" is the Windows "low integrity mode" mandatory access control mechanism. If the process elevation was achieved through a privilege escalation attack against this mechanism rather than by attacking the non-low integrity mode Chrome master process, this might not be a bug in Chrome at all...