mmc: davinci: avoid NULL deref of host->data in IRQ handler
Summary
| CVE | CVE-2026-97502 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-24 17:17:27 UTC |
| Updated | 2026-09-28 06:16:36 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: mmc: davinci: avoid NULL deref of host->data in IRQ handler mmc_davinci_irq() returns early only when both host->cmd and host->data are NULL: if (host->cmd == NULL && host->data == NULL) { ... return IRQ_NONE; } So we may legitimately reach the rest of the handler with host->data == NULL (and therefore data == NULL). The DATDNE branch already guards against this with an explicit "if (data != NULL)" check, but the subsequent TOUTRD ("read data timeout") and CRCWR/CRCRD ("data CRC error") branches dereference data unconditionally: if (qstatus & MMCST0_TOUTRD) { data->error = -ETIMEDOUT; <-- NULL deref ... davinci_abort_data(host, data); } if (qstatus & (MMCST0_CRCWR | MMCST0_CRCRD)) { data->error = -EILSEQ; <-- NULL deref ... } If either bit is set in qstatus while host->data is NULL, the kernel will crash inside the IRQ handler. smatch flags this: drivers/mmc/host/davinci_mmc.c:933 mmc_davinci_irq() error: we previously assumed 'data' could be null (see line 914) Gate both branches on a non-NULL data, matching the existing pattern used by the DATDNE branch. No functional change for callers where data is non-NULL, which is the only case in which these branches did meaningful work before this change. |
Risk And Classification
EPSS: 0.001550000 probability, percentile 0.039120000 (date 2026-09-29)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected b4cff4549b7a8c5fc8b88e3493b6287555f0512c a01cedf230dc0fcd55b994f5e548d3982ba4c732 git | Not specified |
| CNA | Linux | Linux | affected b4cff4549b7a8c5fc8b88e3493b6287555f0512c 5b7e151fe9ea9311ba601849aaecdc4fc97fd577 git | Not specified |
| CNA | Linux | Linux | affected b4cff4549b7a8c5fc8b88e3493b6287555f0512c 4f28846aaf8db9668e338b8987973f8935edff34 git | Not specified |
| CNA | Linux | Linux | affected 2.6.33 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.33 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/5b7e151fe9ea9311ba601849aaecdc4fc97fd577 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4f28846aaf8db9668e338b8987973f8935edff34 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a01cedf230dc0fcd55b994f5e548d3982ba4c732 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.