CVE-2025-38401: mtk-sd: Prevent memory corruption from DMA map failure
In the Linux kernel, the following vulnerability has been resolved:
mtk-sd: Prevent memory corruption from DMA map failure
If msdc_prepare_data() fails to map the DMA region, the request is
not prepared for data receiving, but msdc_start_data() proceeds
the DMA with previous setting.
Since this will lead a memory corruption, we have to stop the
request operation soon after the msdc_prepare_data() fails to
prepare it.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s MediaTek SD-card driver can corrupt kernel memory when a data-transfer setup fails but the driver continues using old DMA settings. Successful exploitation requires local access under the supplied CVSS assessment, but impact could include data disclosure, system compromise, or a crash.
Executive priority
Treat this as a high-priority kernel maintenance issue for affected MediaTek-based systems, especially shared devices or systems permitting local untrusted users. It is not presented as an internet-exploitable emergency or actively exploited threat. Establish exposure promptly, then deploy supported corrected kernels through normal expedited change controls.
Technical view
If msdc_prepare_data() cannot map a DMA region, the request remains unprepared. msdc_start_data() nevertheless starts DMA using settings from a previous request, creating a kernel-memory corruption condition. The supplied CVSS 3.1 score is 7.8: local vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on systems running an affected Linux release where the mtk-sd driver supports relevant MediaTek SD hardware. The supplied version data spans multiple kernel branches but is not sufficiently clear to determine every vulnerable or fixed package version. Remote-only systems have reduced direct exposure because the rated attack vector is local.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not identified as being in KEV. The CVSS assessment indicates a local attacker with low privileges could potentially trigger high-impact memory corruption without user interaction. No public exploit or demonstrated exploitation is established by the supplied evidence.
Researcher notes
The failure path permits DMA to proceed with stale configuration after mapping fails. The supplied affected-version records are ambiguous because they mix release versions and repeated commit identifiers. Branch-level remediation should therefore be confirmed by commit inclusion or distribution advisories. The bundle does not identify a CWE, trigger conditions beyond DMA mapping failure, proof of concept, or exploitation telemetry.
Mitigation direction
Apply a vendor-supported kernel update containing the appropriate referenced stable fix.
Confirm the corrected kernel is installed and active after rebooting.
Prioritize systems using the mtk-sd driver on relevant MediaTek hardware.
If updates are unavailable, consult Linux or distribution guidance for supported mitigations.
Validation and detection
Inventory running kernel versions and identify systems loading the mtk-sd driver.
Map each kernel branch to the applicable referenced stable commit.
Verify distribution packages include the fix; version numbers alone may be insufficient.
After updating, confirm systems booted into the corrected kernel.
Monitor kernel logs for DMA, mtk-sd, memory-corruption, or unexpected crash events.
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-38401 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
1ADP providers
11Source 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.