CVE-2022-49477: ASoC: samsung: Fix refcount leak in aries_audio_probe
In the Linux kernel, the following vulnerability has been resolved:
ASoC: samsung: Fix refcount leak in aries_audio_probe
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when done.
If extcon_find_edev_by_node() fails, it doesn't call of_node_put()
Calling of_node_put() after extcon_find_edev_by_node() to fix this.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a resource leak in Samsung Aries audio driver probing. The main business risk is local denial of service, not data theft. It matters most for systems running affected kernel versions with this driver path present. No provided source shows active exploitation.
Executive priority
Treat as a moderate availability risk. Patch through the normal kernel maintenance cycle, faster for devices using the affected Samsung audio driver. It does not currently justify emergency response based on the provided evidence.
Technical view
aries_audio_probe calls of_parse_phandle(), which increments a device-tree node reference. If extcon_find_edev_by_node() fails, the reference was not released with of_node_put(), creating a refcount leak. CVSS 3.1 is 5.5 with local access, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most likely on Linux systems using affected kernels in the recorded ranges and Samsung Aries ASoC audio support. General servers without this driver path are less likely exposed, but kernel package provenance should be checked.
Exploitation context
The provided data marks this as not in KEV and includes no cited evidence of active exploitation. The CVSS vector indicates local, low-privileged exploitation with availability impact only. Evidence is insufficient to claim remote risk or data compromise.
Researcher notes
The issue is a missing reference release after of_parse_phandle() in aries_audio_probe. The fix is the addition of of_node_put() after extcon_find_edev_by_node(). Confirm exposure by source/config review, not by assuming all Linux hosts are affected.
Mitigation direction
Update affected Linux kernels to vendor-supported fixed builds.
Confirm distro packages include one of the referenced stable fixes.
Prioritize systems where Samsung Aries ASoC audio support is enabled.
Follow Linux distribution or device vendor guidance for backported fixes.
Do not deploy direct kernel changes without normal regression testing.
Validation and detection
Inventory running kernel versions across Linux assets.
Map kernel packages against the affected version records.
Check whether the referenced stable commits are present or backported.
Review kernel configuration for Samsung Aries ASoC audio support.
Run normal service availability regression tests after patching.
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-49477 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.