Windows DirectX CVE-2025-55698

Exploitation requires the attacker to already possess low-level authorized access (PR:L) to reach the vulnerable Windows DirectX code path over the network; it is not anonymously reachable. No user interaction is needed (UI:N) and attack complexity is low (AC:L). The limiting factor is the authentication/authorization requirement - the attacker must be an authorized network participant - and impact is restricted to availability (denial of service) with no confidentiality or integrity effect. The MSRC advisory does not specify a particular non-default configuration or DirectX feature, so the trigger is assumed to apply to standard DirectX functionality on the affected Windows 11 24H2/25H2 and Windows Server 2025 builds.

This is a medium-priority availability issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H, base 7.7) describes a network-reachable, low-complexity denial of service that nonetheless requires some level of privilege (PR:L) - so an attacker must already be an authenticated/authorized party, not an anonymous internet stranger. Impact is confined to availability (C:N/I:N/A:H); there is no data exposure or code execution, which caps the real-world severity. The scope change (S:C) is what elevates the score, but for a null pointer dereference (CWE-476) that typically manifests as a crash/hang of the affected service or host. Exploitation signals are modest and consistent: EPSS is only 1.20% (68th percentile), there is no CISA KEV listing, and no public exploit code was identified, so this is not evidence of active or widespread exploitation. No signals conflict - all available data points to a credible but non-urgent DoS. The main uncertainty is that the single Microsoft MSRC reference provides no technical detail on the exact DirectX code path or affected configuration, so the precise trigger cannot be independently verified.

An attacker who already holds low-level authorized access on the network sends specially crafted input to a Windows DirectX code path, triggering a null pointer dereference that crashes or hangs the targeted service or system, denying service to legitimate users. No public proof-of-concept exploit was identified at the time of analysis, and the low complexity (AC:L) means the malformed input itself is not difficult to construct once the trigger is known.