CVE-2026-89594: hsi: omap_ssi_core: fix missing DMA mask setup for SSI controller device

Published Sep 11, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

hsi: omapssicore: fix missing DMA mask setup for SSI controller device

The OMAP SSI driver uses a synthetic HSI controller device allocated via hsialloccontroller(), 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, dmamapsg() and related helpers now require a valid dmamask 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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Explicitly initialize/setup the embedded SSI controller device's 32-bit DMA mask during initialization (hsi_alloc_controller/SSI controller device allocation) so it matches the hardware device DMA mask setup path and avoids crash/trigger warnings during dma_map_sg() DMA mapping.

    Linux kernel OMAP SSI driver (hsi: omap_ssi_core) DMA mask (dma_mask) for SSI controller device = 32-bit (initialized to match hardware)

Event History

Sep 11, 2026
CVE Published
via MITRE·07:44 PM
Data Sourced
via MITRE·07:44 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel OMAP SSI driver are affected when the driver performs DMA mapping for its synthetic HSI controller device. The issue is tied to that driver's controller initialization path rather than normal OF or platform-device initialization.

2

What conditions trigger the failure?

The failure can occur when DMA mapping operations such as dma_map_sg() are attempted without a valid DMA mask on the SSI controller device. Recent DMA API hardening makes the missing mask capable of causing warnings or a driver crash.

3

What is the mitigation if an update cannot be applied immediately?

The provided data identifies the required code-level mitigation: initialize the SSI controller device DMA mask explicitly to 32 bits, matching the hardware capability. No runtime configuration workaround is described.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203