Linux Kernel up to 5.4.203/5.10.128/5.15.52/5.18.9 of_get_devfreq_events/of_get_child_by_name reference count

Summaryinfo

A vulnerability marked as problematic has been reported in Linux Kernel up to 5.4.203/5.10.128/5.15.52/5.18.9. This vulnerability affects the function of_get_devfreq_events/of_get_child_by_name. The manipulation leads to reference count. This vulnerability is referenced as CVE-2022-49668. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 5.4.203/5.10.128/5.15.52/5.18.9. This issue affects the function of_get_devfreq_events/of_get_child_by_name. The manipulation with an unknown input leads to a reference count vulnerability. Using CWE to declare the problem leads to CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. This function only calls of_node_put() in normal path, missing it in error paths. Add missing of_node_put() to avoid refcount leak.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2022-49668 since 02/26/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 237099 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:01600-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.204, 5.10.129, 5.15.53 or 5.18.10 eliminates this vulnerability. Applying the patch bdecd912e99acfd61507f1720d3f4eed1b3418d8/e65027fdebbacd40595e96ef7b5d2418f71bddf2/01121e39ef537289926ae6f5374dce92c796d863/194781229d4cbc804b8ded13156eb8addce87d6c/f44b799603a9b5d2e375b0b2d54dd0b791eddfc2 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (237099). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.4.203
• 5.10.128
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.15.33
• 5.15.34
• 5.15.35
• 5.15.36
• 5.15.37
• 5.15.38
• 5.15.39
• 5.15.40
• 5.15.41
• 5.15.42
• 5.15.43
• 5.15.44
• 5.15.45
• 5.15.46
• 5.15.47
• 5.15.48
• 5.15.49
• 5.15.50
• 5.15.51
• 5.15.52
• 5.18.0
• 5.18.1
• 5.18.2
• 5.18.3
• 5.18.4
• 5.18.5
• 5.18.6
• 5.18.7
• 5.18.8
• 5.18.9

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion