Yes, it does look like a cosmetic bug. It should not cause any problem in the system and that could be one of the reasons the bug was not fixed in an earlier version. You can ignore the error as long as you can live with it. This should not break anything on the system.
As this is fixed in CM 4.3(1) which is already available, you can upgrade to that version.
Hope that helps.