The reason it took 3 weeks appears to be because that's around how long it took Kees to come up with a general-case demonstration of the bug. You really have to stretch a bit to argue that Kees was acting in any way other than as someone trying to work out the technicalities of the bug, and just trying to get other technical people interested in the problem, on that basis alone. And if you look at the upstream bug various people (from various vendors) discussed it.
Isn't part of the benefit of Linux that it provides a way for commercial organisations to work semi-mutually to further the interests of *shared* code.
Again, these accusations appear less than solidly founded. It surely can not be good to start creating an atmosphere where people are afraid to talk to other developers of a project about a bug just because they work for a different vendor.