mmc: davinci: avoid NULL deref of host->data in IRQ handler
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f216cf00e829895ff49bdf695c944915e59bd698, Kernel 3c5e3e5badbf0592332887d12db02458323682c3, Kernel 4f28846aaf8db9668e338b8987973f8935edff34 and 10 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <f216cf00e829895ff49bdf695c944915e59bd698, >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <3c5e3e5badbf0592332887d12db02458323682c3, >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <4f28846aaf8db9668e338b8987973f8935edff34, >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <51738de7dd5f8e8b33dfc07ef85bc06d3bf41e96, >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <5b7e151fe9ea9311ba601849aaecdc4fc97fd577, >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <a01cedf230dc0fcd55b994f5e548d3982ba4c732, >=b4cff4549b7a8c5fc8b88e3493b6287555f0512c <a0cde8d70d64c1a75fbd57f01d9f2d7cccac8319, =2.6.33 | f216cf00e829895ff49bdf695c944915e59bd698, 3c5e3e5badbf0592332887d12db02458323682c3, 4f28846aaf8db9668e338b8987973f8935edff34, 51738de7dd5f8e8b33dfc07ef85bc06d3bf41e96, 5b7e151fe9ea9311ba601849aaecdc4fc97fd577, a01cedf230dc0fcd55b994f5e548d3982ba4c732, a0cde8d70d64c1a75fbd57f01d9f2d7cccac8319 |
| linux-kernel: Kernel | >=5.11.0 <5.15.222, >=5.16.0 <6.1.189, >=6.13.0 <6.18.53, >=6.2.0 <6.6.158, >=6.7.0 <6.12.111, >=2.6.33 <5.10.271 | 5.15.222, 6.1.189, 6.18.53, 6.6.158, 6.12.111, 5.10.271 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket