CVE-2022-48630
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-835
- Record status
- Analyzed
Affected
- Linux Kernel < 4.19.245
- Linux Kernel < 5.4.196
- Linux Kernel < 5.10.118
- Linux Kernel < 5.15.42
- Linux Kernel < 5.17.10
- Linux Kernel 5.18
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-48630.md and follow it. Check whether this project is affected by CVE-2022-48630. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3
- https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d
- https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c
- https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550
- https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce
- https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae
- https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3
- https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d
- https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c
- https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550
References
- https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3
- https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d
- https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c
- https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550
- https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce
- https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae
- https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3
- https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d
- https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c
- https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550
- https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce
- https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae