Can you back that up? The exploit states x86_64, and even if there is only an x86 exploit published, it's likely the same vulnerability is present on an x86_64 kernel (in general).
Lack of exploit code doesn't imply a lack of vulnerability :)
I mean, the fix consists in making sure that attr.config has all the 64 bits cleared -
on the 64 bit machines, int is 64bit, so u64 == int, and all the bits are correctly handled.
on 32 bit machines, int is 32bit, and the top 32 bit of attr.config is not cleared.
I may be wrong though, as I didn't scan through all the affected code.
