From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-45854: crypto: inside-secure/eip93 - unregister only available algorithm
Date: Wed, 27 May 2026 14:18:16 +0200 [thread overview]
Message-ID: <2026052709-CVE-2026-45854-1df1@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: inside-secure/eip93 - unregister only available algorithm
EIP93 has an options register. This register indicates which crypto
algorithms are implemented in silicon. Supported algorithms are
registered on this basis. Unregister algorithms on the same basis.
Currently, all algorithms are unregistered, even those not supported
by HW. This results in panic on platforms that don't have all options
implemented in silicon.
The Linux kernel CVE team has assigned CVE-2026-45854 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 9739f5f93b7806a684713ba42e6ed2d1df7c8100 and fixed in 6.18.14 with commit 243d642ff5809811208fa1707b7ab8a6ab4b1d68
Issue introduced in 6.15 with commit 9739f5f93b7806a684713ba42e6ed2d1df7c8100 and fixed in 6.19.4 with commit 4c1c5a1d720fdacea060e106c7dd79417243d121
Issue introduced in 6.15 with commit 9739f5f93b7806a684713ba42e6ed2d1df7c8100 and fixed in 7.0 with commit 0ceeadc7b53a041d89d5843f6bf0ccb7c98b0b4f
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-45854
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/crypto/inside-secure/eip93/eip93-main.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/243d642ff5809811208fa1707b7ab8a6ab4b1d68
https://git.kernel.org/stable/c/4c1c5a1d720fdacea060e106c7dd79417243d121
https://git.kernel.org/stable/c/0ceeadc7b53a041d89d5843f6bf0ccb7c98b0b4f
reply other threads:[~2026-05-27 12:21 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=2026052709-CVE-2026-45854-1df1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.