In the Linux kernel, the following vulnerability has been resolved: clk:
Get runtime PM before walking tree for clk_summary Similar to the previous
commit, we should make sure that all devices are runtime resumed before
printing the clk_summary through debugfs. Failure to do so would result in
a deadlock if the thread is resuming a device to print clk state and that
device is also runtime resuming in another thread, e.g the screen is
turning on and the display driver is starting up. We remove the calls to
clk_pm_runtime_{get,put}() in this path because they’re superfluous now
that we know the devices are runtime resumed. This also squashes a bug
where the return value of clk_pm_runtime_get() wasn’t checked, leading to
an RPM count underflow on error paths.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 14.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 16.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
git.kernel.org/linus/9d1e795f754db1ac3344528b7af0b17b8146f321 (6.9-rc5)
git.kernel.org/stable/c/2c077fdfd09dffb31a890e5095c8ab205138a42e
git.kernel.org/stable/c/83ada89e4a86e2b28ea2b5113c76d6dc7560a4d0
git.kernel.org/stable/c/9d1e795f754db1ac3344528b7af0b17b8146f321
git.kernel.org/stable/c/b457105309d388e4081c716cf7b81d517ff74db4
launchpad.net/bugs/cve/CVE-2024-27003
nvd.nist.gov/vuln/detail/CVE-2024-27003
security-tracker.debian.org/tracker/CVE-2024-27003
www.cve.org/CVERecord?id=CVE-2024-27003