CVE-2023-53443: mfd: arizona: Use pm_runtime_resume_and_get() to prevent refcnt leak
In the Linux kernel, the following vulnerability has been resolved:
mfd: arizona: Use pm_runtime_resume_and_get() to prevent refcnt leak
In arizona_clk32k_enable(), we should use pm_runtime_resume_and_get()
as pm_runtime_get_sync() will increase the refcnt even when it
returns an error.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause an availability problem when a local user reaches the affected arizona MFD driver path. The bug is a runtime power-management reference count leak on error, not a data theft or privilege escalation issue based on the supplied CVSS vector.
Executive priority
Treat as a moderate Linux availability risk. It does not appear remotely exploitable from the supplied evidence, but exposed systems should receive normal kernel maintenance, especially where the affected driver is in use.
Technical view
In arizona_clk32k_enable(), pm_runtime_get_sync() increments the runtime PM reference count even when it returns an error. The resolved change uses pm_runtime_resume_and_get() to avoid leaking the reference count. The CVSS vector is local, low complexity, low privileges, no user interaction, availability high.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with the arizona MFD driver code present and reachable. The bundle lists Linux as affected across several kernel release ranges, but does not identify specific distributions or hardware products.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. The CVSS vector requires local access with low privileges and has no confidentiality or integrity impact, but could affect system availability.
Researcher notes
The evidence is limited to the CVE record and Linux stable commit references. No CWE, exploit detail, affected distributions, or product-specific advisories are provided in the bundle, so validation should focus on kernel lineage and backport status.
Mitigation direction
Apply vendor kernel updates that include the referenced Linux stable fixes.
Confirm downstream distribution kernels have backported the arizona runtime PM fix.
Prioritize systems where the arizona MFD driver is enabled or loaded.
If no vendor update is available, track vendor guidance for compensating controls.
Validation and detection
Inventory kernel versions against the affected ranges in the CVE record.
Check whether the arizona MFD driver is configured, built, or loaded.
Verify the kernel includes one of the referenced stable commits or an equivalent backport.
Review vendor advisories for distribution-specific package names and fixed builds.
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-53443 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.