CVE-2022-49482: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe
In the Linux kernel, the following vulnerability has been resolved:
ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when done.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49482 is a Linux kernel reliability issue in the mxs-saif audio driver. A reference-counted device-tree node was not released correctly during driver probing. The published impact is local denial of service, not data theft or privilege escalation.
Executive priority
Treat as routine but real patching work. It is a medium-severity local availability issue with no provided evidence of active exploitation. Prioritize exposed multi-user or embedded Linux systems, then handle through normal kernel maintenance cycles.
Technical view
The Linux kernel mxs_saif_probe path calls of_parse_phandle(), which returns a node with an incremented refcount. The fix adds of_node_put() when done, preventing a refcount leak. CVSS 3.1 is 5.5 with local, low-complexity, low-privilege attack conditions and high availability impact.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions with the mxs-saif ASoC driver path present. The source bundle does not prove broad server exposure. Asset owners should map kernel versions and vendor backports rather than relying only on upstream version strings.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source reports active exploitation. The CVSS vector requires local access and low privileges, with availability impact only. Evidence for real-world exploitation is incomplete.
Researcher notes
The root issue is a missing of_node_put() after of_parse_phandle() in mxs_saif_probe. The source bundle gives upstream stable commit references but not complete distribution fix mapping, affected configuration requirements, or exploit proof.
Mitigation direction
Update to a vendor-supported kernel containing the referenced upstream stable fix.
Check Linux distribution advisories for the correct backported package version.
Prioritize systems where local users or workloads can reach the affected driver path.
Avoid direct wrangler or deployment assumptions; follow normal change control for kernel updates.
Validation and detection
Inventory Linux kernel versions and vendor package builds across affected assets.
Confirm whether the mxs-saif driver is built, loaded, or relevant to deployed hardware.
Verify the vendor kernel includes the upstream stable commit or equivalent backport.
Retest affected systems after patching for normal audio and boot behavior.
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-49482 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.