In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Fix race condition when checking rpm_on When autosuspend is triggered, driver rpm_on flag is set to indicate that a suspend/resume is already in progress. However, when a userspace application submits a command during this narrow window, amdxdna_pm_resume_get() may incorrectly skip the resume operation because the rpm_on flag is still set. This results in commands being submitted while the device has not actually resumed, causing unexpected behavior. The set_dpm() is called by suspend/resume, it relied on rpm_on flag to avoid calling into rpm suspend/resume recursivly. So to fix this, remove the use of the rpm_on flag entirely. Instead, introduce aie2_pm_set_dpm() which explicitly resumes the device before invoking set_dpm(). With this change, set_dpm() is called directly inside the suspend or resume execution path. Otherwise, aie2_pm_set_dpm() is called.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://git.kernel.org/stable/c/00ffe45ece80160aef446d74ded906352f21dd72 Patch
- https://git.kernel.org/stable/c/e7cb75b6a5127d78298e39750b4f3185eca0dafc Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- References+1 references (now 3)NVD modified 2026-10-15 11:17
- StatusAnalyzed → ModifiedNVD modified 2026-10-15 11:17
- First seenCVSS 4.7 · linuxNVD modified 2026-10-14 13:10
Affected (CPE criteria) 1
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*