CVE-2022-48630

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

State: Published
Severity: Not scored
Published: Mar 5, 2024
Updated: May 23, 2026
Reserved: Feb 25, 2024

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

Product	Versions
LinuxLinux	a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d to before 71a89789552b7faf3ef27969b9bc783fa0df3550Affected 184f7bd08ce56f003530fc19f160d54e75bf5c9d to before 8be06f62b426801dba43ddf8893952a0e62ab6aeAffected 0f9b7b8df17525e464294c916acc8194ce38446b to before 233a3cc60e7a8fe0be8cf9934ae7b67ba25a866cAffected ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd to before 8a06f25f5941c145773204f2f7abef95b4ffb8ceAffected a680b1832ced3b5fa7c93484248fd221ea0d614b to before 05d4d17475d8d094c519bb51658bc47899c175e3Affected a680b1832ced3b5fa7c93484248fd221ea0d614b to before 16287397ec5c08aa58db6acf7dbc55470d78087dAffected 485995cbc98a4f77cfd4f8ed4dd7ff8ab262964dAffected 4.19.236 to before 4.19.245Affected 5.4.187 to before 5.4.196Affected 5.10.108 to before 5.10.118Affected 5.15.31 to before 5.15.42Affected 5.16.17 to before 5.17Affected
LinuxLinux	5.17Affected before 5.17Not affected 4.19.245 through 4.19.Not affected 5.4.196 through 5.4.Not affected 5.10.118 through 5.10.Not affected 5.15.42 through 5.15.Not affected 5.17.10 through 5.17.*Not affected 5.18 and laterNot affected

Product

Versions

LinuxLinux

a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d to before 71a89789552b7faf3ef27969b9bc783fa0df3550Affected
184f7bd08ce56f003530fc19f160d54e75bf5c9d to before 8be06f62b426801dba43ddf8893952a0e62ab6aeAffected
0f9b7b8df17525e464294c916acc8194ce38446b to before 233a3cc60e7a8fe0be8cf9934ae7b67ba25a866cAffected
ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd to before 8a06f25f5941c145773204f2f7abef95b4ffb8ceAffected
a680b1832ced3b5fa7c93484248fd221ea0d614b to before 05d4d17475d8d094c519bb51658bc47899c175e3Affected
a680b1832ced3b5fa7c93484248fd221ea0d614b to before 16287397ec5c08aa58db6acf7dbc55470d78087dAffected
485995cbc98a4f77cfd4f8ed4dd7ff8ab262964dAffected
4.19.236 to before 4.19.245Affected
5.4.187 to before 5.4.196Affected
5.10.108 to before 5.10.118Affected
5.15.31 to before 5.15.42Affected
5.16.17 to before 5.17Affected

LinuxLinux

5.17Affected
before 5.17Not affected
4.19.245 through 4.19.*Not affected
5.4.196 through 5.4.*Not affected
5.10.118 through 5.10.*Not affected
5.15.42 through 5.15.*Not affected
5.17.10 through 5.17.*Not affected
5.18 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.