CVE-2025-38573: spi: cs42l43: Property entry should be a null-terminated array
In the Linux kernel, the following vulnerability has been resolved:
spi: cs42l43: Property entry should be a null-terminated array
The software node does not specify a count of property entries, so the
array must be null-terminated.
When unterminated, this can lead to a fault in the downstream cs35l56
amplifier driver, because the node parse walks off the end of the
array into unknown memory.
Security readout for executives and security teams
Plain-English summary
A Linux audio-driver configuration array lacks a required ending marker. Another amplifier driver may read beyond the array into unintended memory, causing a kernel fault and potentially exposing or altering data. Exploitation requires local access, but the supplied CVSS rates confidentiality and availability impact high.
Executive priority
Prioritize remediation for multi-user systems or devices where untrusted users can obtain local access and the relevant audio hardware is present. Treat as a scheduled high-priority kernel update, escalating if vendors confirm exposure. The current evidence does not support emergency, internet-wide response or claims of active exploitation.
Technical view
The cs42l43 SPI driver creates a software-node property array without null termination. Because no entry count is supplied, downstream cs35l56 parsing can walk beyond the array into unknown memory. The supplied CVSS 3.1 score is 7.3: local, low-complexity, low-privilege exploitation without user interaction.
Likely exposure
Exposure is limited to Linux systems combining an affected kernel build with the relevant cs42l43 and downstream cs35l56 audio-driver path. The bundle lists affected version markers including 6.11, 6.12.42, 6.15.10, 6.16.1, and 6.17, but does not provide sufficiently clear ranges for reliable inventory matching.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. The CVSS vector requires local, low-privileged access. Practical reachability also appears dependent on the relevant audio-driver and hardware configuration; the supplied evidence does not establish exploit reliability or observed attacks.
Researcher notes
The core defect is an unterminated property-entry array consumed without an explicit count, permitting an out-of-bounds walk. Four stable-kernel commits are cited as resolution references. Precise affected and fixed ranges, architecture applicability, exploitability details, and root-cause CWE classification are not established by the supplied bundle.
Mitigation direction
Update to a vendor-supported kernel containing the applicable stable fix commit.
Check distribution or device-vendor advisories for exact fixed package versions.
Prioritize systems exposing the relevant cs42l43 and cs35l56 driver path.
Restrict local account access until affected systems are updated.
Validation and detection
Record running kernel and vendor package versions on potentially affected systems.
Confirm whether cs42l43 and cs35l56 drivers and corresponding hardware are present.
Verify the installed kernel includes an applicable referenced stable commit.
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-2025-38573 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.