CVE-2022-48629
published 2024-03-05CVE-2022-48629: In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in…
PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.53%
41.9th percentile
In the Linux kernel, the following vulnerability has been resolved:
crypto: qcom-rng - ensure buffer for generate is completely filled
The generate function in struct rng_alg expects that the destination
buffer is completely filled if the function returns 0. qcom_rng_read()
can run into a situation where the buffer is partially filled with
randomness and the remaining part of the buffer is zeroed since
qcom_rng_generate() doesn't check the return value. This issue can
be reproduced by running the following from libkcapi:
kcapi-rng -b 9000000 > OUTFILE
The generated OUTFILE will have three huge sections that contain all
zeros, and this is caused by the code where the test
'val & PRNG_STATUS_DATA_AVAIL' fails.
Let's fix this issue by ensuring that qcom_rng_read() always returns
with a full buffer if the function returns success. Let's also have
qcom_rng_generate() return the correct value.
Here's some statistics from the ent project
(https://www.fourmilab.ch/random/) that shows information about the
quality of the generated numbers:
$ ent -c qcom-random-before
Value Char Occurrences Fraction
0 606748 0.067416
1 33104 0.003678
2 33001 0.003667
...
253 � 32883 0.003654
254 � 33035 0.003671
255 � 33239 0.003693
Total: 9000000 1.000000
Entropy = 7.811590 bits per byte.
Optimum compression would reduce the size
of this 9000000 byte file by 2 percent.
Chi square distribution for 9000000 samples is 9329962.81, and
randomly would exceed this value less than 0.01 percent of the
times.
Arithmetic mean value of data bytes is 119.3731 (127.5 = random).
Monte Carlo value for Pi is 3.197293333 (error 1.77 percent).
Serial correlation coefficient is 0.159130 (totally uncorrelated =
0.0).
Without this patch, the results of the chi-square test is 0.01%, and
the numbers are certainly not random according to ent's project page.
The results improve with this patch:
$ ent -c qcom-random-after
Value Char Occurrences Fraction
0 35432 0.003937
1 35127 0.003903
2 35424 0.003936
Affected
25 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.18-1 (bookworm) | linux 5.16.18-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= ceec5f5b59882b871a722ca4d49b767a09a4bde9 < a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d | a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d |
| linux | linux | >= ceec5f5b59882b871a722ca4d49b767a09a4bde9 < 184f7bd08ce56f003530fc19f160d54e75bf5c9d | 184f7bd08ce56f003530fc19f160d54e75bf5c9d |
| linux | linux | >= ceec5f5b59882b871a722ca4d49b767a09a4bde9 < 0f9b7b8df17525e464294c916acc8194ce38446b | 0f9b7b8df17525e464294c916acc8194ce38446b |
| linux | linux | >= ceec5f5b59882b871a722ca4d49b767a09a4bde9 < ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd | ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd |
| linux | linux | >= ceec5f5b59882b871a722ca4d49b767a09a4bde9 < 485995cbc98a4f77cfd4f8ed4dd7ff8ab262964d | 485995cbc98a4f77cfd4f8ed4dd7ff8ab262964d |
| linux | linux | >= ceec5f5b59882b871a722ca4d49b767a09a4bde9 < a680b1832ced3b5fa7c93484248fd221ea0d614b | a680b1832ced3b5fa7c93484248fd221ea0d614b |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.113-1 | 5.10.113-1 |
| linux | linux_kernel | >= 0 < 5.16.18-1 | 5.16.18-1 |
| linux | linux_kernel | >= 0 < 5.16.18-1 | 5.16.18-1 |
| linux | linux_kernel | >= 0 < 5.16.18-1 | 5.16.18-1 |
| linux | linux_kernel | >= 4.19 < 4.19.236 | 4.19.236 |
| linux | linux_kernel | >= 4.20 < 5.4.187 | 5.4.187 |
| linux | linux_kernel | >= 5.11 < 5.15.31 | 5.15.31 |
| linux | linux_kernel | >= 5.16 < 5.16.17 | 5.16.17 |
| linux | linux_kernel | >= 5.5 < 5.10.108 | 5.10.108 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-48629: In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate fu
osv·2024-03-05·CVSS 5.5
CVE-2022-48629 [MEDIUM] CVE-2022-48629: In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate fu
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full b
GHSA
GHSA-2689-83hc-5vvp: In the Linux kernel, the following vulnerability has been resolved:
crypto: qcom-rng - ensure buffer for generate is completely filled
The generate
ghsa_unreviewed·2024-03-05
CVE-2022-48629 [MEDIUM] GHSA-2689-83hc-5vvp: In the Linux kernel, the following vulnerability has been resolved:
crypto: qcom-rng - ensure buffer for generate is completely filled
The generate
In the Linux kernel, the following vulnerability has been resolved:
crypto: qcom-rng - ensure buffer for generate is completely filled
The generate function in struct rng_alg expects that the destination
buffer is completely filled if the function returns 0. qcom_rng_read()
can run into a situation where the buffer is partially filled with
randomness and the remaining part of the buffer is zeroed since
qcom_rng_generate() doesn't check the return value. This issue can
be reproduced by running the following from libkcapi:
kcapi-rng -b 9000000 > OUTFILE
The generated OUTFILE will have three huge sections that contain all
zeros, and this is caused by the code where the test
'val & PRNG_STATUS_DATA_AVAIL' fails.
Let's fix this issue by ensuring that qcom_rng_read() always returns
with a f
Red Hat
kernel: crypto: qcom-rng - ensure buffer for generate is completely filled
vendor_redhat·2024-03-05·CVSS 5.5
CVE-2022-48629 [MEDIUM] CWE-99 kernel: crypto: qcom-rng - ensure buffer for generate is completely filled
kernel: crypto: qcom-rng - ensure buffer for generate is completely filled
In the Linux kernel, the following vulnerability has been resolved:
crypto: qcom-rng - ensure buffer for generate is completely filled
The generate function in struct rng_alg expects that the destination
buffer is completely filled if the function returns 0. qcom_rng_read()
can run into a situation where the buffer is partially filled with
randomness and the remaining part of the buffer is zeroed since
qcom_rng_generate() doesn't check the return value. This issue can
be reproduced by running the following from libkcapi:
kcapi-rng -b 9000000 > OUTFILE
The generated OUTFILE will have three huge sections that contain all
zeros, and this is caused by the code where the test
'val & PRNG_STATUS_DATA_AVAIL' fails.
Let's
Debian
CVE-2022-48629: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: qco...
vendor_debian·2022·CVSS 5.5
CVE-2022-48629 [MEDIUM] CVE-2022-48629: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: qco...
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full b
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0f9b7b8df17525e464294c916acc8194ce38446bhttps://git.kernel.org/stable/c/184f7bd08ce56f003530fc19f160d54e75bf5c9dhttps://git.kernel.org/stable/c/485995cbc98a4f77cfd4f8ed4dd7ff8ab262964dhttps://git.kernel.org/stable/c/a680b1832ced3b5fa7c93484248fd221ea0d614bhttps://git.kernel.org/stable/c/a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9dhttps://git.kernel.org/stable/c/ab9337c7cb6f875b6286440b1adfbeeef2b2b2bdhttps://git.kernel.org/stable/c/0f9b7b8df17525e464294c916acc8194ce38446bhttps://git.kernel.org/stable/c/184f7bd08ce56f003530fc19f160d54e75bf5c9dhttps://git.kernel.org/stable/c/485995cbc98a4f77cfd4f8ed4dd7ff8ab262964dhttps://git.kernel.org/stable/c/a680b1832ced3b5fa7c93484248fd221ea0d614bhttps://git.kernel.org/stable/c/a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9dhttps://git.kernel.org/stable/c/ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd
2024-03-05
Published