ghsa-4rpf-4vmp-3hfw
Vulnerability from github
Published
2024-03-05 12:30
Modified
2025-02-03 15:31
Severity ?
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Details

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.

Show details on source website

To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2022-48630"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-835"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-03-05T12:15:45Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ\n\nThe commit referenced in the Fixes tag removed the \u0027break\u0027 from the else\nbranch in qcom_rng_read(), causing an infinite loop whenever \u0027max\u0027 is\nnot a multiple of WORD_SZ. This can be reproduced e.g. by running:\n\n    kcapi-rng -b 67 \u003e/dev/null\n\nThere are many ways to fix this without adding back the \u0027break\u0027, but\nthey all seem more awkward than simply adding it back, so do just that.\n\nTested on a machine with Qualcomm Amberwing processor.",
  "id": "GHSA-4rpf-4vmp-3hfw",
  "modified": "2025-02-03T15:31:59Z",
  "published": "2024-03-05T12:30:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48630"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/05d4d17475d8d094c519bb51658bc47899c175e3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/16287397ec5c08aa58db6acf7dbc55470d78087d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/71a89789552b7faf3ef27969b9bc783fa0df3550"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8a06f25f5941c145773204f2f7abef95b4ffb8ce"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8be06f62b426801dba43ddf8893952a0e62ab6ae"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.