I'm not clear whether the 'corrupted' memory location actually contains the wrong value, or the read just returns the wrong result. If the latter is the case you could perhaps keep reading the memory location until two consecutive reads return the same value? This would avoid the need to use the semaphore at all.

I realise that this method may not be suitable for your specific application.