Description
In the Linux kernel, the following vulnerability has been resolved: spi: Fix DMA mapping ownership on partial map failure If RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps TX but leaves tx_sg_mapped set. If TX mapping fails on a later transfer, mappings created for earlier transfers remain active. In both cases, cur_{tx,rx}_dma_dev have not yet been updated because they are assigned only after every transfer has been mapped. The subsequent spi_unmap_msg() may therefore unmap the TX mapping again or release earlier mappings using a NULL or stale device. Using a NULL device can trigger an oops. An empty SG table does not prevent the NULL dereference because dma_unmap_sg_attrs() accesses the device before checking the entry count. Publish both mapping devices before mapping starts and unwind all failures through __spi_unmap_msg(). This clears the mapping flags and releases each mapping once with the device that created it. Publishing the devices before the loop also refreshes them when no transfer needs mapping. No mapping flag is set in that case, so current users do not use the pointers as mapping owners.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
e289df82344fecc104ad8326b9ab6da612b9c899 to < cc8354213ad6bd5fb8cc05a3fa3701188d086626affectede289df82344fecc104ad8326b9ab6da612b9c899 to < a38051fa2ddedbc8ec15292c55e276880ec5b9a4affectede289df82344fecc104ad8326b9ab6da612b9c899 to < 5def8b6aaad44603740786262b95b6f77df52a1caffectede289df82344fecc104ad8326b9ab6da612b9c899 to < 367cea239fc93094e5c16a72724800e0358f5c46affected
Linux Linux
Default version status: affected
6.11affected0 to < 6.11unaffected6.12.110 to ≤ 6.12.*unaffected6.18.51 to ≤ 6.18.*unaffected7.2.5 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected