CVE-2026-97502: Linux Vulnerability

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.

Metrics

EPSS Probability

0.15%

4.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < 51738de7dd5f8e8b33dfc07ef85bc06d3bf41e96; >= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < f216cf00e829895ff49bdf695c944915e59bd698; >= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < a0cde8d70d64c1a75fbd57f01d9f2d7cccac8319; >= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < 3c5e3e5badbf0592332887d12db02458323682c3; >= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < a01cedf230dc0fcd55b994f5e548d3982ba4c732; >= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < 5b7e151fe9ea9311ba601849aaecdc4fc97fd577; >= b4cff4549b7a8c5fc8b88e3493b6287555f0512c, < 4f28846aaf8db9668e338b8987973f8935edff34
Linux	Linux	2.6.33

References

Timeline

Published: Sep 24, 2026
Last Modified: Oct 3, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-97502?

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.

How severe is CVE-2026-97502?

Severity scoring for CVE-2026-97502 is pending analysis. The EPSS model estimates a 0.15% probability of exploitation in the next 30 days.

How do I fix CVE-2026-97502?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →