Flooding with extended CAN IDs cause packets to be broadcast

[FrostTusk]

When sending messages to extended CAN identifiers such as for example id 0xFFFF, VulCAN interprets these as being sent to ID 0x0 (broadcast ID).
This occurs most reliably when flooding the bus with extended CAN IDs, it was observed while fuzz testing the demo bench.
The packets are still observed as being extended packets using candump, but VulCAN believes them to be sent to ID 0x0.

I have tried fixing it, but have not had much success.