Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-48630, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 87% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d – < 71a89789552b7faf3ef27969b9bc783fa0df3550
    • affected 184f7bd08ce56f003530fc19f160d54e75bf5c9d – < 8be06f62b426801dba43ddf8893952a0e62ab6ae
    • affected 0f9b7b8df17525e464294c916acc8194ce38446b – < 233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c
    • affected ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd – < 8a06f25f5941c145773204f2f7abef95b4ffb8ce
    • affected a680b1832ced3b5fa7c93484248fd221ea0d614b – < 05d4d17475d8d094c519bb51658bc47899c175e3
    • affected a680b1832ced3b5fa7c93484248fd221ea0d614b – < 16287397ec5c08aa58db6acf7dbc55470d78087d
    • affected 485995cbc98a4f77cfd4f8ed4dd7ff8ab262964d
    • affected 4.19.236 – < 4.19.245
    • affected 5.4.187 – < 5.4.196
    • affected 5.10.108 – < 5.10.118
    • affected 5.15.31 – < 5.15.42
    • affected 5.16.17 – < 5.17
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 4.19.245 – ≤ 4.19.*
    • unaffected 5.4.196 – ≤ 5.4.*
    • unaffected 5.10.118 – ≤ 5.10.*
    • unaffected 5.15.42 – ≤ 5.15.*
    • unaffected 5.17.10 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48630 badge
[![CVE-2022-48630](https://cveledger.app/badge/CVE-2022-48630.svg)](https://cveledger.app/cve/CVE-2022-48630)

Record last updated .