I cannot reproduce this bug.
That's fine, there are other miners.
Well, if the bug happens to be on the pool side (ie, pools are not properly checking hashes), then not only is that exploitable, it would be blocked by the pool software I'm writing (which checks share validity fully).
If the bug IS in my miner, I would love to find out what exactly triggers it so I can fix it, but I just don't think it is.