This is not correct; at least, not in the implementations I've seen. You will get a rejection frame from the AP, which you can see in a 802.11 sniffer. (It's not a "packet", but packets don't have MAC addresses anyway.)

To clarify, in the 802.11 standard the "authentication" phase is a leftover wart from the WEP days, and is essentially a no-op: an authentication request provides no credentials and results in an automatic success (unless you've been MAC-filtered). Still, it must be done before associating with the AP to make sure its protocol state machine is in the right place. The WPA2 key negotiation stuff that provides the actual authentication happens after the association phase and is called RSN (Robust Secure Negotiation).

I appreciate this answer -- IncludeOS is a very interesting project and this is a very interesting edge-case behavior.

Note that for simplicity this answer is written as if a cloud provider is running a tenant's workload on a bare metal. The same principles apply to virtual machines with virtual TPMs -- except that a virtual TPM typically doesn't require a soldering iron to fool. I can go into more detail in another question if you're interested in the differences in the trust model between virtual and physical TPMs.