PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-71303 Linux CVE debrief

A race condition in the Linux kernel's AMD XDNA accelerator driver (accel/amdxdna) could allow commands to be submitted while the device is in an improper power state. The vulnerability exists in the driver's runtime power management (RPM) logic where the `rpm_on` flag was used to indicate suspend/resume progress. When autosuspend triggers, this flag is set; however, if a userspace application submits a command during this narrow window, `amdxdna_pm_resume_get()` may incorrectly skip the resume operation because `rpm_on` remains set. This results in commands being submitted while the device has not actually resumed, leading to unexpected behavior. The fix removes the `rpm_on` flag entirely and introduces `aie2_pm_set_dpm()` to explicitly resume the device before invoking `set_dpm()`, ensuring proper synchronization between power state transitions and command submission.

Vendor
Linux
Product
Unknown
CVSS
MEDIUM 4.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-27
Original CVE updated
2026-06-25
Advisory published
2026-05-27
Advisory updated
2026-06-25

Who should care

Organizations running Linux systems with AMD XDNA AI accelerators, particularly those utilizing runtime power management features. Cloud providers and HPC environments with AMD XDNA hardware should prioritize kernel updates. System administrators managing workstations or servers with AMD Ryzen AI or similar XDNA-based accelerators.

Technical summary

The accel/amdxdna driver in the Linux kernel contains a race condition in its runtime power management implementation. The `rpm_on` flag, intended to prevent recursive suspend/resume calls via `set_dpm()`, creates a timing window where `amdxdna_pm_resume_get()` may return success without actually resuming the device. This occurs when autosuspend is triggered and a userspace command submission interleaves with the flag check. The resolution removes the `rpm_on` flag and restructures the code to use `aie2_pm_set_dpm()` for explicit resume operations outside of the core suspend/resume paths, while calling `set_dpm()` directly within those paths.

Defensive priority

medium

Recommended defensive actions

  • Apply kernel updates containing the referenced stable tree commits when available from your Linux distribution
  • Monitor vendor security advisories for AMD XDNA driver updates
  • Review systems utilizing AMD XDNA accelerators for unexpected behavior during power state transitions
  • Consider disabling runtime power management for AMD XDNA devices as a temporary mitigation if operational impact is observed

Evidence notes

The vulnerability description is sourced from the official CVE record published by NVD on 2026-05-27. The fix involves kernel-level changes to the AMD XDNA accelerator driver's power management subsystem. Two kernel.org stable tree commits are referenced as resolution sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-71303 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-71303

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-71303 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-71303

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/00ffe45ece80160aef446d74ded906352f21dd72

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e7cb75b6a5127d78298e39750b4f3185eca0dafc

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.