Guard empty successful WMI enumeration batches

[Copilot]

A malformed remote WMI enumerator can report success without returning an object, causing Current to dereference a null cache entry.

• Enumeration guard: throw a ManagementException for zero-result successful batches after preserving timeout and normal end-of-enumeration handling.

if (cachedCount == 0)
    ManagementException.ThrowWithExtendedInfo(ManagementStatus.Timedout);

Note

This PR description was generated by AI/Copilot.

• Fixes Potential null-deref in remote WMI enumeration #128581

[Copilot]

Copilot wasn't able to review any files in this pull request.

[azure-pipelines]

Azure Pipelines:
16 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/libraries/System.Management/src/System/Management/ManagementObjectCollection.cs:586

• This change adds a new exception-throwing path for malformed WMI enumerators (success status with cachedCount == 0), but there’s no regression test exercising this behavior. Without a test, it’s easy for future refactors to remove or change this guard and reintroduce the original null-deref scenario.

                        if (cachedCount == 0)
                            ManagementException.ThrowWithExtendedInfo(ManagementStatus.Timedout);

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/libraries/System.Management/src/System/Management/ManagementObjectCollection.cs:588

• The PR description (and the existing pattern in ManagementEventWatcher.cs:436-437) indicates this guard should throw a Timedout ManagementException for a successful fetch that returns 0 objects, but the implementation throws ManagementStatus.Failed here. Please reconcile (either update the PR description / issue rationale, or align the code with the Timedout behavior used elsewhere).

                        //A malformed enumerator can report success without returning any objects; treat this as a failure
                        //rather than silently proceeding with an empty cache.
                        if (cachedCount == 0)
                            ManagementException.ThrowWithExtendedInfo(ManagementStatus.Failed);

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-management
See info in area-owners.md if you want to be subscribed.