Have you checked if your situation fulfills everything that the kb speaks about? If you suspect that it may be that bug, seems like the only way to verify that for sure is to apply the fix mentioned in the kb.
If that is not the case, then corruption like the message says, is likely.
In any case, I can only guess - what is sure is that DBCC thinks it has found an inconsistency. For the most parts, these situations (if proven to be irreparable) is what your backups are ment for.
What step to take next really depends on what you can do.
The options are either to apply the fix, and check again. If the error is gone, all is well, and it was the bug. or... run DBCC again with the option mentioned in the error. This will probably lead to loss of data - if that data aren't already lost. If you suspect this, then you probably need to restore to the last known good backup anyway, in order to get the missing data back.
/Kenneth