Well turns out it's most likely a bug in the AMD driver, explicitely setting the correct stride value in glVertexAttribPointer() has solved the issue. Seems like the NVidia driver correctly calculates the stride with the parameter set to 0, as it should according to specification, but the Radeon driver seems to have an issue with that.