Linux Kernel up to 5.18.7 of_find_matching_node reference count

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 4.19.249/5.4.201/5.10.126/5.15.50/5.18.7. This affects the function of_find_matching_node. Such manipulation leads to reference count. This vulnerability is referenced as CVE-2022-49678. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 4.19.249/5.4.201/5.10.126/5.15.50/5.18.7. It has been rated as critical. Affected by this issue is the function of_find_matching_node. 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. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. In brcmstb_init_sram, it pass dn to of_address_to_resource(), of_address_to_resource() will call of_find_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node().

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2022-49678 since 02/26/2025. Technical details are known, but there is no available exploit.

Upgrading to version 4.19.250, 5.4.202, 5.10.127, 5.15.51 or 5.18.8 eliminates this vulnerability. Applying the patch 4f5877bdf7b593e988f1924f4c3df6523f80b39c/734a4d15142bb4c8ecad2d8ec70d7564e78ae34d/30bbfeb480ae8b5ee43199d72417b232590440c2/10ba9d499a9fd82ed40897e734ba19870a879407/dcafd5463d8f20c4f90ddc138a5738adb99f74c8/37d838de369b07b596c19ff3662bf0293fdb09ee 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.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.19.249
• 5.4.201
• 5.10.126
• 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.18.0
• 5.18.1
• 5.18.2
• 5.18.3
• 5.18.4
• 5.18.5
• 5.18.6
• 5.18.7

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 best quality of vulnerability data, you may have to visit VulDB.

Discussion