CVE-2022-48630
"Qualcomm crypto qcom-rng Looping Vulnerability"
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ The commit referenced in the Fixes tag removed the 'break' from the else branch in qcom_rng_read(), causing an infinite loop whenever 'max' is not a multiple of WORD_SZ. This can be reproduced e.g. by running: kcapi-rng -b 67 >/dev/null There are many ways to fix this without adding back the 'break', but they all seem more awkward than simply adding it back, so do just that. Tested on a machine with Qualcomm Amberwing processor.
INFO
Published Date :
March 5, 2024, 12:15 p.m.
Last Modified :
Feb. 3, 2025, 2:09 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the Linux kernel to a patched version.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-48630.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-48630 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-48630
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-48630 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-48630 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Feb. 03, 2025
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NIST CWE-835 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.236 up to (excluding) 4.19.245 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.187 up to (excluding) 5.4.196 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.108 up to (excluding) 5.10.118 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.31 up to (excluding) 5.15.42 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.17 up to (excluding) 5.17.10 *cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:5.18:rc9:*:*:*:*:*:* Changed Reference Type https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3 No Types Assigned https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3 Patch Changed Reference Type https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3 No Types Assigned https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3 Patch Changed Reference Type https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d No Types Assigned https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d Patch Changed Reference Type https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d No Types Assigned https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d Patch Changed Reference Type https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c No Types Assigned https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c Patch Changed Reference Type https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c No Types Assigned https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c Patch Changed Reference Type https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550 No Types Assigned https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550 Patch Changed Reference Type https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550 No Types Assigned https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550 Patch Changed Reference Type https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce No Types Assigned https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce Patch Changed Reference Type https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce No Types Assigned https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce Patch Changed Reference Type https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae No Types Assigned https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae Patch Changed Reference Type https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae No Types Assigned https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3 Added Reference https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d Added Reference https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c Added Reference https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550 Added Reference https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce Added Reference https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 28, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Mar. 05, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ The commit referenced in the Fixes tag removed the 'break' from the else branch in qcom_rng_read(), causing an infinite loop whenever 'max' is not a multiple of WORD_SZ. This can be reproduced e.g. by running: kcapi-rng -b 67 >/dev/null There are many ways to fix this without adding back the 'break', but they all seem more awkward than simply adding it back, so do just that. Tested on a machine with Qualcomm Amberwing processor. Added Reference Linux https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550 [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3 [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d [No types assigned]