When rkhunter is updated with new versions, md5 checksums/hashes of key binary files that are likely to be trojaned are added. The exact hash value will vary from version to version so, for example, there might be some small change between the ifconfig binary on SuSE 8.2 and on SuSE 9.0.
Rkhunter figures out what version of Linux you are running and, if it knows the "correct" hashes for that, it checks them. Keeping all those hashes up to date is a pretty thankless task and, of course, if you update something that rolls out a new version of one of those binaries, the hash is going to be wrong.
This is almost certainly a false positive, which you should be able to safely ignore.
You could also contact the maintainer (Michael) at
www.rkhunter.org/contact/ and let him know the details. He puts out new versions of rkhunter ever few weeks so an update should get in pretty quickly.