Bug 2528694 (CVE-2026-80835) - CVE-2026-80835 kernel: crypto: qcom-rng - Remove crypto_rng interface
Summary: CVE-2026-80835 kernel: crypto: qcom-rng - Remove crypto_rng interface
Keywords:
Status: NEW
Alias: CVE-2026-80835
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-04 16:24 UTC by OSIDB Bzimport
Modified: 2026-11-04 16:10 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-04 16:24:18 UTC
In the Linux kernel, the following vulnerability has been resolved:

crypto: qcom-rng - Remove crypto_rng interface

qcom-rng.c exposes the same hardware through two completely separate
interfaces, crypto_rng and hwrng.  However, the implementation of this
is buggy because it permits generation operations from these interfaces
to run concurrently with each other, accessing the same registers.  That
is, qcom_rng_generate() synchronizes with itself but not with
qcom_hwrng_read().  This results in potential repetition of output from
the RNG, output of non-random values, etc.

Fortunately, there's actually no point in hardware RNG drivers
implementing the crypto_rng interface.  It's not actually used by
anything besides the "rng" algorithm type of AF_ALG, which in turn is
not actually used in practice.  Other crypto_rng hardware drivers are
likewise being phased out, leaving just the hwrng support.

Thus, remove it to simplify the code and avoid conflict (and confusion)
with the hwrng interface which is the one that actually matters.


Note You need to log in before you can comment on or make changes to this bug.