85236 matches found
CVE-2026-80922
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random...
DEBIAN-CVE-2026-80922
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random...
CVE-2026-80922 crypto: qcom-rng - Allow zero as a random number
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random...
EUVD-2026-75099
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random...
CVE-2026-80922 crypto: qcom-rng - Allow zero as a random number
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random...
Linux Distros Unpatched Vulnerability : CVE-2026-80922
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to ...
PT-2026-89092
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the qcom-rng crypto component where zero was not allowed as a random number. Since zero is a valid random number, excluding it makes the output distinguishable from...
CVE-2026-62647
A vulnerability has been identified in Reyrolle 7SR5 All versions V2.70. A random number generator is used to generate security-relevant values such as session identifiers used for authentication purposes that is not initialized with a True Random Number Generator TRNG, resulting in a predictable...
CVE-2026-62647
Reyrolle 7SR5 (all versions prior to V2.70 ) contains a weak random number generator that is not seeded by a True Random Number Generator (TRNG), producing a predictable sequence of security-relevant values such as session identifiers. An unauthenticated remote attacker could predict these values...
CVE-2026-62647
A vulnerability has been identified in Reyrolle 7SR5 All versions V2.70. A random number generator is used to generate security-relevant values such as session identifiers used for authentication purposes that is not initialized with a True Random Number Generator TRNG, resulting in a predictable...
CVE-2026-79575: Use of Insufficiently Random Values
The JWT signing secret in yfexam-exam v2.0 is derived from the username and the current month instead of a random server-side key, making the secret key easily obtainable via a bruteforce attack...
Malicious code in dasnoo-random-word (npm)
The package dasnoo-random-word was found to contain malicious code. --- Credit: OpenSSF source...
SUSE CVE-2026-80835
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Remove cryptorng interface qcom-rng.c exposes the same hardware through two completely separate interfaces, cryptorng and hwrng. However, the implementation of this is buggy because it permits generation...
EUVD-2026-71501
In the Linux kernel, the following vulnerability has been resolved: crypto: xilinx-trng - Remove cryptorng interface Implementing the cryptorng interface has no purpose, as it isn't used in practice. It's being removed from other drivers too. Just remove it. This leaves hwrng, which is actually...
CVE-2026-80835
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Remove cryptorng interface qcom-rng.c exposes the same hardware through two completely separate interfaces, cryptorng and hwrng. However, the implementation of this is buggy because it permits generation...
EUVD-2026-71285
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Remove cryptorng interface qcom-rng.c exposes the same hardware through two completely separate interfaces, cryptorng and hwrng. However, the implementation of this is buggy because it permits generation...
CVE-2026-80835
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Remove cryptorng interface qcom-rng.c exposes the same hardware through two completely separate interfaces, cryptorng and hwrng. However, the implementation of this is buggy because it permits generation...
CVE-2026-80835 crypto: qcom-rng - Remove crypto_rng interface
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Remove cryptorng interface qcom-rng.c exposes the same hardware through two completely separate interfaces, cryptorng and hwrng. However, the implementation of this is buggy because it permits generation...
CVE-2026-80835 crypto: qcom-rng - Remove crypto_rng interface
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Remove cryptorng interface qcom-rng.c exposes the same hardware through two completely separate interfaces, cryptorng and hwrng. However, the implementation of this is buggy because it permits generation...
CVE-2026-80835
CVE-2026-80835 affects the Linux kernel 's qcom-rng crypto driver, which exposes a Qualcomm hardware RNG through two separate interfaces (crypto_rng and hwrng). The root cause is a lack of synchronization between qcom_rng_generate() and qcom_hwrng_read(), allowing concurrent access to the same ha...