cve/2024/CVE-2024-27003.md

### [CVE-2024-27003](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27003)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=1bb294a7981c%3C%2083ada89e4a86%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

In the Linux kernel, the following vulnerability has been resolved:clk: Get runtime PM before walking tree for clk_summarySimilar to the previous commit, we should make sure that all devices areruntime resumed before printing the clk_summary through debugfs. Failureto do so would result in a deadlock if the thread is resuming a deviceto print clk state and that device is also runtime resuming in anotherthread, e.g the screen is turning on and the display driver is startingup. We remove the calls to clk_pm_runtime_{get,put}() in this pathbecause they're superfluous now that we know the devices are runtimeresumed. This also squashes a bug where the return value ofclk_pm_runtime_get() wasn't checked, leading to an RPM count underflowon error paths.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/fkie-cad/nvd-json-data-feeds
Update Sat May 25 21:48:12 CEST 2024 2024-05-25 21:48:12 +02:00			`### [CVE-2024-27003](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27003)`
			`![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)`
			`![](https://img.shields.io/static/v1?label=Version&message=1bb294a7981c%3C%2083ada89e4a86%20&color=brighgreen)`
			`![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)`

			`### Description`

			In the Linux kernel, the following vulnerability has been resolved:clk: Get runtime PM before walking tree for clk_summarySimilar to the previous commit, we should make sure that all devices areruntime resumed before printing the clk_summary through debugfs. Failureto do so would result in a deadlock if the thread is resuming a deviceto print clk state and that device is also runtime resuming in anotherthread, e.g the screen is turning on and the display driver is startingup. We remove the calls to clk_pm_runtime_{get,put}() in this pathbecause they're superfluous now that we know the devices are runtimeresumed. This also squashes a bug where the return value ofclk_pm_runtime_get() wasn't checked, leading to an RPM count underflowon error paths.

			`### POC`

			`#### Reference`
			`No PoCs from references.`

			`#### Github`
			`- https://github.com/fkie-cad/nvd-json-data-feeds`