No. This exploit runs against the firmware of the wireless chipset itself. (That's what's so weird and interesting about it.)
That being said -- the wireless chipset firmware is loaded by the application processor, so it still requires an OS update to fix.
I guess this must work differently on Android handsets with Broadcom wifi, if it's not possible to just push a new firmware bin file into /usr/lib/firmware? Presumably Google could do that, although I'm not sure what the code signing requirments are for firmware blobs such as this.
Savvy users with root can probably patch it themselves, if they can find the correct fixed firmware binary and know where it's stored on their device.
Your first statement isn't congruent with your second statement. That they push it to their devices alone does not mean they "can and did" apply the update to all Android devices. My whole post is that they can't push kernel drivers to handsets that aren't theirs.
Worse is Better strikes again.
Google has nothing close. Even if they tried, it could take a decade to get there.
It's like criticizing Windows, that it doesn't run on Chromebooks or PPC Macs.
The issue is whether it will result in better product, where better is defined as "will it sell more?". Your average cellphone buyer does not care about that. But he cares about thinness and battery life, which would be affected by a more universal platform.
Imagine a 3D chart, where one axis is battery life and small-sized hardware, second is versatility, third showing the sales, with a curve going through, showing a compromise between two trade-offs and total sales for that compromise. We are currently in one point, with few people arguing to change the position to another point, completely ignoring these two other axes.
fwiw: my Nexus does not see the update yet.
Whereas Google can't do that; it'd be up to the handset manufacturer.
Is this an example of the problem Google faces using the Linux kernel in Android? It cedes the kernel to the manufacturer, and wifi (and bluetooth etc) drivers are all kernel space, not user space. So Google can't really do anything here can they?