hsi: omap_ssi_core: fix missing DMA mask setup for SSI controller device
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f959dcd6ddfd29235030e8026471ac1b022ad2b0 · < 4e019e5e247bfe877fdf288f2d6ec1b4c850c7c6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
hsi: omap_ssi_core: fix missing DMA mask setup for SSI controller device
The OMAP SSI driver uses a synthetic HSI controller device allocated via hsi_alloc_controller(), which does not go through the normal OF/platform device initialization path.
As a result, the embedded struct device does not have a DMA mask initialized by default.
After recent DMA API hardening changes, dma_map_sg() and related helpers now require a valid dma_mask to be present, otherwise the driver may crash or trigger warnings when attempting DMA mapping operations.
Fix this by explicitly initializing the DMA mask for the SSI controller device and setting a 32-bit DMA mask, which matches the hardware capabilities.
From the CVE record · Linux
The Linux kernel OMAP SSI driver does not initialize the DMA mask for its synthetic HSI controller device. After DMA API hardening changes, DMA mapping may crash the driver or trigger warnings. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the OMAP SSI driver should check their systems; affected versions are not specified.