dmaengine: zynqmp_dma: fix race between runtime PM and device removal
- 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.18.52, 7.2.6
- 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: dmaengine: zynqmp_dma: fix race between runtime PM and device removal In zynqmp_dma_remove(), runtime PM was disabled only after checking state and doing a manual suspend. This can race with runtime PM in the remove/unbind (rmmod) path. Disable runtime PM first, then suspend only if the device is not already suspended. To prevent any further runtime PM transitions.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 72dd8b2914b5db1dccf902971c2ea6b541711b28 · fixed in 32f69e6c95b59f9cfc649ebf352a204d23ba93d7; From 72dd8b2914b5db1dccf902971c2ea6b541711b28 · fixed in aec7cf9a5bd89047c58d5648bfce0b1bd19ba7d5; From 72dd8b2914b5db1dccf902971c2ea6b541711b28 · fixed in 516ba2d8b7aac4238f9fcbd58579c43c71b9b695
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6