From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89594: hsi: omap_ssi_core: fix missing DMA mask setup for SSI controller device
Date: Fri, 11 Sep 2026 21:44:43 +0200 [thread overview]
Message-ID: <2026091131-CVE-2026-89594-c472@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-89594 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit f959dcd6ddfd29235030e8026471ac1b022ad2b0 and fixed in 6.12.109 with commit e8d47e309c704df95816e7442f05947424d8b33f
Issue introduced in 5.10 with commit f959dcd6ddfd29235030e8026471ac1b022ad2b0 and fixed in 6.18.50 with commit 4e019e5e247bfe877fdf288f2d6ec1b4c850c7c6
Issue introduced in 5.10 with commit f959dcd6ddfd29235030e8026471ac1b022ad2b0 and fixed in 7.2.4 with commit fbffbfdae55954213fea99c5c9856c48dc705019
Issue introduced in 5.10 with commit f959dcd6ddfd29235030e8026471ac1b022ad2b0 and fixed in 7.3-rc1 with commit e81250ec6b69248b00d38c523dc6a13efaf38aab
Issue introduced in 5.9.2 with commit 4e57482e8440fac7137832629109730ea4b267aa
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89594
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/hsi/controllers/omap_ssi_core.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e8d47e309c704df95816e7442f05947424d8b33f
https://git.kernel.org/stable/c/4e019e5e247bfe877fdf288f2d6ec1b4c850c7c6
https://git.kernel.org/stable/c/fbffbfdae55954213fea99c5c9856c48dc705019
https://git.kernel.org/stable/c/e81250ec6b69248b00d38c523dc6a13efaf38aab
reply other threads:[~2026-09-11 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091131-CVE-2026-89594-c472@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox