CVE-2023-53465: soundwire: qcom: fix storing port config out-of-bounds
In the Linux kernel, the following vulnerability has been resolved:
soundwire: qcom: fix storing port config out-of-bounds
The 'qcom_swrm_ctrl->pconfig' has size of QCOM_SDW_MAX_PORTS (14),
however we index it starting from 1, not 0, to match real port numbers.
This can lead to writing port config past 'pconfig' bounds and
overwriting next member of 'qcom_swrm_ctrl' struct. Reported also by
smatch:
drivers/soundwire/qcom.c:1269 qcom_swrm_get_port_config() error: buffer overflow 'ctrl->pconfig' 14 <= 14
Security readout for executives and security teams
Plain-English summary
A bounds error in the Linux Qualcomm SoundWire driver can overwrite adjacent kernel-driver data when port configuration is stored. Because successful abuse could affect confidentiality, integrity, and availability, it is rated high severity. Exposure depends on whether a system uses the affected Qualcomm SoundWire driver and an unfixed kernel.
Executive priority
Treat this as a high-priority kernel maintenance issue for Qualcomm-based Linux devices, especially shared or locally accessible systems. First establish driver use, then deploy a supported fixed kernel. Broad emergency action is not supported because no active exploitation evidence is provided and exposure appears hardware and driver dependent.
Technical view
The driver stores real port numbers beginning at index 1 in a 14-element pconfig array. Port 14 therefore writes beyond the array and into the next qcom_swrm_ctrl structure member. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, and potentially high system impact.
Likely exposure
Likely exposure is limited to Linux systems running affected kernel revisions with the Qualcomm SoundWire driver and relevant hardware or configuration. The supplied version data is ambiguous, so kernel provenance and backported fixes must be verified rather than relying only on version numbers.
Exploitation context
The source bundle does not identify public exploitation, exploit code, or active attacks, and the CVE is not listed as KEV. The CVSS vector indicates that exploitation would require local, low-privileged access. Whether the vulnerable path is practically reachable is not established by the supplied evidence.
Researcher notes
This is a one-based indexing mismatch: pconfig has 14 elements, but indexing follows port numbers starting at 1, allowing index 14 beyond valid indices 0–13. The reported consequence is corruption of the following qcom_swrm_ctrl member. No CWE, affected-range semantics, crash evidence, or demonstrated exploitation is supplied.
Mitigation direction
Install a vendor-supported kernel containing the applicable cited stable fix.
Check distribution advisories for backported fixes before judging exposure by version number.
Prioritize systems using Qualcomm SoundWire hardware or loading the qcom SoundWire driver.
Where patching is delayed, restrict unnecessary local accounts and privileged workload access.
Validation and detection
Record the running kernel version, package release, and distribution build identifier.
Determine whether the Qualcomm SoundWire driver is built, loaded, or used by present hardware.
Verify that the kernel source or vendor package includes an applicable cited fix commit.
Reassess exposure after kernel upgrades and confirm systems booted into the corrected kernel.
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-53465 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.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
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.