accel/amdxdna: Fix race condition when checking rpm_on
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 00ffe45ece80160aef446d74ded906352f21dd72, Kernel e7cb75b6a5127d78298e39750b4f3185eca0dafc and Kernel a82142af837f67a3f0a257a6dc355448ace58926.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.19, >=063db451832b8849faf1b0b8404b3a6a39995b29 <00ffe45ece80160aef446d74ded906352f21dd72, >=063db451832b8849faf1b0b8404b3a6a39995b29 <e7cb75b6a5127d78298e39750b4f3185eca0dafc, >=3bdd26582d026bdd86aa76f03989a1137b2490a0 <a82142af837f67a3f0a257a6dc355448ace58926 | 00ffe45ece80160aef446d74ded906352f21dd72, e7cb75b6a5127d78298e39750b4f3185eca0dafc, a82142af837f67a3f0a257a6dc355448ace58926 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket