CVE-2025-38188

What it actually does

Missing CP_RESET_CONTEXT_STATE call on context switch in the MSM A7XX driver leaves persistent BR/BV synchronization state across submits, allowing one context's userspace submission to corrupt or hang another context.

Why it matters to the business

May cause graphics-related system hangs or denial of service on affected Linux kernels without data exposure; low EPSS and 480 days since publication indicate limited active exploitation risk but still requires patching for stability in graphics workloads.

How an attack unfolds

An attacker submits specially crafted GPU commands in one context that leave unsafe persistent state; on the next context switch the state affects a second context, triggering incorrect operation or a hang.

How to fix it

Upgrade to kernel containing commit 8a1f52651dd8203695d293c6824d8f6c067877d1 or to package versions 25.6.0.109173-r0 for affected Chainguard and Wolfi sonarqube variants.

How to confirm the fix worked

Confirm the patch is present in drm/msm/a7xx source or verify installed package versions match the listed fixed releases.

Typical attack path

1. Identify systems running vulnerable MSM A7XX kernel code
2. Obtain ability to submit userspace graphics commands in one context
3. Craft submissions that manipulate persistent BR/BV state
4. Force or wait for a context switch to induce hang in target context

How to detect it

Review kernel logs for drm/msm context-switch errors or unexplained GPU hangs; correlate with userspace graphics submissions around the time of the incident.

What your security team should do

• Apply the listed kernel or package updates across all affected systems
• Prioritize updates on systems with active GPU workloads
• Monitor graphics driver stability after deployment