CVE-2023-53268: ASoC: fsl_mqs: move of_node_put() to the correct location
In the Linux kernel, the following vulnerability has been resolved:
ASoC: fsl_mqs: move of_node_put() to the correct location
of_node_put() should have been done directly after
mqs_priv->regmap = syscon_node_to_regmap(gpr_np);
otherwise it creates a reference leak on the success path.
To fix this, of_node_put() is moved to the correct location, and change
all the gotos to direct returns.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53268 is a Linux kernel bug in the fsl_mqs audio driver where a device-tree reference is not released on a successful path. The published impact is denial of service only, requiring local low-privileged access. It does not indicate data theft or integrity compromise.
Executive priority
Treat as a routine but real availability patching item. It is not cited as remotely exploitable or actively exploited, but local denial-of-service risk matters for shared, embedded, or appliance-like Linux systems using this driver.
Technical view
The issue is a reference leak caused by of_node_put() being called in the wrong location after syscon_node_to_regmap(gpr_np). Linux resolved it by moving of_node_put() and replacing goto cleanup paths with direct returns. CVSS 3.1 is 5.5: local, low complexity, low privileges, no user interaction, availability impact high.
Likely exposure
Exposure appears limited to Linux kernels containing the affected fsl_mqs ASoC driver code path. Systems without that driver enabled or reachable local users are lower concern. The source bundle lists Linux kernel versions and stable commits but does not identify distributions or appliances.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. The CVSS vector requires local access with low privileges. No exploit method, public weaponization, or remote attack path is cited in the provided sources.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. The vulnerability is described as a success-path reference leak, with availability impact only. Do not assume affected distributions, exploitability beyond local low-privileged access, or specific mitigations absent vendor guidance.
Mitigation direction
Update to a vendor kernel containing the referenced Linux stable fixes.
If no package is available, ask the vendor about backport status.
Prioritize systems with the fsl_mqs ASoC driver enabled.
Reduce unnecessary local user access on affected systems.
Track distribution advisories for package-specific fixed versions.
Validation and detection
Inventory Linux kernel versions against vendor advisories and the listed stable commits.
Check whether the fsl_mqs ASoC driver is built or loaded.
Confirm the deployed kernel includes the relevant upstream fix commit.
Review local-user exposure on systems requiring the affected driver.
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-2023-53268 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.