CVE-2022-49621: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: cpufreq: pmac32-cpufreq: Fix refcount leak bug In pmac_cpufreq_init_MacRISC3(), we need to add corresponding of_node_put() for the three node pointers whose refcount have been incremented by of_find_node_by_name().
AI Analysis
Technical Summary
CVE-2022-49621 is a vulnerability identified in the Linux kernel specifically related to the cpufreq subsystem for the pmac32 architecture (Power Macintosh 32-bit). The issue arises from a reference count leak in the function pmac_cpufreq_init_MacRISC3(). Within this function, three node pointers obtained via of_find_node_by_name() have their reference counts incremented but are not properly decremented by corresponding of_node_put() calls. This leads to a resource management bug where the reference counts are not balanced, causing a leak. Reference count leaks in kernel code can result in resource exhaustion over time, potentially degrading system stability or causing denial of service (DoS) conditions. The vulnerability does not appear to allow direct code execution or privilege escalation but can impact system reliability. The affected versions are identified by a specific commit hash repeated multiple times, indicating a particular kernel source state before the fix. No known exploits are reported in the wild, and no CVSS score has been assigned yet. The fix involves adding the missing of_node_put() calls to properly release the node references and prevent the leak. This vulnerability is architecture-specific, affecting the pmac32 cpufreq driver, which is relevant to older Power Macintosh hardware running Linux kernels with this driver enabled.
Potential Impact
For European organizations, the impact of CVE-2022-49621 is likely limited due to the niche nature of the affected architecture (pmac32) and driver. Most modern Linux deployments in Europe run on x86_64, ARM, or other architectures rather than Power Macintosh 32-bit hardware. However, organizations that maintain legacy systems or specialized embedded devices using pmac32 Linux kernels could experience system instability or denial of service due to resource leaks if this vulnerability is exploited or triggered. This could affect availability of critical systems if the leak leads to kernel memory exhaustion or crashes. Since no privilege escalation or remote code execution is involved, confidentiality and integrity impacts are minimal. The lack of known exploits and the specialized hardware context reduce the immediate risk. Nonetheless, organizations with legacy Linux systems should prioritize patching to maintain system reliability and prevent potential DoS conditions.
Mitigation Recommendations
To mitigate CVE-2022-49621, organizations should: 1) Identify any Linux systems running on pmac32 architecture or using the pmac32 cpufreq driver. 2) Apply the official Linux kernel patches that add the missing of_node_put() calls in pmac_cpufreq_init_MacRISC3() as soon as they become available in stable kernel releases. 3) For legacy systems where kernel upgrades are challenging, consider recompiling the kernel with the patch applied manually. 4) Monitor system logs and kernel metrics for signs of resource leaks or instability related to cpufreq operations. 5) Implement routine kernel updates and maintain an inventory of hardware architectures in use to ensure timely vulnerability management. 6) If legacy pmac32 hardware is no longer critical, plan for migration to supported architectures to reduce exposure to such niche vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden
CVE-2022-49621: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: cpufreq: pmac32-cpufreq: Fix refcount leak bug In pmac_cpufreq_init_MacRISC3(), we need to add corresponding of_node_put() for the three node pointers whose refcount have been incremented by of_find_node_by_name().
AI-Powered Analysis
Technical Analysis
CVE-2022-49621 is a vulnerability identified in the Linux kernel specifically related to the cpufreq subsystem for the pmac32 architecture (Power Macintosh 32-bit). The issue arises from a reference count leak in the function pmac_cpufreq_init_MacRISC3(). Within this function, three node pointers obtained via of_find_node_by_name() have their reference counts incremented but are not properly decremented by corresponding of_node_put() calls. This leads to a resource management bug where the reference counts are not balanced, causing a leak. Reference count leaks in kernel code can result in resource exhaustion over time, potentially degrading system stability or causing denial of service (DoS) conditions. The vulnerability does not appear to allow direct code execution or privilege escalation but can impact system reliability. The affected versions are identified by a specific commit hash repeated multiple times, indicating a particular kernel source state before the fix. No known exploits are reported in the wild, and no CVSS score has been assigned yet. The fix involves adding the missing of_node_put() calls to properly release the node references and prevent the leak. This vulnerability is architecture-specific, affecting the pmac32 cpufreq driver, which is relevant to older Power Macintosh hardware running Linux kernels with this driver enabled.
Potential Impact
For European organizations, the impact of CVE-2022-49621 is likely limited due to the niche nature of the affected architecture (pmac32) and driver. Most modern Linux deployments in Europe run on x86_64, ARM, or other architectures rather than Power Macintosh 32-bit hardware. However, organizations that maintain legacy systems or specialized embedded devices using pmac32 Linux kernels could experience system instability or denial of service due to resource leaks if this vulnerability is exploited or triggered. This could affect availability of critical systems if the leak leads to kernel memory exhaustion or crashes. Since no privilege escalation or remote code execution is involved, confidentiality and integrity impacts are minimal. The lack of known exploits and the specialized hardware context reduce the immediate risk. Nonetheless, organizations with legacy Linux systems should prioritize patching to maintain system reliability and prevent potential DoS conditions.
Mitigation Recommendations
To mitigate CVE-2022-49621, organizations should: 1) Identify any Linux systems running on pmac32 architecture or using the pmac32 cpufreq driver. 2) Apply the official Linux kernel patches that add the missing of_node_put() calls in pmac_cpufreq_init_MacRISC3() as soon as they become available in stable kernel releases. 3) For legacy systems where kernel upgrades are challenging, consider recompiling the kernel with the patch applied manually. 4) Monitor system logs and kernel metrics for signs of resource leaks or instability related to cpufreq operations. 5) Implement routine kernel updates and maintain an inventory of hardware architectures in use to ensure timely vulnerability management. 6) If legacy pmac32 hardware is no longer critical, plan for migration to supported architectures to reduce exposure to such niche vulnerabilities.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-02-26T02:21:30.420Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982cc4522896dcbe463b
Added to database: 5/21/2025, 9:09:00 AM
Last enriched: 6/29/2025, 11:25:41 PM
Last updated: 7/31/2025, 1:06:54 PM
Views: 15
Related Threats
CVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.