CVE-2026-97502

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mmc: davinci: avoid NULL deref of host-&gt;data in IRQ handler<br /> <br /> mmc_davinci_irq() returns early only when both host-&gt;cmd and<br /> host-&gt;data are NULL:<br /> <br /> if (host-&gt;cmd == NULL &amp;&amp; host-&gt;data == NULL) {<br /> ...<br /> return IRQ_NONE;<br /> }<br /> <br /> So we may legitimately reach the rest of the handler with<br /> host-&gt;data == NULL (and therefore data == NULL). The DATDNE branch<br /> already guards against this with an explicit "if (data != NULL)"<br /> check, but the subsequent TOUTRD ("read data timeout") and<br /> CRCWR/CRCRD ("data CRC error") branches dereference data<br /> unconditionally:<br /> <br /> if (qstatus &amp; MMCST0_TOUTRD) {<br /> data-&gt;error = -ETIMEDOUT; error = -EILSEQ; data is NULL, the kernel<br /> will crash inside the IRQ handler. smatch flags this:<br /> <br /> drivers/mmc/host/davinci_mmc.c:933 mmc_davinci_irq() error: we<br /> previously assumed &amp;#39;data&amp;#39; could be null (see line 914)<br /> <br /> Gate both branches on a non-NULL data, matching the existing pattern<br /> used by the DATDNE branch.<br /> <br /> No functional change for callers where data is non-NULL, which is<br /> the only case in which these branches did meaningful work before<br /> this change.