All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80834: crypto: sun8i-ce - Remove crypto_rng interface
Date: Fri,  4 Sep 2026 17:53:01 +0200	[thread overview]
Message-ID: <2026090456-CVE-2026-80834-e881@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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

crypto: sun8i-ce - Remove crypto_rng interface

Since the crypto_rng interface for hardware PRNGs is unused and is
redundant with hwrng and the actual Linux RNG, it's being phased out.
Most drivers for it were already removed.  Go ahead and remove the
sun8i-ce support which is one of the only remaining ones.

Note that the sun8i-ce support for hwrng remains in place.  That is the
interface that actually matters.

As usual for crypto_rng, this driver was also buggy: its ->generate()
function had a use-after-free vulnerability due to using
wait_for_completion_interruptible_timeout() without handling shutting
down the DMA operation if a signal is sent.  There's no point in fixing
this separately only to remove the code anyway, so this commit is marked
with Fixes and Cc stable.

The Linux kernel CVE team has assigned CVE-2026-80834 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.10 with commit 5eb7e946888493959b1c393144934afcbcd0cfc1 and fixed in 7.2.3 with commit 1017f987c5f0841f00408a78f947990c9d84b346
	Issue introduced in 5.10 with commit 5eb7e946888493959b1c393144934afcbcd0cfc1 and fixed in 7.3-rc1 with commit 011556f71d094da61379ae3672692cae2795304e

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-80834
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/allwinner/Kconfig
	drivers/crypto/allwinner/sun8i-ce/Makefile
	drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c
	drivers/crypto/allwinner/sun8i-ce/sun8i-ce-prng.c
	drivers/crypto/allwinner/sun8i-ce/sun8i-ce.h


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/1017f987c5f0841f00408a78f947990c9d84b346
	https://git.kernel.org/stable/c/011556f71d094da61379ae3672692cae2795304e

                 reply	other threads:[~2026-09-04 15:55 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=2026090456-CVE-2026-80834-e881@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.