# CVE-2022-48630: crypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ

> An infinite loop in the Qualcomm RNG driver causes a denial of service when processing requests not aligned to word size.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2024
- **Updated:** 23 May 2026
- **Also known as:** DEBIAN-CVE-2022-48630, GHSA-4rpf-4vmp-3hfw, UBUNTU-CVE-2022-48630

## What is CVE-2022-48630?

CVE-2022-48630 is a medium-severity denial of service vulnerability in Linux kernel, published on 5 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2022-48630?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2022-48630?

Apply the vendor's patch.

## Is CVE-2022-48630 being exploited?

There is no known exploitation of CVE-2022-48630 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48630 and fix it if it is affected.

What it is: CVE-2022-48630 is a medium-severity denial of service vulnerability in Linux kernel, published on 5 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48630 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48630/ (Markdown: https://insights.sbomify.com/CVE-2022-48630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48630
- OSV: https://osv.dev/vulnerability/CVE-2022-48630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48630/
Summaries are generated and may contain mistakes; the official description above is the record.