I assume this is a bug in firmware version that's only used on enterprise class hardware, but that they assumed the bug also exists on consumer grade hardware o

I assume this is a bug in firmware version that's only used on enterprise class hardware, but that they assumed the bug also exists on consumer grade hardware on the basis of the circuits being mostly the same (and thus assuming the firmware is shared).