CVE-2022-49415: ipmi:ipmb: Fix refcount leak in ipmi_ipmb_probe
In the Linux kernel, the following vulnerability has been resolved:
ipmi:ipmb: Fix refcount leak in ipmi_ipmb_probe
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when done.
Add missing of_node_put() to avoid refcount leak.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49415 is a Linux kernel resource-management flaw in the IPMI IPMB driver. A device-tree node reference is acquired but not released, causing a reference-count leak. The public sources do not provide CVSS, a CWE, a demonstrated security impact, or evidence of active exploitation.
Executive priority
Treat this as a routine kernel maintenance item unless your environment relies heavily on IPMI/IPMB management paths. There is no sourced evidence of active exploitation, but kernel resource leaks can affect reliability and should be handled through normal patch cycles.
Technical view
The kernel fix adds a missing of_node_put() after of_parse_phandle() in ipmi_ipmb_probe. Without it, probing the IPMI IPMB path can leak a device-tree node reference. Sources identify affected Linux 5.18-era versions and stable commits that resolve the issue.
Likely exposure
Exposure appears limited to Linux systems where the IPMI IPMB driver probe path is present and exercised. The source bundle lists Linux 5.18 through 5.18.3 as affected, but does not name distributions, appliances, or downstream vendor packages.
Exploitation context
The CVE is not listed as KEV in the supplied data, and the sources do not state active exploitation or provide exploit details. The available evidence describes a kernel reference-count leak, not a confirmed remote attack path.
Researcher notes
Evidence is narrow: the public description only identifies a missing of_node_put() after of_parse_phandle() and provides stable commit references. No CVSS vector, CWE, attacker prerequisites, impact bounds, or distribution-specific status is included in the supplied sources.
Mitigation direction
Apply Linux kernel vendor updates containing the referenced stable fixes.
Check downstream distribution advisories for backported kernel patches.
Prioritize systems that use IPMI/IPMB or BMC-management features.
If updates are unavailable, follow vendor guidance for this driver path.
Validation and detection
Inventory Linux kernel versions against the affected range in vendor advisories.
Confirm whether IPMI IPMB driver support is enabled or deployed.
Verify patched kernels include the referenced stable commits or equivalent backports.
Review operational monitoring for unusual kernel resource growth on relevant systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49415 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 26, 2025, 02:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.