mmc: davinci: avoid NULL deref of host->data in IRQ handler
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in 51738de7dd5f8e8b33dfc07ef85bc06d3bf41e96; From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in f216cf00e829895ff49bdf695c944915e59bd698; From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in a0cde8d70d64c1a75fbd57f01d9f2d7cccac8319; From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in 3c5e3e5badbf0592332887d12db02458323682c3; From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in a01cedf230dc0fcd55b994f5e548d3982ba4c732; From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in 5b7e151fe9ea9311ba601849aaecdc4fc97fd577; From b4cff4549b7a8c5fc8b88e3493b6287555f0512c · fixed in 4f28846aaf8db9668e338b8987973f8935edff34
- Linux Linux
2.6.33
- KernelLinux
From 2.6.33 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53
References 7
git.kernel.org
- stable/c/51738de7dd5f8e8b33dfc07ef85bc06d3bf41e96
- stable/c/f216cf00e829895ff49bdf695c944915e59bd698
- stable/c/a0cde8d70d64c1a75fbd57f01d9f2d7cccac8319
- stable/c/3c5e3e5badbf0592332887d12db02458323682c3
- stable/c/a01cedf230dc0fcd55b994f5e548d3982ba4c732
- stable/c/5b7e151fe9ea9311ba601849aaecdc4fc97fd577
- stable/c/4f28846aaf8db9668e338b8987973f8935edff34