CVE-2022-49752: device property: fix of node refcount leak in fwnode_graph_get_next_endpoint()
In the Linux kernel, the following vulnerability has been resolved:
device property: fix of node refcount leak in fwnode_graph_get_next_endpoint()
The 'parent' returned by fwnode_graph_get_port_parent()
with refcount incremented when 'prev' is not NULL, it
needs be put when finish using it.
Because the parent is const, introduce a new variable to
store the returned fwnode, then put it before returning
from fwnode_graph_get_next_endpoint().
Security readout for executives and security teams
Plain-English summary
This Linux kernel bug can leak internal references while handling device-property graph endpoints. The stated impact is availability only: a local, low-privileged user could potentially contribute to a denial of service. The provided sources do not indicate data theft, data modification, or confirmed exploitation.
Executive priority
Handle through normal kernel patch governance, with higher priority for shared servers, appliances, or environments where local users can run code. There is no source-backed evidence of remote exploitation or active attacks.
Technical view
The issue is in fwnode_graph_get_next_endpoint(). When prev is non-NULL, fwnode_graph_get_port_parent() returns parent with an incremented refcount, but the function failed to release it before returning. Stable kernel commits correct the missing put path.
Likely exposure
Exposure is limited to affected Linux kernel versions and builds containing this device property code path. The bundle lists Linux 5.15, 5.15.91, 6.1.9, and 6.2 as affected-version markers, but distribution backport status must be verified separately.
Exploitation context
CVSS indicates local access, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact. CISA KEV is false in the bundle, and no cited source claims active exploitation.
Researcher notes
Evidence points to a reference-count leak, not memory corruption or privilege escalation. The source bundle lacks CWE mapping and distribution-specific fix metadata, so exposure validation should focus on kernel provenance and vendor backports.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on version numbers alone.
Restrict unnecessary local user access on systems awaiting kernel maintenance.
Prioritize shared or multi-user Linux hosts where local denial of service matters most.
Validation and detection
Inventory running Linux kernel versions across affected systems.
Confirm whether vendor kernel packages include the referenced stable commits.
Track distribution security advisories for CVE-2022-49752 status.
Validate that patched test systems remain stable after kernel update.
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-49752 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.