CVE-2024-26787: mmc: mmci: stm32: fix DMA API overlapping mappings warning
In the Linux kernel, the following vulnerability has been resolved:
mmc: mmci: stm32: fix DMA API overlapping mappings warning
Turning on CONFIG_DMA_API_DEBUG_SG results in the following warning:
DMA-API: mmci-pl18x 48220000.mmc: cacheline tracking EEXIST,
overlapping mappings aren't supported
WARNING: CPU: 1 PID: 51 at kernel/dma/debug.c:568
add_dma_entry+0x234/0x2f4
Modules linked in:
CPU: 1 PID: 51 Comm: kworker/1:2 Not tainted 6.1.28 #1
Hardware name: STMicroelectronics STM32MP257F-EV1 Evaluation Board (DT)
Workqueue: events_freezable mmc_rescan
Call trace:
add_dma_entry+0x234/0x2f4
debug_dma_map_sg+0x198/0x350
__dma_map_sg_attrs+0xa0/0x110
dma_map_sg_attrs+0x10/0x2c
sdmmc_idma_prep_data+0x80/0xc0
mmci_prep_data+0x38/0x84
mmci_start_data+0x108/0x2dc
mmci_request+0xe4/0x190
__mmc_start_request+0x68/0x140
mmc_start_request+0x94/0xc0
mmc_wait_for_req+0x70/0x100
mmc_send_tuning+0x108/0x1ac
sdmmc_execute_tuning+0x14c/0x210
mmc_execute_tuning+0x48/0xec
mmc_sd_init_uhs_card.part.0+0x208/0x464
mmc_sd_init_card+0x318/0x89c
mmc_attach_sd+0xe4/0x180
mmc_rescan+0x244/0x320
DMA API debug brings to light leaking dma-mappings as dma_map_sg and
dma_unmap_sg are not correctly balanced.
If an error occurs in mmci_cmd_irq function, only mmci_dma_error
function is called and as this API is not managed on stm32 variant,
dma_unmap_sg is never called in this error path.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver flaw affecting the STM32 MMC/SD controller path. On certain error paths, DMA mappings are not properly released, which can trigger DMA API debug warnings and resource leakage. The sources do not provide a CVSS score, confirmed exploitation, or business-impact detail.
Executive priority
Treat this as a targeted embedded Linux maintenance issue unless your environment relies on STM32-based systems. There is insufficient source evidence to justify emergency response, but affected operational technology or appliance fleets should receive normal vendor patching attention.
Technical view
The issue is in the Linux mmc mmci stm32 driver. dma_map_sg and dma_unmap_sg are unbalanced when mmci_cmd_irq hits an error and the STM32 variant does not perform the unmap path. CONFIG_DMA_API_DEBUG_SG exposes overlapping mapping warnings on STM32MP257F-EV1 hardware.
Likely exposure
Exposure is most likely in Linux-based embedded or industrial systems using STM32 MMC/SD controller support. The bundle lists Linux kernel versions as affected and includes Debian LTS and Siemens advisories, but does not identify specific deployed products beyond those references.
Exploitation context
The CVE is not listed as CISA KEV, and the provided sources do not claim active exploitation or public exploit availability. Evidence points to a driver error-handling bug observed through kernel DMA debug instrumentation, not a documented remote attack path.
Researcher notes
The key evidence is the unbalanced DMA mapping/unmapping path in the STM32 mmci driver. The source bundle lacks CVSS, CWE, exploitability analysis, and product-specific impact detail, so exposure assessment depends heavily on kernel configuration, board hardware, and vendor backports.
Mitigation direction
Upgrade to a Linux kernel or vendor package containing the referenced stable fixes.
Follow Debian, Siemens, or device-vendor guidance for affected deployed systems.
Prioritize embedded systems using STM32 MMC/SD hardware paths.
Track vendor advisories where kernel versions are customized or backported.
Validation and detection
Inventory Linux kernel versions on STM32-based devices and appliances.
Check vendor advisories for whether the fix is backported to your build.
Confirm the relevant stable fix commit exists in the running kernel source package.
Review kernel logs for DMA-API overlapping mapping warnings where debug is enabled.
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-2024-26787 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.