Important CVSS 7.8 EPSS 0.01635 ⚠️ Exploited in the wild 🔬 Patch diffed 2024-08 archive

Executive Summary

None

Overview

7.8
CVSS HIGH
Important
MS Severity
Exploited
MS Exploit Status
Exploitation Detected
MS Exploit Likelihood
Category Elevation of Privilege
Released Aug 13 2024
Last Updated Aug 13 2024
Publicly Disclosed No
CISA KEV Listed (added 2024-08-13)
Known Exploits None Known
EPSS Score 0.01635 — 0.74184 percentile
NVD CVSS 7.8 HIGH — matches MSRC

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
ATTACK VECTOR
Local
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
Low
USER INTERACTION
None
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Functional
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 7.2

EPSS Score

0.01635
probability of exploitation in the next 30 days
0.74184 percentile - updated 2026-08-14
View on FIRST.org

Affected Products

31 affected products
Product KB Article Severity Impact Restart Required
Windows 10 for 32-bit Systems 5041782 (Security Update) Important Elevation of Privilege Yes
Windows 10 for x64-based Systems 5041782 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1607 for 32-bit Systems 5041773 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1607 for x64-based Systems 5041773 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1809 for 32-bit Systems 5041578 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 1809 for x64-based Systems 5041578 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for 32-bit Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for ARM64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 21H2 for x64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for 32-bit Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for ARM64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 10 Version 22H2 for x64-based Systems 5041580 (Security Update) Important Elevation of Privilege Yes
Windows 11 version 21H2 for ARM64-based Systems 5041592 (Security Update) Important Elevation of Privilege Yes
Windows 11 version 21H2 for x64-based Systems 5041592 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 22H2 for ARM64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 22H2 for x64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for ARM64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 23H2 for x64-based Systems 5041585 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for ARM64-based Systems 5041571 (Security Update) Important Elevation of Privilege Yes
Windows 11 Version 24H2 for x64-based Systems 5041571 (Security Update) Important Elevation of Privilege Yes
Windows Server 2012 5041851 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2012 (Server Core installation) 5041851 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2012 R2 5041828 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2012 R2 (Server Core installation) 5041828 (Monthly Rollup) Important Elevation of Privilege Yes
Windows Server 2016 5041773 (Security Update) Important Elevation of Privilege Yes
Windows Server 2016 (Server Core installation) 5041773 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 5041578 (Security Update) Important Elevation of Privilege Yes
Windows Server 2019 (Server Core installation) 5041578 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 5041160 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022 (Server Core installation) 5041160 (Security Update) Important Elevation of Privilege Yes
Windows Server 2022, 23H2 Edition (Server Core installation) 5041573 (Security Update) Important Elevation of Privilege Yes

Patches

11 patches
Article Type Restart
5041782 Security Update Yes
5041773 Security Update Yes
5041578 Security Update Yes
5041580 Security Update Yes
5041592 Security Update Yes
5041585 Security Update Yes
5041571 Security Update Yes
5041851 Monthly Rollup Yes
5041828 Monthly Rollup Yes
5041160 Security Update Yes
5041573 Security Update Yes

Patch Diff

ghidriff · pdc.sys (KB5041571)

Use-after-free (CWE-416) in the Windows Power Dependency Coordinator kernel driver pdc.sys ALPC message processing, local EoP to SYSTEM - exploited in the wild (per MSRC 'Exploitation Detected'). pdc.sys services client requests over ALPC; PdcpAlpcProcessMessages -> PdcProcessMessage handle client messages and manage per-client objects (freed via PdcFreeClient). PRE: message processing and client-object teardown were not serialized, so one ALPC message could free a PDC client object (PdcFreeClient) while another concurrent message handler still referenced it - a use-after-free of the client object, usable for local EoP to SYSTEM. Diff of pdc.sys 10.0.26100.1301 -> .1455 (Aug 13 2024, KB5041571) confirms the fix: gated behind CFR flag Feature_760025401, PdcProcessMessage and PdcpAlpcProcessMessages now take a global PDC lock (PdcAcquireLock / PdcReleaseLock, with GetPdcLockThread used to detect the already-owning thread / avoid recursive acquire) around message processing and client freeing, serializing the ALPC handlers so a client object cannot be freed while another handler is using it, closing the use-after-free.

Pre-patch version 10.0.26100.1301 Download
Post-patch version 10.0.26100.1455 Download
Function Address Change Note
PdcProcessMessage code change code (message processing + client free under global lock, CFR-gated) Post (Feature_760025401): PdcAcquireLock() taken around the message handling / PdcFreeClient calls, released after - so client teardown is serialized against concurrent message handlers.
PdcpAlpcProcessMessages code change code (ALPC dispatch serialized) Post: GetPdcLockThread() checked, then PdcAcquireLock()/PdcReleaseLock() around dispatch so processing of concurrent ALPC messages is serialized (reentrancy-aware).
PdcAcquireLock / PdcReleaseLock / GetPdcLockThread new/updated added (global PDC lock) Lock primitives introduced/used to serialize PDC message processing and client-object lifetime.
Feature_760025401 gate added (CFR gate) CFR flag gating the lock-serialized message processing; the original unsynchronized path still ships when disabled.
View full diff report View RCA report

Root Cause Analysis

CVE-2024-38107 — Windows Power Dependency Coordinator pdc.sys Unsynchronized ALPC Message Processing → Use-After-Free (Exploited in the Wild)


Summary

Product Windows — pdc.sys (Power Dependency Coordinator)
CVE ID CVE-2024-38107
Impact Elevation of Privilege (to SYSTEM)
MSRC severity Important
CVSS 7.8 / 7.2 — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
CWE CWE-416: Use After Free
Delivery Local — concurrent ALPC messages to the PDC
KB / Fixed build KB5041571 — pdc.sys 10.0.26100.1455 (Win11 24H2 x64)
Patch Date August 13, 2024 (2024-Aug)
Pre-patch binary pdc.sys 10.0.26100.1301 — SHA256 5b22e887722d6f59f787354d6bca1cd8f91b1ad469be26d1de126729cd47588a
Post-patch binary pdc.sys 10.0.26100.1455 — SHA256 11ee9f3cbec684cfcae87497a67878e0f83d5b7a6e5c9417aefed7baf7af60a6
Feature flag Feature_760025401 — the fix is CFR-gated
Exploitability Exploitation Detected (exploited in the wild); not publicly disclosed (per MSRC)

Sourcing note: OS fixed build .1457; the pdc.sys binary in KB5041571 is .1455. Pre = .1301.


Product Description

pdc.sys is the Windows Power Dependency Coordinator, a kernel driver that services client requests over ALPC. PdcpAlpcProcessMessages → PdcProcessMessage handle inbound client messages and manage per-client objects, which are torn down via PdcFreeClient.


Vulnerability Summary

Pre-patch, PDC message processing and client-object teardown were not serialized. One ALPC message could free a PDC client object (PdcFreeClient) while another concurrent message handler still referenced it — a use-after-free of the client object (CWE-416). Because pdc.sys runs in the kernel and the ALPC interface is reachable by a local user, the freed-object reuse is a local elevation-of-privilege primitive to SYSTEM. MSRC marks this Exploitation Detected — it was exploited in the wild.


Prerequisites and Constraints

  • Local, low-privileged (PR:L, AV:L, AC:L): send ALPC messages to the PDC.
  • Issue concurrent messages that create and free the same client object.
  • Result: a freed PDC client object is used by a concurrent handler.

Vulnerability Details

Root Cause

PDC ALPC message handlers shared per-client objects without a lock, so client teardown in one handler could free an object another handler was still using.

The patch (confirmed — diff, .1301 → .1455)

Gated behind Feature_760025401, PdcProcessMessage and PdcpAlpcProcessMessages now take a global PDC lock around message processing and client freeing (PdcAcquireLock / PdcReleaseLock), using GetPdcLockThread to detect the already-owning thread and avoid a recursive re-acquire:

// PdcpAlpcProcessMessages (10.0.26100.1455) — PATCHED (from our diff)
if (Feature_760025401__private_IsEnabledDeviceUsage()) {
    if (GetPdcLockThread() != current_thread)     // reentrancy-aware
        PdcAcquireLock();
}
... PdcProcessMessage(...) ...   // dispatch under the lock
if (Feature_760025401__private_IsEnabledDeviceUsage())
    PdcReleaseLock();

// PdcProcessMessage — PdcAcquireLock() held around the handling / PdcFreeClient(...) calls

Serializing message processing and client teardown under the global lock ensures a PDC client object cannot be freed while another handler is using it, closing the use-after-free.

Patch Completeness Assessment

CFR-gated behind Feature_760025401. The lock-serialized processing runs only when the flag is enabled; the original unsynchronized path still ships when disabled. Verify Feature_760025401 is enabled to confirm the fix is live. (Given in-the-wild exploitation, apply KB5041571 or later regardless.)


Detection Guidance

Behavioural. High-rate / concurrent ALPC traffic to the Power Dependency Coordinator; use-after-free / pool-corruption bugchecks in pdc!PdcProcessMessage / PdcpAlpcProcessMessages / PdcFreeClient on unpatched/flag-disabled builds.

Config. The fix is CFR-gated — confirm Feature_760025401 is enabled.


References

  • MSRC advisory — CVE-2024-38107 (Windows Power Dependency Coordinator Elevation of Privilege), released 2024-08-13, KB5041571. Exploitation Detected.
  • Full binary diff: /data/patch_diffs/pdc_sys-cve-2024-38107-ghidriff.md

Attack Path

Concurrent PDC ALPC messages free a client object while another handler uses it

Attack path for CVE-2024-38107 Concurrent PDC ALPC messages free a client object while another handler uses it 01 — ENTRY Local user sends ALPC messages to the Power Dependency Coordinator pdc.sys PdcpAlpcProcessMessages -> PdcProcessMessage handle client messages and per-client objects. AV:L/PR:L/AC:L. 02 — CONTROLLED INPUT Issues concurrent messages that create/free the same client object One message frees the client (PdcFreeClient) while another still references it. 03 — MISSING CHECK Message processing / client teardown not serialized (CWE-416) Unsynchronized ALPC handlers free a client object in use -> use-after-free. 04 — PATH Freed PDC client object is dereferenced in the kernel Controlling the freed/reused allocation influences kernel state (exploited in the wild). 05 — PRIMITIVE Use-after-free in pdc.sys -> EoP to SYSTEM The Aug 2024 fix (Feature_760025401) serializes message processing and client freeing under a global PDC lock.

Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.

Exploits & PoC

Detection Rules

Acknowledgments

Anonymous