The Server Message Block (SMB) driver (MRXSMB.SYS) in Microsoft Windows 2000 SP4, XP SP1 and SP2, and Server 2003 SP1 and earlier allows local users to cause a denial of service (hang) by calling the MrxSmbCscIoctlCloseForCopyChunk with the file handle of the shadow device, which results in a deadlock, aka the SMB Invalid Handle Vulnerability.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Windows_2000 | Microsoft | –sp4 (including) | –sp4 (including) |
| Windows_2003_server | Microsoft | - (including) | - (including) |
| Windows_2003_server | Microsoft | –sp1 (including) | –sp1 (including) |
| Windows_xp | Microsoft | - (including) | - (including) |
| Windows_xp | Microsoft | –sp1 (including) | –sp1 (including) |
| Windows_xp | Microsoft | –sp2 (including) | –sp2 (including) |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.