accel/amdxdna: Fix race condition when checking rpm_on
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.19.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3bdd26582d026bdd86aa76f03989a1137b2490a0 · fixed in a82142af837f67a3f0a257a6dc355448ace58926; From 063db451832b8849faf1b0b8404b3a6a39995b29 · fixed in e7cb75b6a5127d78298e39750b4f3185eca0dafc; From 063db451832b8849faf1b0b8404b3a6a39995b29 · fixed in 00ffe45ece80160aef446d74ded906352f21dd72
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 6.19.4